PR Writer

Write, scope, size, and review pull requests that are fast and safe to review and merge. Grounded in Google's Engineering Practices, GitHub's PR guidance, the SmartBear/Cisco review study, Conventional Commits, LLVM's AI tool policy and agentic-PR research, plus delivery practice (expand/contract migrations, flags, observability gates). Covers splitting and sizing, Conventional-Commit titles, a stand-alone description (what/why, Mermaid diagrams of only what changed: Example Mapping for a policy, Event Storming for a process, sequence for an interaction, contracts crossed, confidence card, tes

5 stars 2 forksGit & Code Review Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add vnovakovits/claude-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 vnovakovits/claude-skills --skill pr-writer
Manual install
git clone --depth 1 https://github.com/vnovakovits/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/plugins/engineering-practices/skills/pr-writer ~/.claude/skills/pr-writer

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

From the SKILL.md

# Writing Pull Requests

A pull request is a **request for someone else's time** and a **permanent entry in the project's history**. Optimize for the reviewer and for the engineer who reads `git log` in two years — not for the writer. The central test: **can a reviewer learn what changed, why, and where the risk is, without opening the diff or the ticket — and review it in one sitting?**

## Core Philosophy

- **The reviewer is the customer.** Their time and attention are the scarce resource. Every choice — size, title, description, read-order — should reduce their cognitive load.
- **Small, focused, single-concern.** The strongest predictor of a fast, effective review is a small, single-purpose diff. Almost every other problem (slow reviews, missed defects, scope arguments) traces back to a PR that did too much.
- **The description is the contract and the story.** It states intent and the edges crossed; the diff shows the mechanism. A reviewer should be able to validate the diff *against* the description.
- **Self-review first.** Read your own diff hunk-by-hunk as if it were someone else's before you request review. Most "review comments" are things you'd have caught yourself.
- **Ship when it improves code health.** Perfect is the enemy of merged. Approve (and request merge of) a change that definitely improves the codebase, even if it isn't ideal — file follow-ups for the rest.

---

## 1. One Concern Per PR (the splitting rule)
Read the full skill on GitHub

Details

Skill name
pr-writer
Path
plugins/engineering-practices/skills/pr-writer/SKILL.md
License
MIT
Repo updated
16 November 2026

FAQ

What does the PR Writer skill do?

Write, scope, size, and review pull requests that are fast and safe to review and merge. Grounded in Google's Engineering Practices, GitHub's PR guidance, the SmartBear/Cisco review study, Conventional Commits, LLVM's AI tool policy and agentic-PR research, plus delivery practice (expand/contract migrations, flags, observability gates). Covers splitting and sizing, Conventional-Commit titles, a stand-alone description (what/why, Mermaid diagrams of only what changed: Example Mapping for a policy, Event Storming for a process, sequence for an interaction, contracts crossed, confidence card, tes

How do I install the PR Writer skill?

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

Is PR Writer popular?

It lives in vnovakovits/claude-skills, which has 5 GitHub stars and 2 forks.

Related skills

Accidental Cio

5

vnovakovits/claude-skills

Apply Scott Millett's "The Accidental CIO — A Lean and Agile Playbook for IT Leaders" (Wiley, 2024) when designing or reviewing how a technology organisation decides, funds, governs and delivers work. Covers the five components of an adaptive IT operating model (organised, work, govern, talent, lead) and its four themes (outcomes over output, intrinsic motivation, being not doing agile, manage flow not people); matching method and governance to context via Cynefin and Wardley evolution; governance as demand management + funding + measurement + decision rights, shifting from project funding to

Frontend & Design

Agent Retro

5

vnovakovits/claude-skills

Run a retrospective on a coding-agent session and improve the agent's environment, not the code. Combines Derby & Larsen's five-stage retrospective, Shigeo Shingo's poka-yoke (turn a mechanical mistake into a check that makes it impossible), and Matt Pocock's retro categories — navigation, automated checks, coding standards, steering files, tool economy, information access. Covers mining the session transcript for corrections, wrong turns and slow searches; deciding where each fix belongs (analyzer, hook, CI, reviewer standards, CLAUDE.md pointer, skill, doc or memory); the no-op test for stee

AI, LLMs & Agents

API Design

5

vnovakovits/claude-skills

Design APIs that are clear, evolvable, and idiomatic to their protocol — covering REST (Fielding, Richardson Maturity Model, Massé), GraphQL, gRPC/protobuf, versioning strategies, pagination, error responses (RFC 7807 Problem Details), idempotency, authentication, documentation (OpenAPI), and the pragmatic trade-offs between RESTful purity and developer ergonomics. Use when designing a new endpoint, choosing between REST/GraphQL/gRPC, defining versioning, structuring error responses, deciding pagination strategy, or evaluating an existing API's evolvability.

Software Development

Receiving Code Review

8

Freddy-CHEN-ux/00_claude_skills

Use when processing code review feedback. Technical evaluation of feedback, verify before implementing. No performative agreement or gratitude.

Git & Code Review

PR Feedback Training First Loop

8

Freddy-CHEN-ux/00_claude_skills

Extract, learn, and integrate PR feedback into the Violet brain

Git & Code Review

Requesting Code Review

8

Freddy-CHEN-ux/00_claude_skills

Use when completing tasks or major features. Know when and how to request reviews. Provides git commit range to code-reviewer agent.

Git & Code Review

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