# AI use cases for First Pass (joetawil7/first-pass) Repo: [joetawil7/first-pass](https://github.com/joetawil7/first-pass) | Use cases: 4 | Page: https://dedupedai.com/use-cases/joetawil7-first-pass/ first-pass is a set of rules, skills and checks for coding agents that makes them review the code around a change, prove their work, and fix bugs as a class. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Check your own branch before asking for review: https://dedupedai.com/use-cases/joetawil7-first-pass/review-own-branch-before-pr/ - Fix a bug and every same-pattern copy in one pass: https://dedupedai.com/use-cases/joetawil7-first-pass/fix-bug-across-the-class/ - Answer ten pre-code questions before writing a feature: https://dedupedai.com/use-cases/joetawil7-first-pass/ten-questions-before-feature-code/ - Run faster checks on a small change: https://dedupedai.com/use-cases/joetawil7-first-pass/quick-checks-on-small-change/ ## How to check your own branch before asking for review with First Pass Repo: [joetawil7/first-pass](https://github.com/joetawil7/first-pass) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Run First Pass review on your branch to catch unproven problems before a teammate sees the pull request. **Who it is for:** A developer with a finished branch who wants it checked before opening or requesting a pull request review. **The problem:** Reviews by people catch problems late, and an agent's own review of its own work tends to miss the same mistakes it made. **The outcome:** A list of findings, each with its proof or marked unproven, plus what the merge needs. Nothing is posted to GitHub. ### Steps 1. Run `/plugin marketplace add joetawil7/first-pass` in Claude Code. 2. Run `/plugin install first-pass@first-pass`. 3. In the folder where you start your sessions, run `/first-pass:setup-first-pass`. 4. Check out your branch in the repo, then run `/first-pass:review` with nothing after it. 5. Read each finding. Check any finding marked unproven before you fix it. ### Prompt to paste into your agent ```text In the repo, check out branch and run /first-pass:review with nothing after it. Expected output: a list of findings, each with its proof or marked unproven, and what the merge needs. Verify that nothing was posted to GitHub. ``` ### Caveat The review reads GitHub and never posts, but whether a finding is real depends on the proof the agent gives, so unproven findings still need your own check. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/joetawil7-first-pass/review-own-branch-before-pr/ ## How to fix a bug and every same-pattern copy in one pass with First Pass Repo: [joetawil7/first-pass](https://github.com/joetawil7/first-pass) | Difficulty: Intermediate | Time: 45 minutes | Basis: From the README Reproduce a bug, find the same pattern across the task's scope, and add a check that stops it returning. **Who it is for:** A developer who has found one bug and suspects the same mistake exists in other code paths that touch the same data. **The problem:** Patching one spot leaves the same pattern in neighboring code, and the lesson is lost in the next session. **The outcome:** A reproduction, the bug class named, every same-pattern hit in scope fixed or recorded, and a new check that catches the class. ### Steps 1. Complete the install and setup steps from `/plugin install first-pass@first-pass` and `/first-pass:setup-first-pass`. 2. Run `/first-pass:fix-the-class` followed by a short description of the bug and how to reproduce it. (inferred, check the README) 3. Read the list of same-pattern hits the agent found in the task's scope. 4. Check that the new helper, constraint or test fails on the old code before you accept the fix. ### Prompt to paste into your agent ```text In the repo, use fix-the-class on this bug: . Expected output: a reproduction, the bug class name, every same-pattern hit in the task's scope with its fix or record, and the check added. Verify that the new check fails against the code before the fix. ``` ### Caveat The search covers the task's scope only, so use hulk when you want the whole codebase searched, and the README says the scope is set from your prompt and the code around it. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/joetawil7-first-pass/fix-bug-across-the-class/ ## How to answer ten pre-code questions before writing a feature with First Pass Repo: [joetawil7/first-pass](https://github.com/joetawil7/first-pass) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Have the agent answer ten questions against the real code before it writes a feature. **Who it is for:** A developer about to start a feature where retries, outside services, endings or shared data could break things. **The problem:** Feature requests that say 'be 100% sure' change how confident the answer sounds but do not make the agent check the other code that writes the same data. **The outcome:** Each of the ten questions answered with a file and line, a test, or a named gap you accept. ### Steps 1. Complete the install and setup steps from `/plugin install first-pass@first-pass` and `/first-pass:setup-first-pass`. 2. Run `/first-pass:premortem` followed by your feature request before the agent writes any code. (inferred, check the README) 3. Read each answer. Accept a gap only when you decide to, since each gap is recorded as Not handled, because a reason. 4. Approve the code only after the answers match the real code. ### Prompt to paste into your agent ```text In the repo, run premortem on this feature: . Expected output: ten answers covering running twice, stopping halfway, outside service failure, neighbors, endings, money, hostile users, words, scale and time, each as file:line, a test, or Not handled. Verify that each file:line points to code that exists. ``` ### Caveat The questions run against code the agent can read, so answers are only as good as the repo's own files and the setup section written for it. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/joetawil7-first-pass/ten-questions-before-feature-code/ ## How to run faster checks on a small change with First Pass Repo: [joetawil7/first-pass](https://github.com/joetawil7/first-pass) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Switch to quick mode so a small change runs only the checks it can affect. **Who it is for:** A developer making a small, contained change who does not need the full CI run on every edit. **The problem:** Running the full CI suite on every small change is slow, but a change still needs proof that it does not break what it touches. **The outcome:** The change runs format, lint, types, build, its own tests, and every test that reaches what it touched. The rest is left for a full run. ### Steps 1. Complete the install and setup steps from `/plugin install first-pass@first-pass` and `/first-pass:setup-first-pass`. 2. Run `/first-pass:quick` to turn quick mode on. 3. Make your change and run the checks through the ship-check flow. 4. Run `/first-pass:quick off` to return to full CI checks before the final merge. ### Prompt to paste into your agent ```text In the repo, run /first-pass:quick, make the change described here: , then run ship-check. Expected output: a report listing each check run and its result, and which checks were left for a full run. Verify that the report says which CI checks were not run. ``` ### Caveat Quick mode leaves the rest of the suite for a full run such as your pull request's CI, so a change is not fully proven until that run passes. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/joetawil7-first-pass/quick-checks-on-small-change/