skills.rest
pqem
pqemCOMMUNITY
Explore all skills by this author →
GitHub

pr

Generate standardized pull request titles and bodies via GitHub CLI.

Updated Aug 27, 2026
Search Tags:#git#workflow#formatting#pr#code-review#pull-request
One-click install
npx skills add https://github.com/pqem/agent-automatizado --skill pr-pqem
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/pqem/agent-automatizado/tree/main/templates/skills/generic/pr
Command: npx skills add https://github.com/pqem/agent-automatizado --skill pr-pqem

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pull requests often lack a consistent format, causing confusion, slower reviews, and reduced traceability.

Core Features & Use Cases

  • Enforce a standardized PR title format (type(scope): description) to align with common commit conventions.
  • Provide a reusable PR body template with sections like What changed, Why, and How to test.
  • Integrate with CLI tools (e.g., gh pr create) to streamline PR creation within CI/CD pipelines.
  • Use case: teams require uniform PRs across multiple repositories to speed reviews and improve auditability.

Quick Start

Create a PR with a standardized title and body for the current branch using the GitHub CLI.

Frequently Asked Questions about pr

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

FAQPage Schema
How do I enforce a consistent pull request format for my Git workflow?▼

You can standardize PR titles and bodies using a structured template with sections like What changed, Why, and How to test. This enforces a consistent pull request format, which speeds up code reviews and improves traceability across software projects.

Can I automate pull request creation with the GitHub CLI to speed up code review?▼

Yes, you can automate pull request creation by invoking the gh pr create command via CLI. This integrates standardized PR titles and descriptions directly into your CI/CD pipelines, streamlining PR creation and accelerating the review process.

What is the best way to structure a PR title for automated formatting?▼

The best way to structure a PR title for automated formatting is using the type(scope): description convention. This aligns with common commit conventions, ensuring your pull requests maintain a uniform structure that is easily traceable during code reviews.

Does standardized PR formatting work across multiple repositories?▼

Yes, standardized PR formatting works across multiple repositories. By applying uniform title conventions and reusable body templates, teams can generate pull requests with a consistent structure, improving auditability and review speed across diverse software projects.

Why do my pull requests lack a consistent format and how does this affect code review?▼

Pull requests lack a consistent format when no standardized title and body template is enforced. This causes confusion, slower reviews, and reduced traceability, making it difficult for teams to maintain quality during feature development and bug fixes.

Related Skills

Explore More Software Engineering Skills→
0r0loo0r0loo

Git Skill

Enforce standardized Git commit formats, branch naming, and PR templates.

Community
Intermediate
vince-winkintelvince-winkintel
43

glab-mr

Manage GitLab merge requests for creation, review, approval, and merging.

Community
Intermediate
robhowleyrobhowley
5

open-pr

Generate pull request titles and descriptions from conventional commit messages.

Community
Intermediate
auldsyababuaauldsyababua
6

pr-backlog-cleaner

Triage, rebase, and verify GitHub pull requests for safe disposition.

Community
Advanced