Loop directory
4 loops match your filters.
Including grade C — stops on its own, but runs fewer checks than A or B. Back to A and B →
C
/goalDebuggingmedium risknew
Debug, fix, verify regression
Narrate the root cause, diff summary, and regression test path until the test passes.
/goal "Claude has narrated the three-part completion output (root-cause one-liner, fix diff summary, regression-test path) with the regression test passing" /superpowers:systematic-debugging "<symptom>"
C
/goalDebugginglow risk
Run agent goal with CI exit codes
Your agent runs autonomously toward a goal and exits 0 on success or 2 if blocked, enabling CI integration.
/goal "…" works autonomously until the goal is done and verified, or reports exactly why it is blocked. Exits 0 or 2 in headless mode, so it works in CI. |
C
/loopDebuggingmedium risk
Rewrite every user-facing error
Inventory user-visible errors, replace internal or confusing text, and prove each reachable error state reads clearly.
Find and improve every user-visible error message within [repository, product, or named scope]. If no scope is supplied, use the user-facing surfaces in the current repository and state any exclusions before editing. Inventory error strings in source code, surfaced API or client errors, and reachable browser states. Record each one in a CSV with its location, trigger, current copy, user risk, proposed replacement, implementation status, and verification result. Rank the errors by user harm. Rewrite one coherent group at a time using plain language and a useful recovery step when one exists. Do not expose provider names, stack traces, internal identifiers, or implementation details. After each change, run the relevant tests, exercise the affected state in a real browser when possible, and search again for raw or internal error text. Do not mark an unreachable state as verified. Stop when every row is verified or explicitly blocked. Finish with the CSV, changed files, test evidence, browser evidence, and blocked items.
B
/ralphDebugginghigh risk
Ralph the bug backlog
Work a triaged bug list one fix per fresh-context iteration: reproduce first, fix minimally, prove it with a regression test, and log root-cause patterns to guardrails.
/loop fresh context each iteration: read bugs.json and .ralph/guardrails.md, take the top open bug, write a failing test that reproduces it before touching any code, then apply the smallest fix that makes the test pass with the rest of the suite green, and mark the bug fixed; if you cannot reproduce it, mark it needs-info with your findings instead; append recurring root-cause patterns to .ralph/guardrails.md; stop when bugs.json is clear or after 25 turns