README

Free sample

What is in the pack, and the table of which passes a given change needs.

README.md · 1.9 KB

README.md

# Review & Repair

The prompt arsenal for the unglamorous half.

Writing new code is the easy half. This pack is the other half — the passes
you run on code that already exists, whether an agent wrote it or you did.

## Why single-purpose passes

Asking for "a code review" gets you a list that is 60% style opinions, 30%
things you already knew, and 10% real — and you cannot tell which is which,
so you read all of it.

Each prompt here looks for **one class of problem**. Run three of them and
you get three focused lists instead of one long ambiguous one. You also get
to choose: a UI change does not need the concurrency pass.

## What is here

    review/     Eleven single-purpose review passes
    debug/      A protocol that reproduces before it diagnoses
    refactor/   Changes with an explicit blast radius
    tests/      Backfill that targets behaviour, not coverage
    migration/  Library upgrades across a large codebase, file by file

## The rule that applies to all of them

**Run the review in a context that did not write the code.**

Self-review inside the implementing session is close to worthless — the
model has just spent an hour establishing that the implementation is right.
Fresh session, paste the diff, no history.

## Which passes to run

| Change | Passes |
|---|---|
| Any change | correctness, error-handling |
| Touches a database | data-access, migrations |
| Touches auth or user input | auth-boundaries, input-validation |
| Public API or client-facing | api-contract |
| Anything concurrent or async | concurrency |
| Frontend | frontend-state |
| Adds or upgrades a package | dependencies |
| Anything going to production | observability |

Two or three passes is normal. Running all eleven on a small change wastes
your attention, which is the scarce resource.

## Licence

Yours to use in any project, personal or commercial. Do not resell or
republish the files themselves.

That was one of 20 files

The rest of Review & Repair is written the same way. $29 once, yours permanently, 14-day refund.

# Review & Repair The prompt arsenal for the unglamorous half. Writing new code is the easy half. This pack is the other half — the passes you run on code that already exists, whether an agent wrote it or you did. ## Why single-purpose passes Asking for "a code review" gets you a list that is 60% style opinions, 30% things you already knew, and 10% real — and you cannot tell which is which, so you read all of it. Each prompt here looks for **one class of problem**. Run three of them and you get three focused lists instead of one long ambiguous one. You also get to choose: a UI change does not need the concurrency pass. ## What is here review/ Eleven single-purpose review passes debug/ A protocol that reproduces before it diagnoses refactor/ Changes with an explicit blast radius tests/ Backfill that targets behaviour, not coverage migration/ Library upgrades across a large codebase, file by file ## The rule that applies to all of them **Run the review in a context that did not write the code.** Self-review inside the implementing session is close to worthless — the model has just spent an hour establishing that the implementation is right. Fresh session, paste the diff, no history. ## Which passes to run | Change | Passes | |---|---| | Any change | correctness, error-handling | | Touches a database | data-access, migrations | | Touches auth or user input | auth-boundaries, input-validation | | Public API or client-facing | api-contract | | Anything concurrent or async | concurrency | | Frontend | frontend-state | | Adds or upgrades a package | dependencies | | Anything going to production | observability | Two or three passes is normal. Running all eleven on a small change wastes your attention, which is the scarce resource. ## Licence Yours to use in any project, personal or commercial. Do not resell or republish the files themselves.