PR Self Review
Draft explanatory author-context comments for the user's own PR or local diff. Use for self-review or reviewer context, not a formal review submission. Posting requires approval.
Install
npx skills add petekp/claude-code-setup --skill pr-self-reviewgit clone --depth 1 https://github.com/petekp/claude-code-setup.git /tmp/claude-code-setup
mkdir -p ~/.claude/skills
cp -r /tmp/claude-code-setup/skills/pr-self-review ~/.claude/skills/pr-self-reviewPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# PR author context Draft notes that help a teammate understand changed behavior, affected callers, and non-obvious choices. This workflow authorizes inspection and drafting, not additional code changes or replies to teammates. Here, self-review means inspecting the author's own changes and explaining them to reviewers. Publish that context as standalone comments. Do not create or submit a grouped GitHub review, or issue an approval or request-changes verdict. For an existing PR, read [target and authorship](references/target.md) to verify the repository, open PR, author, and current head. When no PR exists, inspect the local diff and continue with private drafts. Read the diff, existing discussion, and affected consumers. Follow history or linked issues when needed to support a reason. Cover distinct reviewer questions across the meaningful changes; there is no required number or ceiling. A complex change may need several short notes, and a straightforward change may need none. Use [writing notes](references/writing-notes.md) when choosing or drafting explanations. Keep each note short, concrete, and supported. Do not invent the author's intent or speak as Pete personally. Flag a needed durable code comment separately unless its edit is already authorized. Distinguish the two comment formats: - **PR conversation comments:** ordinary comments in the PR conversation, with links to the relevant committed code. These are not attached to a review.
Details
- Skill name
pr-self-review- Repository
- petekp/claude-code-setup
- Path
skills/pr-self-review/SKILL.md- License
- MIT
- Repo updated
- 26 October 2026
FAQ
What does the PR Self Review skill do?
Draft explanatory author-context comments for the user's own PR or local diff. Use for self-review or reviewer context, not a formal review submission. Posting requires approval.
How do I install the PR Self Review skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add petekp/claude-code-setup --skill pr-self-review. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is PR Self Review popular?
It lives in petekp/claude-code-setup, which has 49 GitHub stars and 10 forks.
Related skills
Catch Up
49petekp/claude-code-setup
Give the human a fast, plain-English catch-up on what changed in the project: what the agents did, why, and what decisions need their input. Use when the user asks to "catch me up", "what changed", "where are we", "recap", "brief me", "give me the rundown", "what did you do", "summarize the session", or "fill me in", or otherwise wants to get back up to speed after being away.
Clean Copy
49petekp/claude-code-setup
Cut interface copy that should not exist. Captions that restate a label, hints that pre-empt a worry the user never had, warnings that are scar tissue from a fixed bug. Use when writing or reviewing any user-facing string (labels, hints, empty states, toasts, confirmations, button text), or when asked to clean up or tighten copy.
Code Comments
49petekp/claude-code-setup
Write, review, or remove code comments. Use when adding comments or doc comments, reviewing the comments in a diff, or cleaning up or removing comments.
Finishing a Development Branch
49sodiumjoe/dotfiles
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work
PR Screenshot Comparison
49petekp/claude-code-setup
Create clear, polished before-and-after screenshots from the actual running product for a GitHub pull request. Use when a UI change needs visual proof: capture matching product states, crop to the relevant UI, stitch and caption one comparison image, attach it natively to the PR, and keep the image out of the repository.
Neovim Review
49sodiumjoe/dotfiles
Use when the user invokes /neovim-review for a pull request or a local :Review session in Neovim.
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.