grace-cli
Operate the GRACE 4 CLI for .grace linting, status, module navigation, verification navigation, and file-local semantic markup.
@osovvInstall SkillDevelopment
Skill
/grace-ask
Answer questions about a GRACE 4 project by navigating .grace current-state artifacts and file-local semantic markup.
Claude Code
$ npx -y skills add osovv/grace-marketplace --skill grace-ask --agent claude-code
Codex
$ npx skills add osovv/grace-marketplace --skill grace-ask -a codex -y
Cursor
$ npx skills add osovv/grace-marketplace --skill grace-ask -a cursor -y
Gemini CLI
$ npx skills add osovv/grace-marketplace --skill grace-ask -a gemini-cli -y
GitHub Copilot
$ npx skills add osovv/grace-marketplace --skill grace-ask -a github-copilot -y
OpenCode
$ npx skills add osovv/grace-marketplace --skill grace-ask -a opencode -y
Windsurf
$ npx skills add osovv/grace-marketplace --skill grace-ask -a windsurf -y
SKILL.md
grace-ask.SKILL.mdname: grace-ask description: Answer questions about a GRACE 4 project by navigating .grace current-state artifacts and file-local semantic markup.
<skill> <context_order> 1. `.grace/context/*.xml` for requirements, technology, principles, deployment, and UX constraints. 2. `.grace/graph/index.xml` then routed graph documents for `M-*` and `DF-*` ownership. 3. `.grace/verification/index.xml` then routed verification documents for `V-M-*` coverage. 4. `.grace/changes/active/C-*` for in-flight approved or draft work. 5. File-local `MODULE_CONTRACT`, `MODULE_MAP`, `LINKS:`, `START_CONTRACT`, and `START_BLOCK_` anchors. </context_order>
<answer_rules>
- Cite the artifact or anchor that supports each important claim.
- Distinguish durable current state from active change intent.
- If legacy GRACE 3 docs are present, explain that they require `grace-migrate` and are not GRACE 4 truth.
- Do not invent missing graph or verification facts; report uncertainty and the safest next lookup.
</answer_rules> </skill>
Stats
268
Stars
60
Forks
Maintained
Maintenance
TypeScript
Language
MIT
License
Last commit
Created
Ships withgrace-marketplace
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.
26815 skills
Stars on GitHub
Momentum
- stars in total
- 268
Other skills on grace-marketplace.
@osovvInstall Skillgrace-execute
Execute an approved GRACE 4 GraceChangePlan in sequential or parallel-safe mode with recovery-aware preflight and centralized…
@osovvInstall Skillgrace-explainer
Explain GRACE 4 methodology, .grace artifacts, semantic anchors, change lifecycle, verification, and migration boundaries.
@osovvInstall Skillgrace-fix
Debug and fix issues in a GRACE 4 project using .grace semantic navigation, assertions, and verification evidence.
@osovvInstall Skillgrace-init
Bootstrap a Full GRACE 4 project by creating the canonical .grace context, graph, verification, and changes skeleton.
@osovvInstall Skillgrace-migrate
Agent-applied GRACE 3 to GRACE 4 migration workflow. CLI validates the result but does not convert or delete files.
@osovvInstall SkillMore skills from other plugins.
Auto-invoked
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
@obraInstall Skillask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
@mattpocockInstall SkillAuto-invoked
Questions about grace-ask.
- Which coding agents can use grace-ask?
- grace-ask installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.