Review My Diff

Self-review uncommitted or branch changes before a PR, with findings ranked by severity and backed by file and line evidence. Use when asked to review my changes or check my diff.

Git & Code Review Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add agentkitco/agentkit-dev-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add agentkitco/agentkit-dev-skills --skill review-my-diff
Manual install
git clone --depth 1 https://github.com/agentkitco/agentkit-dev-skills.git /tmp/agentkit-dev-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agentkit-dev-skills/skills/review-my-diff ~/.claude/skills/review-my-diff

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Review my diff before a human does

Goal: catch the problems a reviewer would catch, in order of how much they matter. You are reviewing, not rewriting: do not edit files unless asked.

## Steps

1. **Get the change.** Run `git status --short`, then `git diff` (unstaged) and `git diff --staged`. For a branch, find the base (`git merge-base HEAD origin/main` or the default branch) and run `git diff <base>...HEAD`. If the diff is huge, review it by directory and say so.
2. **State the intent** in one sentence, inferred from commit messages, branch name or the user's request. If you cannot tell, ask once.
3. **Read the whole diff, then the code around risky hunks** (callers, tests, config). A diff hides what it did not touch.
4. **Check in this order:**
   1. Correctness: wrong conditions, off-by-one, null/empty cases, error paths, concurrency, resource cleanup.
   2. Safety: input validation, auth checks, secrets, injection, destructive operations, migrations that lock or lose data.
   3. Tests: does a test fail without this change? Are the new branches covered? Any test that asserts nothing?
   4. Compatibility: public API, config, database, file formats, callers outside this repo.
   5. Maintainability: dead code, copy-paste, unclear names, debug leftovers (`console.log`, `print`, `TODO`, commented code).
   6. Scope: unrelated edits that should be a separate PR.
Read the full skill on GitHub

Details

Skill name
review-my-diff
Path
skills/review-my-diff/SKILL.md
License
MIT
Repo updated
12 November 2026

FAQ

What does the Review My Diff skill do?

Self-review uncommitted or branch changes before a PR, with findings ranked by severity and backed by file and line evidence. Use when asked to review my changes or check my diff.

How do I install the Review My Diff skill?

Claude Code plugin: /plugin marketplace add agentkitco/agentkit-dev-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Related skills

Agents Md Audit

agentkitco/agentkit-dev-skills

Audit an AGENTS.md, CLAUDE.md, Cursor rule or Copilot instructions file for stale commands, broken paths, vague rules, secrets and contradictions. Use to review or trim agent instructions.

AI, LLMs & AgentsIn 1 list

Brag Doc From Git

agentkitco/agentkit-dev-skills

Build an evidence-based brag doc or self-review draft from your merged PRs and commits, leaving visible gaps where results are unknown. Use for review season, promotion cases or resumes.

Git & Code ReviewIn 1 list

Dependency Upgrade

agentkitco/agentkit-dev-skills

Upgrade one dependency at a time by reading its changelog, planning for breaking changes, updating code and proving it still builds and passes. Use to bump, update or migrate a package.

Git & Code ReviewIn 1 list

PR Description

agentkitco/agentkit-dev-skills

Write a pull request title and description from the actual diff and commits, with what changed, why, how it was tested and what to review. Use when asked to write or improve a PR description.

Git & Code ReviewIn 1 list

Report

danybgoode/golden-frijoles

Posts a project report to a chat destination, at the cadence asked for. Daily: a delta-only standup of overnight signals across every repo the project spans (opened/merged PRs and CI, the latest browser smoke, BUILD-ORDER drift, open-PR state, stale previews). Weekly: an executive recap/retro (merged PRs, shipped epics, deploys per app repo, a retro digest). PMO: the weekly operational report with scrum/DORA/doc-ops metrics and a story deck, or the on-demand monthly stakeholder packet with a metrics sheet. Use when the product owner asks to "post the standup", "run the daily standup", "what ha

Git & Code ReviewIn 1 list

Build Order Sync

danybgoode/golden-frijoles

Regenerates Roadmap/00-ideas/BUILD-ORDER.md when it has drifted from the SSOT (each epic README's frontmatter status:) and opens a claude/ docs PR with the fix — never hand-edits the board. Use when the product owner asks to "sync the build order", "regenerate BUILD-ORDER.md", "check board drift", "is the build-order board stale", "open a build-order PR", or as the nightly ops routine's first step. Runs scripts/build-order-sync.mjs, which does the check, the regen, and (on real drift) the branch/commit/ push/PR — this skill just invokes it and reports the result.

Git & Code ReviewIn 1 list

Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.