skills.rest
ComplianceAsCode
ComplianceAsCodeOFFICIAL
Explore all skills by this author →
GitHub

draft-pr

Generate pull request descriptions from branch commits and PR templates.

2.8k|817|Updated Apr 29, 2014
Search Tags:#automation#templates#draft#pull-request#pr-description#commit-analysis#branch-history
One-click install
npx skills add https://github.com/ComplianceAsCode/content --skill draft-pr-complianceascode
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: draft-pr
Source: https://github.com/ComplianceAsCode/content/tree/main/.claude/skills/draft-pr
Command: npx skills add https://github.com/ComplianceAsCode/content --skill draft-pr-complianceascode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Draft PR descriptions are automatically generated from the current feature branch's commit history and the project's PR template, reducing manual drafting time and ensuring consistency across PRs.

Core Features & Use Cases

  • Automatic generation of PR descriptions from commits since branching point
  • Adherence to the project's PR template to ensure consistent formatting
  • Deterministic generation with MCP tooling when available; fallback to filesystem-based analysis if MCP is not configured
  • Supports use cases such as feature branch reviews, release prep, and team-wide PR standardization

Quick Start

Create a PR description for the current feature branch by analyzing commits since the branching point and applying the project PR template.

Frequently Asked Questions about draft-pr

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

FAQPage Schema
How do I automatically generate a pull request description from branch commits?▼

You can generate pull request descriptions automatically by analyzing the commit history since the branching point and applying the repository's PR template. This ensures consistent formatting and reduces manual drafting time for feature branch reviews.

What is the best way to standardize PR content across a software project?▼

Standardizing PR content is achieved by automatically drafting pull request descriptions that strictly adhere to the project's PR template. This enforces consistent formatting across all feature branches and release preparations without manual formatting effort.

Do I need MCP tooling configured to draft PR descriptions from branch history?▼

You do not need MCP tooling configured to draft PR descriptions. The generation uses deterministic logic with MCP tooling when available, and automatically falls back to filesystem-based commit analysis if MCP is not configured.

Can I use filesystem-based analysis to prepare PR descriptions for release prep?▼

You can use filesystem-based analysis to prepare PR descriptions for release prep and feature branch reviews. When MCP tooling is absent, the system automatically falls back to analyzing the branch's commit history directly from the filesystem.

How does commit analysis work when generating PR descriptions from a feature branch?▼

Commit analysis for PR generation works by examining the commit history from the current feature branch back to its branching point. It extracts the relevant changes and maps them into the project's PR template for a structured description.

Related Skills

Explore More Software Engineering Skills→
kangmominkangmomin
1

commit-pr-hd

Automate commit, branch creation, and pull request workflows on repositories.

Community
Advanced
assertchrisassertchris
2

custom-submit-pr

Create a GitHub pull request with the gh CLI and assign it to assertchris.

Community
Intermediate
Taketo-YodaTaketo-Yoda
4

pr

Create pull requests after passing formatting, linting, and test checks.

Community
Advanced
rserse
44

ase-meta-commit

Generate a concise commit message from `git diff --cached` output.

Community
Basic