skills.rest
shwilliamson
shwilliamsonCOMMUNITY
Explore all skills by this author →
GitHub

pr-writing

Format pull request titles and bodies with standardized templates.

Updated Jan 4, 2026
Search Tags:#template#github#code-review#pull-request#pr-writing#title-formatting
One-click install
npx skills add https://github.com/shwilliamson/a-test --skill pr-writing
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-writing
Source: https://github.com/shwilliamson/a-test/tree/main/.automatasaurus/skills/pr-writing
Command: npx skills add https://github.com/shwilliamson/a-test --skill pr-writing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineers craft clear, effective pull request descriptions, improving reviewer understanding and approval times.

Core Features & Use Cases

  • Standardized Title Formatting: Enforce the required PR title format with issue number prefixes.
  • Structured PR Body: Provide templates for Summary, Changes, Testing, and Notes for Reviewers.
  • Use Case: When preparing PRs for features, bug fixes, documentation updates, this Skill guides consistent structure.

Quick Start

Use the pr-writing skill to draft a PR title and body for a hypothetical feature update.

Frequently Asked Questions about pr-writing

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

FAQPage Schema
How do I write a pull request description that gets approved faster?▼

To write a pull request that gets approved faster, use a structured PR body with templates for Summary, Changes, Testing, and Notes for Reviewers. Consistent PR formatting improves reviewer understanding and reduces approval times.

What is the best way to format GitHub pull request titles?▼

The best way to format GitHub pull request titles is to use a standardized title format with issue number prefixes. This enforces consistency across software development workflows and clearly links PRs to their corresponding issues.

How do I structure a PR body for a bug fix or feature update?▼

Structure a PR body for a bug fix or feature update by using templates for Summary, Changes, Testing, and Notes for Reviewers. This guides consistent structure and helps reviewers quickly understand the changes.

When do I need to include issue references in a pull request?▼

You need to include issue references in a pull request whenever you are preparing PRs for features, bug fixes, or documentation updates. Linking issues provides context and tracks the resolution across your software development workflow.

Can I use a PR template for both code review and documentation updates?▼

Yes, you can use a PR template for both code review and documentation updates. The template guides consistent structure for Summary, Changes, Testing, and Notes for Reviewers, ensuring clear communication across different types of pull requests.

Related Skills

Explore More Software Engineering Skills→
mvillmowmvillmow
18

gh-create-pr-linked

Create a GitHub pull request linked to a specified issue.

Community
Basic
mkalkeremkalkere
4

pr-complete

Verify GitHub PR readiness by checking approvals, CI status, mergeability, and notify humans via bus message.

Community
Advanced
gobikomgobikom
2

prp-issue-fix

Automate code issue resolution from artifact loading to PR creation.

Community
Advanced
robhowleyrobhowley
5

open-pr

Generate pull request titles and descriptions from conventional commit messages.

Community
Intermediate