AI toolkit · free download
You cannot read every pull request a model opens
Paste the diff and the ticket. Get a triage of what to read line by line, and comments that hold up.
The AI pull request review pack is a free prompt pack for reviewing code a model generated. Paste the ticket, the description and the diff into any AI assistant. You get a file triage, comments ordered by what matters, and a note of what it could not check.
Who this is for
- Engineering managers and tech leads reviewing code they did not write.
- Staff engineers who became the default reviewer for anything AI-generated.
- Anyone merging model-written code where a quiet mistake gets expensive.
Before you download. This pack runs in your environment, on your data. Nothing is sent to Perform, and Perform receives no data from it at any point. It is provided free and as is, with no warranty of any kind. It is not legal, tax, security or accounting advice, not an audit and not an attestation, and no professional relationship is created by downloading or using it. You are responsible for reviewing it before you run it and for any decision you make with its output. Licensed under Apache-2.0, which includes a disclaimer of warranties and a limitation of liability.
Anything you point it at should be treated as untrusted input, because a document, a repository or a chat thread can carry instructions aimed at a model.
Version 1.0, 28 August 2026. Security contact: privacy@totalperform.com, acknowledged within five business days.
A markdown file. Paste it into any assistant. Nothing to install.
The same pack, installed once and there every time.
The problem
- Four open before standup, three of them mostly generated. You skim, and the one that mattered is the one you skimmed.
- Generated code invents calls that read perfectly and do not exist.
- It shifts a boundary by one inside a loop that looks correct.
- It swallows an error the old path used to raise and hands the caller a success.
- Your checklist was written for human mistakes. It walks past all three.
What it does about it
- Triages every file: four buckets, and a count of the added lines you just committed to reading.
- Starts with the deleted lines: most quiet damage in a rewrite is in what was removed.
- Hunts ten failure modes: the ones generated code has and human code does not.
- Sorts findings four ways: including a bucket for scope creep, so it stops merging as a nitpick.
- Signs off on a scope: what was read, what was skimmed, what nobody could check.
Two minutes to first output
- Paste the pack into Claude, ChatGPT or Copilot.
- Add the ticket, the description and the diff.
- Read the triage first.
What it will not do
- Confirm a call exists without the imports or the repository. It lists what it could not check.
- Review what you did not paste. If the diff is elided it says so up front.
- Run your tests.
| What you paste | Ticket, pull request description, diff |
|---|---|
| What comes back | File triage, ordered comments, coverage note |
| Time | Under two minutes |
| Where it runs | Your assistant, on your machine |
| Tested against | A 29-line diff with nine planted defects. Four rounds of practitioner testing. |
30 minutes with the engineer who would do the work.