Agent skill

grace-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.

Stars 120
Forks 30

Install this agent skill to your Project

npx add-skill https://github.com/osovv/grace-marketplace/tree/main/skills/grace/grace-status

SKILL.md

Show 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
  • docs/verification-plan.xml — version and verification entry count
  • docs/operational-packets.xml — optional packet template version

2. Codebase Metrics

Scan source files and report:

  • Total source files
  • Files WITH MODULE_CONTRACT
  • Files WITHOUT MODULE_CONTRACT (warning)
  • Total test files
  • Test files WITH MODULE_CONTRACT
  • Total semantic blocks (START_BLOCK / END_BLOCK pairs)
  • Unpaired blocks (integrity violation)
  • Files with stable log markers
  • Test files that assert log markers or traces when relevant

3. Knowledge Graph and Verification Health

Quick check:

  • Modules in graph vs modules in codebase
  • Any orphaned or missing entries
  • Modules in verification plan vs modules in development plan
  • Missing or stale verification refs

If the optional grace CLI is available, you may also run grace lint --path <project-root> as a fast integrity snapshot and include any relevant findings in the report.

When the report needs focused navigation instead of raw artifact dumps, you may also use:

  • grace module find <query> --path <project-root> to resolve the relevant module from names, IDs, dependencies, or changed paths
  • grace module show M-XXX --path <project-root> --with verification for the shared/public module snapshot
  • grace file show <path> --path <project-root> --contracts --blocks for the file-local/private markup snapshot

4. Recent Changes

List the 5 most recent CHANGE_SUMMARY entries across source and substantive test 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 exists but verification is still thin — "Run $grace-verification"
  • If plan and verification are ready but modules are missing — "Run $grace-execute or $grace-multiagent-execute"
  • If drift detected — "Run $grace-refresh"
  • If fast integrity signals are needed before deeper review — "Run grace lint --path <project-root>"
  • If the next step is targeted investigation of one module or file — "Run grace module show M-XXX --path <project-root> --with verification or grace file show <path> --path <project-root> --contracts --blocks"
  • If tests or logs are too weak for autonomous work — "Run $grace-verification"
  • If everything synced — "Project is healthy"

Expand your agent's capabilities with these related and highly-rated skills.

osovv/grace-marketplace

grace-verification

Design and enforce testing, traces, and log-driven verification for a GRACE project. Use when modules need stronger automated tests, execution-trace checks, or a maintained verification-plan.xml that autonomous and multi-agent workflows can trust.

120 30
Explore
osovv/grace-marketplace

grace-refactor

Refactor GRACE-governed code safely: rename, move, split, merge, or extract modules while keeping contracts, graph, verification, and semantic markup synchronized.

120 30
Explore
osovv/grace-marketplace

grace-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.

120 30
Explore
osovv/grace-marketplace

grace-cli

Operate the optional `grace` CLI against a GRACE project. Use when you want to lint GRACE artifacts, resolve modules from names or file paths, inspect shared/public module context, or inspect file-local/private markup through `grace lint`, `grace module find`, `grace module show`, and `grace file show`.

120 30
Explore
osovv/grace-marketplace

grace-plan

Run the GRACE architectural planning phase. Use when you have requirements and technology decisions defined and need to design the module architecture, create contracts, map data flows, and establish verification references. Produces development-plan.xml, verification-plan.xml, and knowledge-graph.xml.

120 30
Explore
osovv/grace-marketplace

grace-reviewer

GRACE integrity reviewer. Use for fast scoped gate reviews during execution, or full integrity audits at phase boundaries and after broader code, graph, or verification changes.

120 30
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results