draft-pr

Generate a conventional commit title and markdown PR description from a git branch diff.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/deneb-cygnus-dev/dot-agent --skill draft-pr-deneb-cygnus-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: draft-pr
Source: https://github.com/deneb-cygnus-dev/dot-agent/tree/main/skills/draft-pr
Command: npx skills add https://github.com/deneb-cygnus-dev/dot-agent --skill draft-pr-deneb-cygnus-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of Pull Request titles and descriptions, streamlining the code review process and ensuring consistent commit messaging.

Core Features & Use Cases

  • Conventional Commits: Generates PR titles adhering to the Conventional Commits specification.
  • Structured Descriptions: Creates detailed PR descriptions including Summary, Changes, and Test Plan sections.
  • Direct Creation or Local Draft: Can either create the PR directly using gh pr create or save the draft to a local file.
  • Use Case: After completing a feature, run this Skill to automatically generate a well-formatted PR title and description based on your branch's commits, then create the PR with a single command.

Quick Start

Use the draft-pr skill to create a pull request for the current branch.

Frequently Asked Questions about draft-pr

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

FAQPage Schema
How do I generate a pull request description from my git diff?

To generate a pull request description from your git diff, this Skill analyzes the current branch's commits against main and outputs a structured markdown summary with Changes and Test Plan sections.

Can I create a GitHub pull request with a conventional commit title automatically?

Yes, you can create a GitHub pull request with a conventional commit title automatically. The Skill formats the PR title according to the Conventional Commits specification and executes creation directly via the gh cli.

Does the draft-pr Skill require the GitHub CLI to create pull requests?

The GitHub CLI is required for direct PR creation, but you can alternatively save the generated conventional commit title and markdown description to a local file without using the gh command.

What is the best way to automate conventional commit formatting for code review?

The best way to automate conventional commit formatting for code review is using a Skill that parses branch diffs to generate standardized PR titles and structured descriptions, streamlining the entire review process.

Can I save a pull request draft to a local file instead of pushing it to GitHub?

You can save a pull request draft to a local file instead of pushing it to GitHub. The Skill outputs the generated markdown description and conventional commit title locally for review before submission.