メニュー
Use when asked about a rebar repo's health, compliance, tier, or contract status — and before claiming any tier, badge, or "green" state in docs or commits. Runs the three status surfaces and reads them without conflating the two maturity vocabularies.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
Use at the start of every session in a REBAR-managed repo, before the first substantive task — and any time you catch yourself working from stale context (post-compaction restart, missing cold-start hook output, QUICKCONTEXT claims that don't match git reality). Runs the session-start ritual that grounds you in current project state.
Use when you hit a gap, anti-pattern, bug, or missing guidance in rebar's templates, practices, or scripts during real work — or when the user says "file feedback" / "write this up for rebar." Files a durable feedback item instead of editing templates directly.
Use during multi-repo coordination phases (release days, cross-repo arcs, ratification rounds) when this repo holds a peer inbox/ directory — arms a persistent background watcher so new memo deposits reach you as live notifications instead of sitting unread while a peer waits.
SOC 職業分類に基づく
| name | rebar-audit |
| description | Use when asked about a rebar repo's health, compliance, tier, or contract status — and before claiming any tier, badge, or "green" state in docs or commits. Runs the three status surfaces and reads them without conflating the two maturity vocabularies. |
rebar audit — REBAR CLI compliance audit; sectioned score out of 10
(rebar itself expects 9–10/10).scripts/ci-check.sh — the full enforcement-script suite; the exit
code is the verdict, the output names each failing check.scripts/steward.sh --summary — one-liner: contract counts by
computed lifecycle, open discoveries, enforcement passing. A full
scripts/steward.sh run writes STEWARD_REPORT.md +
architecture/.state/steward-report.json.Computed lifecycle (draft/active/testing/impl-present) is derived by
the steward from file presence, while declared maturity
(stub/draft/in-progress/active/verified) is an honest human/agent
declaration of how real the artifact is. Canonical definitions:
rebar:convention (§Lifecycle Status Definitions, §Declared Maturity) —
resolve with scripts/rebar-doc.sh rebar:convention --cat (or rebar doc
if the CLI is installed).
--summary counts, the
STEWARD_REPORT.md table, the .state JSON. impl-present means
implementation files exist — it does NOT mean proven.Status: lines in artifact headers
(architecture/CONTRACT-*.md) and is weighted into the compliance badge
by scripts/check-compliance.sh. Only this vocabulary may say verified
(active + passing tests/scenarios proving it).Report what the surfaces actually printed, not what you expected.