Skip to content
Development
Skill

/grace-cli

Operate the GRACE 4 CLI for .grace linting, status, module navigation, verification navigation, and file-local semantic markup.

From plugin
grace-marketplace
23330 skills
Install
$ npx -y skills add osovv/grace-marketplace --skill grace-cli --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/grace-cli

Context preview

The summary Claude sees to decide when to auto-load this skill.

Operate the GRACE 4 CLI for .grace linting, status, module navigation, verification navigation, and file-local semantic markup.

SKILL.md

grace-cli.SKILL.md
name: grace-cli
description: Operate the GRACE 4 CLI for .grace linting, status, module navigation, verification navigation, and file-local semantic markup.

<skill> <installation_contract>Invoke the installed stable `grace` binary directly. If it is missing, install it with `bun add -g @osovv/grace-cli`. Do not default to `bunx`, `npx`, or the `rc` dist-tag.</installation_contract>

<commands>

  • Active-baseline preflight before observed writes: `grace lint --path PROJECT --assertions current`
  • Selected baseline: `grace lint --path PROJECT --change C-ID --assertions baseline` (add `--run-commands` when the baseline declares `MustPassCommand`)
  • Selected target: `grace lint --path PROJECT --change C-ID --assertions target --run-commands`
  • Final execution gate: `grace lint --path PROJECT --change C-ID --assertions final --run-commands`
  • Parallel preflight: `grace lint --path PROJECT --parallel-preflight`
  • Status: `grace status --path PROJECT --with modules --json`
  • Navigation: `grace module find|show`, `grace verification find|show`, and `grace file show`.

</commands>

<lifecycle_command_contract>`current` evaluates active approved baselines and is not end-state evidence. Keep `MustPassCommand` entries as leaf project checks; do not nest `grace lint`, `grace status`, or another GRACE lifecycle command inside plan assertions. Run selected target/final lint externally.</lifecycle_command_contract>

<failure_contract> Lint, status, and navigation commands validate before returning records. JSON argument/runtime failures are one `{ "schemaVersion": "1.0.0", "ok": false, "error": { ... } }` object on stdout. Text failures are one concise actionable line with a nonzero exit code and no stack trace. </failure_contract>

<runtime_contract> TypeScript/JavaScript analysis is bundled. Python and Dart governed files require their runtimes on PATH; missing runtimes fail closed with actionable `analysis.runtime-missing` diagnostics instead of silently dropping parity checks. </runtime_contract>

<migration_boundary>GRACE 4 commands do not dual-validate legacy GRACE 3 docs. Use `grace-migrate`.</migration_boundary> </skill>

Read more
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.

Get the whole plugin
Stats
233
Stars
51
Forks
Active
Maintenance
TypeScript
Language
MIT
License
14d ago
Last commit
5mo ago
Created

Repo: osovv/grace-marketplace