Senior engineer / reviewer

Pull request reviewer

Immediate result: A review ranked by severity: bugs first, then risks, then optional nits, each with a suggested fix.

Problem it solvesReviews either rubber-stamp a diff or drown it in style nits, and the real bugs get through.

Add this skill to

You paste

diff: adds if (user.role = 'admin') to the permissions check

You get

Verdict: request changes.

Blocker — line 42: = assigns instead of compares, so every user becomes admin. Use ===.

Test to add: a non-admin calling DELETE /users gets 403.

About this skill

About Pull request reviewer

Code review fails in two ways: rubber stamps and nit storms. This skill avoids both by checking the diff against what the change claims to do, then hunting for the problems that reach production — logic errors, unhandled failures, race conditions, security holes and missing tests. Findings are sorted into blockers, should-fix and at most three nits, each quoting the exact line and suggesting a change. It skips anything a formatter or linter would catch. Use it as a first pass before a human review, or to review your own pull request before you ask a colleague.

Pull request reviewer AI skill for Senior engineer / reviewer: you paste "diff: adds `if (user.role = 'admin')` to the permissions check" and get "Verdict: request changes."
Pull request reviewer — example input and the first lines it returns. Works in ChatGPT, Claude and Gemini.
Job profile
Software engineering · Senior engineer / reviewer
Works in
ChatGPT, Claude, Gemini, Copilot, Claude Code
Format
Agent Skills (SKILL.md)
Price
Free, no sign-up
Install instructions

Copy, paste, send

  1. Cold email writerCopy skillCopied ✓1 Copy the skillPress Copy skill.
  2. ANY AI ASSISTANTSKILLPaste here, then press Enter2 Paste it into a new chatChatGPT, Claude, Gemini or Copilot.
  3. ANY AI ASSISTANT3 Send your inputSend a code diff (git diff or the PR's changed files) and one line on what the change is meant to do.
The skill — paste this into your AI assistant
# Skill: Pull request reviewer

You are running the "Pull request reviewer" skill for me. I work as: Senior engineer / reviewer. What I need from you: a review ranked by severity: bugs first, then risks, then optional nits, each with a suggested fix.

## When I send you a code diff (git diff or the PR's changed files) and one line on what the change is meant to do
1. Check the diff does what the description says.
2. Look for correctness bugs, unhandled errors, race conditions, security issues and missing tests.
3. Rank findings: Blocker, Should fix, Nit.
4. Suggest a concrete change for every Blocker and Should fix.

## Reply in this format
- Summary verdict (approve / request changes)
- Blockers
- Should fix
- Nits (max 3)
- Tests to add

## Rules
- Quote the exact line for every finding.
- Don't report style issues a formatter or linter would catch.
- Use only the facts I give you; mark anything you had to assume with [ASSUMPTION].
- If something essential is missing, ask me one short question, then continue.
- No preamble or filler: start with the result.

Confirm you're ready in one line, then wait for me to send a code diff (git diff or the PR's changed files) and one line on what the change is meant to do.

Then sendA code diff (git diff or the PR's changed files) and one line on what the change is meant to do. For example: diff: adds `if (user.role = 'admin')` to the permissions check

ChatGPT

  1. Fastest: paste the skill as your first message in a new chat, then send your input.
  2. To keep it: open a Project, choose Instructions (or Settings → Personalization → Custom instructions for every chat) and paste it there.
  3. To share it with a team: create a custom GPT and paste the skill into its Instructions.
  4. In the Codex app: copy the skill's folder into ~/.codex/skills/ (or Customize → Skills → Add → Create skill).

Claude

  1. Fastest: paste the skill as your first message in a new chat, then send your input.
  2. To keep it: create a Project, open Project instructions and paste the skill.
  3. As a Claude Skill: download the skill's ZIP, then in Claude open Settings → Skills → Add → Upload skill and choose the file.

Gemini

  1. Fastest: paste the skill as your first message in a new chat, then send your input.
  2. To keep it: open Gems → New Gem, paste the skill into Instructions and save.

Microsoft Copilot

  1. Fastest: paste the skill as your first message, then send your input.
  2. In Microsoft 365 Copilot, save it as a prompt or paste it into an agent's instructions to reuse it.

Any other assistant

  1. Paste the skill as the system prompt or first message in any chat assistant (Perplexity, Meta AI, DeepSeek, Mistral, local models).
  2. Coding agents that read the Agent Skills format (SKILL.md) can load the downloaded file from their skills folder.

Install it permanently

Upload it to Claude, add it to ChatGPT's Codex app, clone it into Claude Code, or download the SKILL.md for any agent. Full guide with screenshots →

Download the ZIP and upload it in Claude. Claude then uses the skill on its own whenever a request matches.

Download ZIP

Quick setup

  1. In Claude, open Settings → Skills (under Customize).
  2. Click Add → Upload skill.
  3. Choose the ZIP — don't unzip it — and make sure the skill is switched on.
Claude Settings with Skills selected under Customize, and the Add menu open showing Upload skill, Create a skill, Create with Claude and Record your screen

Repositoryscienceofapps.com/skills/ai-skills.git · all 200 skills, one folder each, plain git over HTTPS

What it does

The steps it follows

  1. Check the diff does what the description says.
  2. Look for correctness bugs, unhandled errors, race conditions, security issues and missing tests.
  3. Rank findings: Blocker, Should fix, Nit.
  4. Suggest a concrete change for every Blocker and Should fix.
What you get back

The reply format

  • Summary verdict (approve / request changes)
  • Blockers
  • Should fix
  • Nits (max 3)
  • Tests to add

Rules it never breaks

  • Quote the exact line for every finding.
  • Don't report style issues a formatter or linter would catch.
  • Uses only the facts you give it and marks assumptions.
FAQs

Questions about Pull request reviewer

What does the Pull request reviewer skill do?

Reviews either rubber-stamp a diff or drown it in style nits, and the real bugs get through. The skill fixes that: a review ranked by severity: bugs first, then risks, then optional nits, each with a suggested fix.

How do I install Pull request reviewer in ChatGPT, Claude or Gemini?

Copy the skill and paste it as the first message of a new chat, then send your input. To keep it, paste it into a ChatGPT Project or custom GPT, a Claude Project or a Gemini Gem, or upload the SKILL.md file as a Claude Skill.

What do I send Pull request reviewer after installing it?

Send a code diff (git diff or the PR's changed files) and one line on what the change is meant to do. If something essential is missing, the skill asks you one short question and then continues.

Is the Pull request reviewer skill free?

Yes. It's free to copy, use and adapt, with no sign-up, and works in the free versions of ChatGPT, Claude, Gemini and Copilot.

More for software engineering
Software engineer

Unit test writer

ProblemWriting tests for existing functions is tedious, so edge cases go untested until they break in production.

You paste

Python: def slugify(title): return title.lower().replace(' ', '-') # pytest

You get

Covers: basic title, multiple spaces, leading/trailing spaces, punctuation, empty string, unicode.

def test_collapses_multiple_spaces(): assert slugify('a b') == 'a-b'

Suspected bug: 'a b' returns 'a--b' today.

Immediate resultA ready-to-run test file covering the happy path, edge cases and failures for your function.

Software engineer joining a codebase

Legacy code explainer

ProblemInherited code has no docs and the author left, so every change feels risky.

You paste

A 200-line PHP function processOrder() with nested ifs and three SQL queries

You get

What it does: validates a cart, charges the card, then writes the order — in that order, with no transaction.

Side effect: line 88 updates stock before payment succeeds.

Risky: a failed charge leaves stock reduced. Wrap lines 80–140 in a DB transaction.

Immediate resultA plain-English walkthrough of what the code does, its hidden side effects and where it's safe to change.

Developer / data engineer

Regex builder

ProblemRegular expressions are hard to write and harder to read, and one wrong character silently matches too much.

You paste

JavaScript: match Indian mobile numbers, optional +91, 10 digits starting 6–9

You get

/^(?:\+91[- ]?)?[6-9]\d{9}$/

[6-9] — first digit of Indian mobiles; \d{9} — nine more digits.

✓ +91 9876543210 · ✓ 9876543210 · ✗ 5876543210 · ✗ 98765 43210

Immediate resultA tested regex for your flavour, explained token by token, with matching and non-matching examples.

Free PDF · 74 pages · 2 editions

The Laws of UX, in one field guide

60 research-backed principles in 6 categories — what each one means, why it works on the human brain and how to use it on your own screens. Written by Sushant Singh, founder of Science of Apps, who has scaled consumer apps to lacs of users and spent 10+ years leading product across startups and digital businesses in the US, EU & India.

Pick your edition
Free. No card, no paywall — just your email.
Free PDF · 74 pages

Get Laws of UX by email

Choose your edition

You’ll also get occasional UX psychology tips. Unsubscribe anytime. Privacy policy

Free PDF · 90 pages · 2 editions

100+ Subscription Paywalls, decoded

110 real paywalls from top apps, taken apart, rated out of 5 and decoded with the Laws of UX — plus the frameworks, copy and checklists to ship your own. By Sushant Singh, founder of Science of Apps.

  • 110 paywalls rated
  • 34 Laws of UX
  • 12 frameworks

Which paywall scored 4.8 out of 5, and which scored 2.6? It’s all inside.

Pick your edition
Free. No card, no paywall — just your email.
Free PDF · 90 pages

Get 100+ Paywalls, Decoded by email

Choose your edition

You’ll also get occasional UX psychology tips. Unsubscribe anytime. Privacy policy