About grace-refresh
A skill for checking whether code, tests, and file-local markup remain aligned with Grace's context, graph, verification records, and active change scopes. It reports drift and proposes reconciliation through GraceChangeSpec and GraceChangePlan rather than directly changing state.
Key features
- 01Checks Grace lint and status
- 02Finds stale or missing graph anchors
- 03Checks verification coverage and evidence
- 04Compares markup, contracts, tests, and logs
- 05Reports drift and proposes reconciliation
Use cases
- 01Auditing a repository for documentation drift
- 02Finding missing verification coverage
- 03Preparing scoped Grace changes
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ osovv/ grace-marketplace --skill grace-refreshAfter installing, type/grace-refreshin Claude Code to confirm it loaded.
Bundled filesagents/openai.yaml
Details
From the project README
Compare code, tests, and file-local markup against `.grace/context`, `.grace/graph`, `.grace/verification`, and active change scopes. This skill reports drift and proposes a normal `GraceChangeSpec`/`GraceChangePlan`; it does not silently mutate current state.
1. Run or request `grace lint --path ` and `grace status --path `.
2. Inspect `.grace/graph/index.xml` and routed graph documents for stale, missing, or orphaned `M-*` and `DF-*` anchors.
3. Inspect `.grace/verification/index.xml` and routed verification documents for missing deterministic `V-M-*` coverage, stale commands, or missing evidence markers.
4. Compare file-local `LINKS:`, module contracts, tests, and log markers against durable anchors.
5. Report drift as findings with proposed reconciliation scope.
6. If changes are needed, route through `grace-spec` and `grace-plan` instead of direct mutation.
Comments
Markdown supported