Lead Gen Jay/AI Systems
Insiders Exclusive
Automated
AI System · Code Review + Merge Gate + GitHub ActionsV1

Merges the safe pull requests. Stops the dangerous ones.

Claude reviews every pull request your team opens, inside GitHub Actions, fails the check when it finds a real defect, merges the clean ones without you, and holds anything that touches the files you marked dangerous until you approve it.

See What It Builds
  • Fails the check on real defects
  • Merges clean pull requests for you
  • Stops on billing, auth, and migrations
  • Runs on your own Claude key
  • Lives in GitHub Actions, no server to run
Claude CodeSetting up
>

Set up Backseat Developer on this repo. Review every pull request, block anything that touches billing or auth until I approve it, and merge the clean ones on your own.

I will connect to GitHub, read how this repo is built, mark the files that should never merge without you, store your Claude key as a repo secret, install the review workflow, then prove it works on a test pull request before I make it required.

  1. Connect your GitHub accountSigning you in and checking what this repo actually lets me change
  2. Read how the repo is builtFinding the default branch, the stack, and the checks you already run
  3. Mark the dangerous filesListing every path that should never merge without a human: billing, auth, migrations, CI
  4. Install the reviewerStoring your Claude key as a repo secret, then writing the review workflow into your own repo
  5. Prove it on a test pull requestOpening a throwaway PR and watching the reviewer run, comment, and return a verdict
  6. Hand it the merge buttonMaking the review required, then letting clean work on safe files merge itself
Message Claude Code...
What it does

Stop being the only thing between a bad pull request and production

Every other AI reviewer leaves a comment and leaves the decision to you. This one holds the merge button. It fails the check on real defects, merges the clean work on its own, and refuses to move on the files where a mistake costs money.

The old way

Reading every diff yourself

  • Read every pull request line by line, or merge it and hope.
  • Review bots leave comments that nobody is required to act on.
  • A green CI run proves the tests passed, not that the change is safe.
  • A one-line copy fix waits on you exactly as long as a database migration.
  • The one pull request that touches billing looks exactly like the other nine.
The new system

A reviewer that can hold the merge button

  • Claude reads the diff in GitHub Actions and fails the required check when it finds a real defect.
  • Clean pull requests on safe files merge themselves, so small work stops waiting on you.
  • Anything touching the paths you marked dangerous stops until you approve that exact commit.
  • Re-reviews read only what changed since the last round, so you never pay for the whole diff twice.
  • It runs on your own Claude key. Your code goes to Anthropic to be reviewed and nowhere else.
The review runs in GitHub Actions, so it works while your laptop is closed. Setup checks what your repo and GitHub plan allow, turns on everything they support, and tells you plainly what they do not.
  • GitHub
  • Claude Code
WHAT'S INSIDE

EVERYTHING PACKED INTO THE AI SYSTEM

This isn't a prompt you paste. It's the workflow, the rules, and the setup that put a reviewer with a veto in front of your main branch.

  1. THE REVIEW WORKFLOW

    The GitHub Actions workflow that reads each diff, returns a verdict, and reports it as a check your branch protection can require.

  2. THE DANGEROUS PATHS

    The rules that decide which files stop for a human, written to match your stack during setup and yours to edit after.

  3. THE REVIEWER PROMPT

    The instructions that tell Claude what counts as a blocking defect and what is only worth a comment, so it stops arguing about style.

  4. TERMINAL COMMANDS

    Five of them: open the pull request and merge it when the gate clears, fix what the review found, ship it to users, close the session, and get caught up in plain English when you have lost the thread. None of them can merge past the gate.

  5. GUIDED SETUP

    A walkthrough that connects GitHub, stores your key, installs the workflow, and proves it works on a throwaway pull request before you trust it.

Members only

Install Backseat Developer inside AI Automation Insiders

Built from the review system Jay runs across his own production repos, rebuilt to install on yours in one sitting. Comes with the other practical AI systems he uses for acquisition, ads, follow-up, and conversion work.

Related systems inside the membership
Join AI Automation Insiders