Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Development

grace-cli

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

osovv · AI review on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add osovv/grace-marketplace --skill grace-cli

About this skill


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

<command_run_contract> --run-commands executes each declared MustPassCommand value once per lint, fail-fast, with a default 600s per-command timeout (--command-timeout SECONDS overrides, 0 disables). Plan, progress, and per-command result lines go to stderr; the lint report and JSON go to stdout, so piping stdout stays safe. Agents and pipes get compact output by default; interactive terminals see live streamed command output. Force modes with --verbose (live) or --quiet (compact); they are mutually exclusive, and --format json is always compact. Full combined output of every command is stored per run under ~/.cache/grace/run-commands/<project>/runs/<run>/ (respecting XDG_CACHE_HOME) with a machine-readable meta.json; failing commands print a bounded output tail plus the absolute log path. Interrupted runs (SIGINT/SIGTERM) kill the whole command process group, record interrupted status in meta.json, and exit 130. </command_run_contract>

<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>