pr-writer

Create and update GitHub pull requests following Sentry engineering conventions.

1|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/sergical/pi-config --skill pr-writer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-writer
Source: https://github.com/sergical/pi-config/tree/main/skills/pr-writer
Command: npx skills add https://github.com/sergical/pi-config --skill pr-writer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation and updating of pull requests, ensuring adherence to Sentry's engineering conventions for titles, descriptions, and issue referencing, thereby improving code review efficiency and consistency.

Core Features & Use Cases

  • Standardized PRs: Generates PR titles and descriptions following established commit message formats (feat, fix, ref).
  • Contextual Descriptions: Guides users to provide necessary motivation, alternatives, and context beyond the code diff.
  • Issue Linking: Facilitates easy referencing and closing of GitHub or Sentry issues.
  • Use Case: When you've finished a bug fix, invoke this skill to draft a PR that clearly explains the fix, links to the bug ticket, and uses the correct fix(scope): title format.

Quick Start

Use the pr-writer skill to create a draft pull request for your current changes.

Frequently Asked Questions about pr-writer

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

FAQPage Schema
How do I automate GitHub pull request creation?

To automate GitHub pull request creation, this Skill generates standardized titles and descriptive bodies based on your committed changes. It requires the GitHub CLI and follows established engineering conventions like feat, fix, and ref prefixes for consistent code review.

Does this PR writer require the GitHub CLI to create pull requests?

Yes, the GitHub CLI is required to create pull requests using this PR writer. It relies on the GitHub CLI to interact with your repository and assumes that your code changes are already committed locally before generating the standardized PR titles and descriptions.

How do I write a pull request description that follows engineering conventions?

To write a pull request description following engineering conventions, this Skill guides you to provide necessary motivation, alternatives, and context beyond the code diff. It enforces standardized commit message formats and links to relevant GitHub issues for clear communication.

What is the best way to link a GitHub issue when creating a pull request?

The best way to link a GitHub issue when creating a pull request is to use this Skill's issue linking feature. It facilitates easy referencing and closing of GitHub or Sentry issues directly within the generated PR body, ensuring proper tracking and standardized documentation.

Can I update an existing pull request with standardized titles and descriptions?

Yes, you can update an existing pull request with standardized titles and descriptions. This Skill automates both the creation and updating of GitHub pull requests, enforcing established engineering conventions for titles and descriptive bodies during the code review process.

Why does my pull request need a standardized title format like fix or feat?

Your pull request needs a standardized title format like fix or feat to improve code review efficiency and consistency. This Skill enforces these established engineering conventions for titles and descriptions, ensuring clear communication of changes across the development team.