grace-status
npx machina-cli add skill osovv/grace-marketplace/grace-status --openclawShow the current state of the GRACE project.
Report Contents
1. Artifacts Status
Check existence and version of:
-
AGENTS.md— GRACE principles -
docs/knowledge-graph.xml— version and module count -
docs/requirements.xml— version and UseCase count -
docs/technology.xml— version and stack summary -
docs/development-plan.xml— version and module count
2. Codebase Metrics
Scan source files and report:
- Total source files
- Files WITH MODULE_CONTRACT
- Files WITHOUT MODULE_CONTRACT (warning)
- Total semantic blocks (START_BLOCK / END_BLOCK pairs)
- Unpaired blocks (integrity violation)
3. Knowledge Graph Health
Quick check:
- Modules in graph vs modules in codebase
- Any orphaned or missing entries
4. Recent Changes
List the 5 most recent CHANGE_SUMMARY entries across all files.
5. Suggested Next Action
Based on the status, suggest what to do next:
- If no requirements — "Define requirements in docs/requirements.xml"
- If requirements but no plan — "Run
$grace-plan" - If plan but missing modules — "Run
$grace-generate moduleor$grace-execute" - If drift detected — "Run
$grace-refresh" - If everything synced — "Project is healthy"
Source
git clone https://github.com/osovv/grace-marketplace/blob/main/codex-skills/grace-status/SKILL.mdView on GitHub Overview
Grace-status provides a concise health snapshot by aggregating artifacts status, codebase metrics, knowledge graph health, and recent changes. It highlights drift, missing contracts, or unpaired semantic blocks and suggests a concrete next action to remediate.
How This Skill Works
It scans artifact files (AGENTS.md, docs/*.xml) and computes codebase metrics (total files, files with/without MODULE_CONTRACT, semantic block pairs, unpaired blocks). It also compares knowledge graph modules to the codebase and lists the five most recent CHANGE_SUMMARY entries, deriving a recommended next action from the current state.
When to Use It
- Before sharing a project health report with stakeholders.
- Prior to running grace-plan to understand prerequisites.
- When you notice drift between the knowledge graph and codebase.
- After large artifacts changes to verify impact.
- Prior to release to confirm all modules are synced.
Quick Start
- Step 1: Run grace-status to generate the health report.
- Step 2: Review Artifacts Status, Codebase Metrics, and Knowledge Graph Health sections.
- Step 3: Follow the Suggested Next Action to remediate issues.
Best Practices
- Run grace-status after every major change to artifacts.
- Cross-check modules in the knowledge graph against the codebase.
- Review the five most recent changes to contextualize findings.
- Address unpaired blocks or missing contracts before planning.
- Use the suggested next action as the gating step for workflows.
Example Use Cases
- Artifacts and codebase are in sync; KG health is green; next action: Project is healthy.
- Drift detected: modules listed in the knowledge graph don't match codebase; next action: Run $grace-refresh.
- Missing AGENTS.md or outdated docs found; next action: Define requirements in docs/requirements.xml.
- Unpaired semantic blocks detected in START_BLOCK/END_BLOCK pairs; next action: fix blocks and re-run checks.
- Several recent changes in docs/knowledge-graph.xml; next action: Run $grace-plan and review modified modules.
