pr-writer

Standardize GitHub pull request titles, descriptions, and issue references with Sentry conventions.

905|47|Updated Jan 5, 2026
One-click install
npx skills add https://github.com/getsentry/skills --skill pr-writer-getsentry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-writer
Source: https://github.com/getsentry/skills/tree/main/skills/pr-writer
Command: npx skills add https://github.com/getsentry/skills --skill pr-writer-getsentry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PR creation and descriptions often lack consistency, making reviews slower and harder to track. This skill enforces Sentry’s PR conventions to standardize titles, bodies, and issue references across all PRs.

Core Features & Use Cases

  • Enforces PR title and description formats to align with Sentry engineering practices.
  • Automatically references related issues and tickets to improve traceability.
  • Integrates with GitHub workflows to streamline PR creation and updates.

Quick Start

Run the PR writer workflow when creating or updating a pull request to ensure titles, descriptions, and issue references follow Sentry conventions.

Frequently Asked Questions about pr-writer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize pull request titles and descriptions for GitHub workflows?

Standardize pull request writing by enforcing consistent PR titles, descriptions, and issue references during creation or updates. This ensures PR messaging aligns with engineering conventions directly within your GitHub workflow.

Do I need GitHub CLI to automate PR writing conventions?

Yes, GitHub CLI (gh) access is required to automate PR writing conventions. You must also commit your changes before opening a pull request to ensure the workflow processes the latest code state.

What is the best way to automatically reference related issues in a pull request?

Automatically reference related issues and tickets in a pull request by running a PR writer workflow. This standardizes issue traceability by enforcing consistent referencing formats across all PRs.

Can I use a PR writer to update existing pull requests to follow Sentry conventions?

Yes, you can use the PR writer when creating, updating, or drafting pull requests. It ensures titles, descriptions, and issue references follow Sentry conventions across diverse GitHub update scenarios.

Why does inconsistent PR formatting make code reviews slower?

Inconsistent PR creation and descriptions lack standardization, making reviews slower and harder to track. Enforcing PR conventions for titles and bodies streamlines the review process and improves traceability.

Are there limitations when enforcing Sentry PR conventions across different repositories?

Enforcing Sentry PR conventions requires adherence to the specific repository's PR guidelines. The workflow standardizes titles and issue references but is limited by the prerequisite of committing changes before opening a PR.