pr

Generate structured pull request descriptions from commit context.

19|3|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/dirien/yet-another-agent-harness --skill pr-dirien
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/dirien/yet-another-agent-harness/tree/main/.claude/skills/pr
Command: npx skills add https://github.com/dirien/yet-another-agent-harness --skill pr-dirien

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating pull requests often results in inconsistent descriptions, making reviews harder and slowing down merges. This skill standardizes PR creation by producing clear, structured bodies that align with team guidelines.

Core Features & Use Cases

  • Structured PR templates that enforce consistent titles, summaries, and checklists.
  • Context-aware bodies generated from commit messages and branch context to save time during reviews.
  • Use Case: when coordinating changes across multiple contributors or repositories, generate uniform PRs that pass automated checks.

Quick Start

Generate a structured PR description for the current feature branch.

Frequently Asked Questions about pr

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

FAQPage Schema
How do I generate a structured pull request description from commit messages?

To generate a structured pull request description, the Skill analyzes your commit context and branch history to automatically populate consistent PR titles, summaries, and required checklists.

What is the best way to standardize pull request templates across multiple repositories?

Standardizing pull request templates across multiple repositories is achieved by enforcing uniform body sections, title length limits, and required review checks that align with your team workflows.

Can I enforce required review checks and title length limits for PR creation?

Yes, you can enforce required review checks and title length limits during PR creation to ensure descriptions meet team guidelines and pass automated checks before merging.

How does automated PR generation handle unsafe commands or data leakage?

Automated PR generation includes built-in safeguards against unsafe commands and data leakage, ensuring that structured descriptions are produced securely without exposing sensitive repository data.

Does this PR automation tool work with existing Git workflows and multiple branches?

Yes, this PR automation works across multiple branches and existing Git workflows, applying context-aware rules to maintain uniform PR standards regardless of the repository structure.