grace-ask
Answer questions about a GRACE 4 project by navigating .grace current-state artifacts and file-local semantic markup.
Detect drift between observed repository state and durable GRACE 4 .grace current state, then help create reconciliation changes.
$ npx -y skills add osovv/grace-marketplace --skill grace-refresh --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/grace-refreshContext preview
The summary Claude sees to decide when to auto-load this skill.
Detect drift between observed repository state and durable GRACE 4 .grace current state, then help create reconciliation changes.
name: grace-refresh description: Detect drift between observed repository state and durable GRACE 4 .grace current state, then help create reconciliation changes.
<skill> <purpose> 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. </purpose>
<workflow> 1. Run or request `grace lint --path <project-root>` and `grace status --path <project-root>`. 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. </workflow> </skill>
GRACE means Graph-RAG Anchored Code Engineering: a contract-first AI engineering methodology built around semantic markup, .grace XML artifacts, knowledge-graph navigation, assertions, scopes, and log-driven verification.
Repo: osovv/grace-marketplace
Answer questions about a GRACE 4 project by navigating .grace current-state artifacts and file-local semantic markup.
Operate the GRACE 4 CLI for .grace linting, status, module navigation, verification navigation, and file-local semantic markup.
Execute an approved GRACE 4 GraceChangePlan in sequential or parallel-safe mode with recovery-aware preflight and centralized durable apply.
Explain GRACE 4 methodology, .grace artifacts, semantic anchors, change lifecycle, verification, and migration boundaries.
Debug and fix issues in a GRACE 4 project using .grace semantic navigation, assertions, and verification evidence.
Bootstrap a Full GRACE 4 project by creating the canonical .grace context, graph, verification, and changes skeleton.