DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to check your own branch before asking for review with First Pass

Run First Pass review on your branch to catch unproven problems before a teammate sees the pull request.

Who it is forA developer with a finished branch who wants it checked before opening or requesting a pull request review.

The problemReviews by people catch problems late, and an agent's own review of its own work tends to miss the same mistakes it made.

The outcomeA list of findings, each with its proof or marked unproven, plus what the merge needs. Nothing is posted to GitHub.

What you need first

  • Claude Code to install the plugin (Cursor and Codex get the rules and skills, but hooks are Claude Code only)
  • A folder that holds your repos, where you start your sessions
  • Git repos with a branch to review, for the review use case (GitHub access is needed to read pull requests, inferred from the README)

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 for your agent

In the <repo-name> repo, check out branch <branch-name> 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.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page