rebar

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.

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.