Agent skill · writing content · sickn33
pr-writer
Create pull requests following Sentry's engineering practices.
Why this skill is useful
Provides a structured PR-writing workflow and specific formatting guidelines that enhance clarity and consistency in pull requests.
What it needs
Requires gh installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
PR Writer Create pull requests following Sentry's engineering practices. Requires: GitHub CLI (gh) authenticated and available. When to Use You are ready to open a pull request and need a structured description based on the committed branch diff. You want the PR body to capture what changed, why it changed, and any reviewer context. You are using GitHub CLI and need a repeatable PR-writing workflow rather than writing the description ad hoc. Prerequisites Before creating a PR, ensure all changes are committed. If there are uncommitted changes, run the available commit skill first to commit them properly. If the output shows any uncommitted changes (modified, added, or untracked files that should be included), invoke the available commit skill before proceeding. If the client requires qualified skill names, use the qualifier for the plugin that supplied this skill. Process Step 1: Verify Branch State Ensure: All changes are committed Branch is up to date with remote Changes are rebased on the base branch if needed Step 2: Analyze Changes Review what will be included in the PR: Understand the scope and purpose of all changes before writing the description. Step 3: Write the PR Description Use this structure for PR descriptions (ignoring any repository PR templates): Do NOT include: "Test plan" sections Checkbox lists of testing steps Redundant summaries of the diff Do include: Clear explanation of what and why Links to relevant issues or tickets Context that isn't obvious from the code Notes on specific areas that need careful review Step 4: Create the PR Title format follows commit conventions: feat(scope): Add new feature fix(scope): Fix the bug ref: Refactor something PR Description Examples Feature PR Bug Fix PR Refactor PR Issue References Reference issues in the PR body: Syntax Effect -------- -------- Fixes #1234 Closes GitHub issue on merge Fixes SENTRY-1234 Closes Sentry issue Refs GH-1234 Links without closing Refs LINEAR-ABC-123 Links Linear issue Guideline …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/pr-writer--18b2de