From grace
Synchronizes GRACE shared artifacts like knowledge-graph.xml and verification-plan.xml with codebase via targeted scans on changes or full tree scans after refactors or drift.
npx claudepluginhub osovv/grace-marketplace --plugin graceThis skill uses the workspace's default tool permissions.
Synchronize the GRACE shared artifacts with the actual codebase.
Reviews GRACE project integrity by validating semantic markup, module contracts, knowledge graph synchronization, and verification plans. Supports scoped-gate, wave-audit, and full-integrity modes.
Verifies and updates existing codebase documentation nodes (docs/*.md) against current code after changes or refactors. Fast mode for triaged items; full audits entire knowledge base.
Verifies V-Model artifact graph integrity: checks dead links, backlog completeness, references in Epics, Features, Success Criteria, ADRs, arc42 sections, PLANs, Wayfinder rows, and code. Syntactic mode default; semantic on request.
Share bugs, ideas, or general feedback.
Synchronize the GRACE shared artifacts with the actual codebase.
Default to the narrowest scope that can still answer the drift question.
targeted (default during active execution)fullDecide whether the refresh should be targeted or full.
targetedfulltargeted to full when the localized scan reveals wider inconsistencyWhen the optional grace CLI is available, you may use grace lint --path <project-root> as a quick preflight before starting a broader refresh. Treat it as a hint source, not as the refresh itself.
You may also use:
grace module find <changed-path-or-query> --path <project-root> to resolve the likely module scope from changed files or namesgrace module show M-XXX --path <project-root> --with verification to grab the shared/public contract, dependency, and verification contextgrace file show <path> --path <project-root> --contracts --blocks to inspect file-local/private details without rereading whole source files firstFor each file in scope, extract:
Treat shared XML artifacts as public-surface documents:
In targeted mode, also inspect the immediate dependency surfaces needed to validate CrossLinks accurately.
Read docs/knowledge-graph.xml and, when present, docs/verification-plan.xml. Identify:
V-M-xxx entryDo not report drift just because a private helper exists in source but not in shared docs. Shared docs should only drift on public contract or dependency changes.
Present a structured report:
GRACE Integrity Report
======================
Mode: targeted / full
Scope: [modules or files]
Synced modules: N
Missing from graph: [list files]
Orphaned in graph: [list entries]
Stale CrossLinks: [list]
Files without contracts: [list files]
Missing verification entries: [list modules]
Stale verification refs: [list entries]
Escalation: no / yes - reason
For each issue, propose a fix:
V-M-xxx block in docs/verification-plan.xmlWhen updating graph or plan artifacts, add only public module-facing annotations and interfaces. Keep private helper details local to the source file.
Ask the user for confirmation before applying fixes.
Apply approved fixes to docs/knowledge-graph.xml and docs/verification-plan.xml as needed. Update versions only after the selected refresh scope is reconciled.
full whenever targeted evidence suggests broader drift