skills.rest
posiposi
posiposiCOMMUNITY
Explore all skills by this author →
GitHub

pr-template

Generate standardized pull request titles and bodies from issue details.

Updated Nov 15, 2025
Search Tags:#automation#template#standards#code-review#pull-request#gitHub#issue-tracker
One-click install
npx skills add https://github.com/posiposi/dragons-counter --skill pr-template
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-template
Source: https://github.com/posiposi/dragons-counter/tree/main/.claude/skills/pr-template
Command: npx skills add https://github.com/posiposi/dragons-counter --skill pr-template

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill defines a standard template and rules for creating PRs, ensuring consistent titles and bodies across teams and repos.

Core Features & Use Cases

  • PR Title Rules: Derive a clean, concise PR title from the related Issue description without including the issue number.
  • PR Body Template: Provide a structured body with sections such as Overview, Changes, and Tests, including a Closes line.
  • Usage Scenarios: Use when drafting PRs for features, fixes, or documentation updates to enforce uniform quality.

Quick Start

Use the pr-template skill to generate a PR title and body from issue details and a list of changes.

Frequently Asked Questions about pr-template

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

FAQPage Schema
How do I standardize pull request titles and bodies across my repository?▼

To standardize pull request titles and bodies, you can use a template skill that enforces title rules, such as excluding issue numbers and limiting length, while providing a structured body with Overview, Changes, and Tests sections. This ensures consistent PR quality across teams and repos.

What is the best way to generate a PR body from issue details?▼

The best way to generate a PR body from issue details is to use a standardized template that includes a Closes line and sections for Overview, Changes, and Tests. This validates that changes align with issue requirements and maintains uniform documentation.

Can I use a PR template for feature, bug fix, and documentation updates?▼

Yes, you can use a PR template for feature, bug fix, and documentation updates. The template operates across issues-based workflows, enforcing uniform title and body quality regardless of the specific PR scenario.

Why should I exclude issue numbers from my pull request titles?▼

You should exclude issue numbers from pull request titles to maintain a clean and concise naming convention. The template derives the title directly from the related issue description, ensuring clarity and consistency across the repository.

Does a PR template validate that code changes align with issue requirements?▼

Yes, a PR template validates that code changes align with issue requirements. It provides a structured body template that enforces documentation of changes and tests, ensuring the pull request directly addresses the issue's scope.

Related Skills

Explore More Software Engineering Skills→
sergicalsergical
1

pr-writer

Create and update GitHub pull requests following Sentry engineering conventions.

Community
Intermediate
duronextduronext
15

ticket

Create and route tickets across Linear, GitHub Issues, or Jira using jig.config.md.

Official
Intermediate
marcuskroghmarcuskrogh

setup

Generate a WORKSPACE.md file defining artifact roots and tracker integration settings.

Community
Intermediate
ulises-jeremiasulises-jeremias
2

dots-workstation-pr-fallback

Generate structured pull request bodies with YAML and Markdown placeholders.

Community
Intermediate