skills.rest
Aias
AiasCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

pr-guidelines

Standardize GitHub pull request titles, descriptions, and base-branch guidance.

Updated Nov 26, 2025
Search Tags:#workflow#documentation#github#code-review#pull-request#pr-guidelines
One-click install
npx skills add https://github.com/Aias/dotfiles --skill pr-guidelines-aias
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-guidelines
Source: https://github.com/Aias/dotfiles/tree/main/agents/skills/pr-guidelines
Command: npx skills add https://github.com/Aias/dotfiles --skill pr-guidelines-aias

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual PR drafting leads to inconsistent titles, vague descriptions, and misaligned base branches, slowing reviews and increasing churn.

Core Features & Use Cases

  • Standardized PR title and body formats to improve clarity.
  • Base-branch guidance and review-scoped prompts to reduce misdiffs.
  • Coordinated steps for opening, editing, and updating PRs across workflows.

Quick Start

Draft a PR with a clear title and description following these guidelines.

Frequently Asked Questions about pr-guidelines

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

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

To standardize GitHub pull request titles and descriptions, apply enforced style rules and coordinated drafting prompts to ensure consistent formatting, reduce drift, and clarify review scope across workflows.

What is the best way to reduce code review time for pull requests?▼

The best way to reduce code review time is to standardize pull request metadata, enforce clear title and body formats, and provide base-branch guidance to prevent misdiffs and align reviewer expectations.

Can I update existing PR descriptions or only use guidelines for new pull requests?▼

You can update existing PR descriptions as well as draft new ones. The guidelines support opening, editing, and refreshing pull request metadata across GitHub workflows to maintain consistency.

How do I prevent misaligned base branches when opening a GitHub pull request?▼

To prevent misaligned base branches when opening a GitHub pull request, follow base-branch guidance rules that coordinate branch targeting and reduce review-scoped misdiffs.

Why do manual pull request drafts slow down GitHub code reviews?▼

Manual pull request drafts slow down GitHub code reviews because inconsistent titles, vague descriptions, and misaligned base branches increase churn and require additional clarification before merging.

Does this PR workflow guideline require any external code review dependencies?▼

No external code review dependencies are required. The guidelines operate independently to enforce pull request formatting, base-branch guidance, and coordinated drafting prompts within GitHub workflows.

Related Skills

Explore More Software Engineering Skills→
showcase-gig-platformshowcase-gig-platform
4

create-pr

Create GitHub pull requests with conventional commit titles and detailed bodies.

Official
Advanced
taloncjonestaloncjones

ship

Automate code review, testing, version bump, merge, and post-merge cleanup for pull requests.

Community
Advanced
magicpro97magicpro97
8

merge-when-green

Automatically merge GitHub pull requests after all required CI checks pass.

Community
Intermediate
doanchienthangdevdoanchienthangdev
4

finishing-development-branches

Enforce quality gates, clean Git history, and prepare pull requests.

Community
Intermediate