Clean up the slop

Review your recent diff for debug code, dead branches, and bad names, then fix with minimal edits until lint and tests pass.

prompt
→ Claude Code
/goal the recent diff is clean and convention-aligned — review it for debug code, dead branches, and bad names, fix with minimal edits until `npm run lint && npm test` passes; stop after 4 turns
claude-code · codex · cursor

Implementation note

Perfect as a final pass after a long agent session. The tight 4-turn cap keeps it from rewriting things it shouldn't.

Source: loops! ↗graded A · 100/100 — how grades work →

More quality loops

Repair accessibility, highest-impact first

Confirm barriers against an agreed standard, fix the one with the greatest user impact, and rerun the same checks.

prompt
→ Claude Code
Check [scope] against [accessibility standard, such as WCAG 2.2 AA] with automated scans and available keyboard, screen-reader, and other manual tests. Confirm each issue, rank it by harm, and fix the highest-impact blocker. Rerun the same checks, affected task, and regression tests. Keep only verified fixes. Stop when no blocker remains, progress stalls, verification is unavailable, or approval is required. Never silence a check or weaken the target. Return issues, fixes, evidence, exceptions, and untested needs.

Fifteen-minute verification report while you work

Loop/loopGitHubAnew

A recurring six-phase check (build, types, lint, tests with coverage, secret and debug-log grep, diff size) that prints one fixed-format report every fifteen minutes so you catch drift before the PR, not in review. It is strictly read-only: the loop reports, you decide what to fix. It exits when the tests pass and the report reads READY twice running, escalates instead of retrying when the same check fails three times, and stops after eight checks no matter what. Adapted from ECC's verification-loop skill (affaan-m/ECC, MIT), whose 'continuous mode' names the cadence but has no turn cap, exit, or failure path; all three are added here.

prompt
→ Claude Code
/loop every 15 minutes while I work: run `npm run build`, `npx tsc --noEmit`, `npm run lint`, and `npm test -- --coverage`, then grep src/ for `sk-`, `api_key`, and `console.log`, then `git diff --stat`. Print a VERIFICATION REPORT with Build / Types / Lint / Tests (X/Y passed, Z% coverage) / Security / Diff as PASS or FAIL and an overall READY or NOT READY for PR verdict, plus an Issues to Fix list. Report only — never edit files, never commit. Exit when `npm test` exits 0 and the report says READY twice in a row. If the same check FAILs on three consecutive passes, stop and escalate to me with the failing output instead of retrying. Stop after 8 checks regardless.

Karpathy-Style CLAUDE.md Self-Check Protocol for Loops

A self-check protocol embedded in CLAUDE.md that every loop iteration obeys before ending a turn: re-read the goal, diff the changes against it, run the verification command, and state what remains — a ritual that catches drift between iterations.

prompt
→ Claude Code
Preamble rules embedded in CLAUDE.md that every loop iteration obeys: before ending a turn, re-read the goal, diff your changes against it, run the verification command, and explicitly state what remains — a self-check ritual that catches drift between iterations. (Community template descended from Andrej Karpathy's circulated CLAUDE.md rules.) Guardrails: Stop when the goal is verifiably met, or stop after 15 iterations, whichever comes first. Keep changes minimal and never touch files outside the task’s scope.
qualitymedium risk