grace-cli
Use the optional grace CLI as a fast GRACE-aware read/query layer.
Prerequisites
- The
gracebinary must be installed and available onPATH - The target repository should already use GRACE artifacts and markup
- Prefer
--path <project-root>unless you are already in the project root
If the CLI is missing, or the repository is not a GRACE project, say so and fall back to reading the relevant docs and code directly.
Choose the Right Command
grace lint --path <project-root>Use for a fast integrity snapshot across semantic markup, XML artifacts, and export/map drift.grace lint --profile autonomous --path <project-root>Use before long agent runs to verify that operational packets, verification entries, and observable evidence are strong enough for autonomous execution.grace lint --explain <code>Use when a lint code appears in CI or review and you want the built-in explanation plus remediation guidance.grace status --path <project-root>
More from osovv/grace-marketplace
grace-explainer
Complete GRACE methodology reference. Use when explaining GRACE to users, onboarding new projects, or when you need to understand the GRACE framework - its principles, semantic markup, knowledge graphs, contracts, testing, and unique tag conventions.
49grace-multiagent-execute
Execute a GRACE development plan in controller-managed parallel waves with selectable safety profiles, verification-plan excerpts, batched shared-artifact sync, and scoped reviews.
30grace-execute
Execute the full GRACE development plan step by step with controller-managed context packets, verification-plan excerpts, scoped reviews, level-based verification, and commits after validated sequential steps.
28grace-status
Show the current health status of a GRACE project. Use to get an overview of project artifacts, codebase metrics, knowledge graph health, verification coverage, and suggested next actions.
27grace-fix
Debug an issue using GRACE semantic navigation. Use when encountering bugs, errors, or unexpected behavior - navigate through the graph, verification plan, and semantic blocks to analyze the mismatch and apply a targeted fix.
27grace-refresh
Synchronize GRACE shared artifacts with the actual codebase. Use targeted refresh after controlled waves, or full refresh after refactors and when you suspect wider drift between the graph, verification plan, and code.
27