Code review
Reviewing diffs and pull requests for defects, risk and missing tests.
Download all 25
- Review a pull request
Reviews a pull request diff for correctness bugs, risky changes and missing tests, and returns ranked findings. Use before merging a PR, branch or diff.
- Code reviewer
Reviews changes like a senior engineer who blocks only on real defects, backs every finding with a triggering input, and keeps style opinions out. Use as a reviewer persona or subagent.
- Grade my review comments
Grades the review comments a developer wrote on a real diff, showing which caught real defects, which were overstated nits, what was missed and how to phrase each better. Use to learn to review.
- Hunt planted bugs in a practice pull request
Presents a realistic practice pull request with planted defects such as an off-by-one, a race or a security hole, then scores the learner's review comments against them.
- Reply to a first-time contribution
Reviews a first-time contributor's pull request and drafts the reply that gets it merged or redirected without losing the person, with blocking items separated from optional ones. Use on any first PR.
- Respond to code review comments
Triages each review comment as fix, discuss or decline with a reason, drafts the replies, and applies the agreed fixes. Use when a pull request comes back with reviewer feedback.
- Review AI-generated code
Reviews code written by an AI assistant for hallucinated APIs, over-engineering, swallowed errors, weakened tests and copy-paste drift. Use before merging a change an agent produced.
- Review an API change for breaking changes
Reviews an API diff or spec for changes that break existing clients, such as removed fields, changed semantics, new defaults, error changes and versioning gaps. Use before releasing.
- Review a config-only change
Reviews YAML, JSON, env, feature flag or Helm values changes for blast radius, environment mix-ups, type and unit mistakes, missing rollback and validation gaps. Use when a config PR looks harmless.
- Review a dependency update PR
Reviews a bot dependency bump PR by reading the changelog range, flagging breaking and silent behaviour changes, lockfile churn and transitive jumps, and recommends merge, merge with checks or hold.
- Review a diff for concurrency bugs
Reviews a change for data races, lock ordering, missed awaits, check-then-act and cancellation leaks, naming the exact interleaving that breaks each finding. Use on concurrent or async code.
- Review a diff for shipping risks
Assesses what can go wrong when a change reaches production, such as broken contracts, unsafe migrations, rollout order and rollback, and proposes mitigations. Use before deploying a risky change.
- Review error handling
Reviews failure paths for swallowed errors, lost context, unsafe retries, missing timeouts and internal details leaking to users, with ranked fixes. Use on code that calls I/O or external services.
- Review a firmware diff
Reviews embedded C or C++ changes for ISR safety, missing volatile or atomics, stack use, blocking calls in timed paths, overflow, register order and watchdog use. Use on firmware PRs.
- Review a gameplay code change
Reviews game code for per-frame allocations, frame-rate dependent logic, physics in the wrong update, non-determinism that breaks netcode or replays, and editor-only assumptions. Use on gameplay PRs.
- Review a mobile app change
Reviews an iOS, Android, React Native or Flutter diff for main-thread work, lifecycle bugs, permissions, offline behaviour and compatibility with app versions already in the field. Use on mobile PRs.
- Review a data pipeline change
Reviews a change to a batch or streaming job, dbt model or ETL script for idempotency, backfill impact, late and duplicate data, schema drift and silent row loss. Use on data pipeline PRs.
- Review a UI component change
Reviews a frontend component PR for state ownership, re-render and effect hazards, missing loading, empty and error states, responsive and accessibility basics, and token use. Use on UI pull requests.
- Reword review comments
Rewrites vague, curt or sarcastic draft review comments into clear, kind, actionable ones with a label, the reason and a concrete proposal, keeping the technical point. Use before posting a review.
- Practise receiving a code review
Plays a demanding but fair reviewer on the learner's own code, one comment at a time, and coaches how they reply, push back or concede. Use to practise handling review feedback before a first job.
- Self-review a branch before opening a PR
Reviews your own branch the way a strict reviewer would, catches debug leftovers, unrelated changes, missing tests and leaked secrets, and runs the checks. Use before requesting review.
- Summarise a pull request discussion
Condenses a long pull request thread into decisions made, open questions with owners, outstanding requested changes and what blocks merge. Use when returning to or joining a long-running PR.
- Verify a PR meets its acceptance criteria
Checks a diff against its ticket's acceptance criteria one by one, marking each met, partly met, not met or untestable from the diff, with evidence lines and missing tests. Use before approving a PR.
- Walk a reviewer through a pull request
Explains a large or unfamiliar pull request to its reviewer with what changes and why, a reading order, the risky hunks and questions for the author. Use before reviewing a big diff.
- Write code review guidelines
Writes a team's code review guidelines covering what blocks a merge, comment labels, size limits, response times, author and reviewer duties and how to disagree. Use when setting review norms.
Not: security-only review (security); performance-only review (performance); reviewing prose (editing).