Automated PR review · on your machine
A review request shouldn't wait for you.
When someone requests your review on GitHub, Engwire automatically runs your review skill in Claude Code on your machine, against a revision it pins before it starts.
curl -fsSL https://engwire.com/install.sh | shYour machine · Your Claude Code · Your review skill · Your GitHub account · MIT
requested
maria requested your review
acme/checkout #482
picked up
Engwire picked it up
pinned at 4a91c2e
reviewing
Your review skill is running
in your Claude Code · on your machine
feedback
Review posted as you
through your gh
Example · 09:41 → 09:45 · 4 minutes
The request is the trigger.
No notification to notice, no command to remember — and the author has something to work from while the pull request waits for you.
Your review, not the team's bot.
Shared standards don't require one shared bot. Each request runs the skill and Claude Code configuration of the person it names, so review policy stays with the reviewer.
acme/checkout #482
Same pull request, different reviewers
Maya
Skill
security-review
auth · trust boundaries · data exposure
Maya's machine · Claude Code
Anton
Skill
api-review
contracts · compatibility · failure modes
Anton's machine · Claude Code
Jo
Skill
frontend-review
accessibility · UX · browser behaviour
Jo's machine · Claude Code
The request names who. Engwire picks it up. You decide how.
Share one skill across the team, or let each reviewer own theirs.
What Engwire does between the request and the review.
01 · GitHub
A request names you
A review request addressed to you is the trigger. Every event produces one run and at most one agent invocation, so a request is never reviewed twice.
- repo
- acme/checkout #482
- event
- review_requested
- reviewer
- @you
02 · Engwire
The revision is pinned
The head seen on the poll that claimed the run, and nothing moves it for the twenty minutes the review may take. Engwire clones its own copy; it never operates in your checkouts.
- claimed
- 4a91c2e
- worktree
- 4a91c2e
- head now
- 9d3f0b1
03 · Your Claude Code
Your configuration runs it
Engwire starts Claude with your user settings and nothing else. A CLAUDE.md, settings file, project skill or .mcp.json in the branch is inert.
- flag
- --setting-sources user
- skill
- security-review
- branch
- config inert
04 · Your GitHub account
Your skill can post as you
The skill decides whether to post at all. When it does, it goes through your authenticated
gh— there is no Engwire identity on your repository.- posts as
- @you
- through
- your gh
- engwire
- no account
Engwire owns the run. Your skill owns the review.
- Engwire owns the run
- the request · the exact revision · one run, once
- Your skill owns the review
- what Claude reads · what it says · whether it posts
The boundary
A contributor's branch does not get to configure your machine.
The code under review was written by somebody else and can carry instructions of its own. Every boundary below is enforced rather than advised.
Code is input. Control stays yours.
| Contributor branch | Your machine | |
|---|---|---|
| code · diff | reaches | Claude Code |
| CLAUDE.md · .mcp.json | does not reach | not loaded |
| hooks · filters | does not reach | never run |
| a fork's branch | does not reach | never checked out |
Your Claude configuration onlyAn inert checkoutAbsolute program pathsNo Engwire credential, and nothing listening
This is a control boundary, not a sandbox. A pull request can still attempt to influence the model in its own source, so give your skill the narrowest allowed-tools that does its job. Read the trust model →
What still leaves the machine
Engwire talks to GitHub through your own gh, and Claude Code sends what your skill reads to Anthropic. No Engwire service receives your source, no bot account is created, and there is no second credential to your repositories to revoke.
Run one review before you leave it running.
Nothing is reviewed until you name a repository, and nothing happens unattended until you ask for it. These four end in one review you watched happen, in your own terminal.
01 — Check the machine
engwire setupRecords the absolute paths of your
ghand your Claude Code, and lists the skills it found that a rule could actually name.02 — Choose a review skill
npx skills add engwire/skills --skill engwire-review -g -a claude-code -yThe binary ships with none, on purpose.
engwire-reviewcomments instead of blocking a merge, never runs the code it reviews, and approves only where the pull request has asked for it.03 — Name one repository
~/.config/engwire/config.toml[[review]] repos = ["acme/checkout"] skill = "engwire-review"One rule is enough to start. First match wins, so a narrower rule goes above this one.
04 — Watch one review
engwire run --onceOne poll, at most one review, then exit.
In your terminal, where you can read what it did. Nothing is left running when it ends.
It ignores the requests already waiting. Engwire starts watching from your first configured run, so the request sitting in your queue now is not the one to expect back — run it once, then ask again. The whole decision, in the order it is made →
Then decide whether to leave it running.
The service does what you just watched, on a timer. This is the whole of what it asks of the machine.
- One review at a time
- Additional requests wait their turn.
- Every minutedefault
- How often GitHub is asked for review requests.
- 20 minutesdefault
- Review timeout, taking its process group with it.
- 24 hoursdefault
- How long a finished checkout is kept.
On your machine
- Your Claude Code
- The allowance it is already authenticated with, and no Engwire account.
- Local storage
- Its own clone of each repository reviewed, and not reclaimed. How it was measured →
When you're ready
engwire service installAnd back off again: engwire uninstall lists the service, the data and the config it put on this machine, and deletes none of it without --yes.
Point it at one repository and see what it does.
Install Engwire, name one repository, and run one review in your terminal. Leave it running only when you're ready.
curl -fsSL https://engwire.com/install.sh | shmacOS 13+ · Linux · gh 2.31+ · Claude Code
When the rest of the company needs to know
Engwire runs on your machine and answers to you. Engwire for teams is a separate hosted product that tells the people outside engineering what shipped.
Pre-launch