rebar

Principal-engineer codebase health pipeline — a deliberate pause-between-features to buy back optionality. Runs five phases: Discovery (one-concern-per-subagent fan-out over code debt, smells, architectural decay, separation of concerns, spent optionality, doc gaps, oversized units, AI-generated-code & security smells, and temporal decay — returns finding+evidence with NO severity), Verification (an independent blue-team pass that scores validity + impact and drops low-confidence / low-value findings), Remediation (blind parallel proposers with move-level convergence + an OSS-research tiebreak), Approval (a Remediation Plan reviewed one item at a time, approve/refine/reject), and Ticketization (approved work filed as child tickets under a Janitor Cleanup epic). Never edits code — the plan and tickets are the deliverable. Use when the user wants a maintainability/tech-debt review, asks to "clean up" or "audit" a codebase, or invokes /rebar-janitor.

A hypothesis-driven debugging protocol. Takes a problem (or list of problems) and drives each to a proven root cause via the scientific method under a strict two-phase discipline. Phase 1 (Understand) is analysis-only and moves through three separated stages — gather context into a descriptive dossier, fan out a subagent to propose falsifiable root causes with citations, then run experiments to confirm/reject (looping on total rejection) — and its work product is a confirmed, cited root cause. Only a proven root cause unlocks Phase 2 (Repair), which enforces strict RED→GREEN discipline: write a failing test that exercises the mechanism, fix it with a held-out subagent, and replicate the original report to confirm resolution. Use when the user wants to debug a bug/incident/ticket rigorously, asks to find the root cause of a failure, or invokes /rebar-debug.