skills.rest
zebbern
zebbernCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

pr-writer

Draft GitHub pull request descriptions following Sentry conventions.

5|3|Updated Apr 10, 2026
Search Tags:#github#pr#sentry#code-review#pull-request#descriptions
One-click install
npx skills add https://github.com/zebbern/termstack --skill pr-writer-zebbern
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-writer
Source: https://github.com/zebbern/termstack/tree/main/.github/skills/pr-writer
Command: npx skills add https://github.com/zebbern/termstack --skill pr-writer-zebbern

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PRs often lack standardized titles and descriptions, causing inconsistent reviews and slower triage. This skill enforces Sentry conventions for PR wording and issue references to improve clarity and consistency across projects.

Core Features & Use Cases

  • Enforces standardized PR titles and descriptions according to Sentry guidelines.
  • Validates that changes are committed, the branch is up to date, and the PR title/description references related issues.
  • Generates a structured PR body with context, links, and reviewer-friendly details.
  • Integrates with GitHub CLI to draft and create PRs using standardized templates.

Quick Start

Describe the changes in your branch and I will generate a compliant PR title and description following 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 generate a GitHub pull request description that follows Sentry conventions?▼

To generate a Sentry-convention pull request description, the skill analyzes your committed branch changes and automatically drafts a standardized PR title and body with required issue references for GitHub.

What does it mean for a pull request to follow Sentry standards?▼

Following Sentry standards means your pull request enforces standardized titles, structured descriptions, and explicit issue references to improve review clarity and triage consistency across GitHub projects.

Do I need to authenticate the GitHub CLI before creating a standardized PR?▼

Yes, you need the GitHub CLI (gh) to be authenticated before drafting a pull request. The skill validates your branch state and uses the authenticated CLI to output and create the structured PR description.

Can I use this to format a pull request description before submitting it?▼

Yes, this applies to all PR lifecycles including create, open, and submit. It validates that changes are committed and your branch is up to date before outputting a well-structured PR description ready for creation.

Why does my pull request need to reference related issues for code review?▼

Referencing related issues in a pull request provides necessary context links for reviewers. This skill validates that your PR title and description explicitly include these issue references to enforce Sentry wording guidelines.

What is the best way to automate formatting GitHub PR titles and descriptions?▼

The best way to automate PR formatting is to analyze the commit history on your branch and use a template that enforces Sentry conventions, generating a structured PR body with reviewer-friendly context and links.

Related Skills

Explore More Software Engineering Skills→
dioerdendioerden

merge-pr

Squash merge GitHub Pull Requests and clean up the worktree.

Community
Intermediate
assertchrisassertchris
2

custom-submit-pr

Create a GitHub pull request with the gh CLI and assign it to assertchris.

Community
Intermediate
Nabilhassan12345Nabilhassan12345

pr-description

Update GitHub PR descriptions from commits and diffs.

Community
Intermediate
shwilliamsonshwilliamson

pr-writing

Format pull request titles and bodies with standardized templates.

Community
Basic