メニュー
Routes agents to the Contractify audit track — discovery, drift, conflicts, actionable JSON. Triggers on contract audit, contractify check, run contractify audit, repository contract drift.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | contractify-check |
| description | Routes agents to the Contractify audit track — discovery, drift, conflicts, actionable JSON. Triggers on contract audit, contractify check, run contractify audit, repository contract drift. |
Follow contract-audit-task.md end-to-end.
Quick CLI:
python -m contractify.tools audit --json --out "'fy'-suites/contractify/reports/_local_contract_audit.json"
# compare against tracked markdown: 'fy'-suites/contractify/reports/CANONICAL_REPO_ROOT_AUDIT.md
Pre-work reality snapshot (human context): state/PREWORK_REPOSITORY_CONTRACT_REALITY.md
Routes agents to the correct Despaghettify task markdown — check vs solve vs add-task vs autonomous loop vs clean vs reset. Triggers on despaghettify orchestration, spaghetti pipeline, M7 scan then implement, run spaghetti-autonomous-agent-task, which DS next, wipe artefacts only or full hub reset.
Use when verifying gate health after merges, diagnosing gate failures, troubleshooting false positives, adjusting thresholds, or syncing enforcement config with baseline updates
Use when running comprehensive governance health checks, detecting cross-suite drift, verifying coherence before major merges, or synthesizing findings across contractify, docify, and despaghettify audits
Routes agents to the correct Despaghettify task markdown — check vs solve vs add-task vs autonomous loop vs clean vs reset. Triggers on despaghettify orchestration, spaghetti pipeline, M7 scan then implement, run spaghetti-autonomous-agent-task, which DS next, wipe artefacts only or full hub reset.
Use when determining MVP readiness status across domains, identifying blockers preventing completion, assessing domain maturity levels, or prioritizing next work targets
Use when integrating YAML content authority (God of Carnage builtin roles) into turn execution, testing authority conflict detection, verifying YAML module loads correctly, or ensuring content authority flows through turn graph