pr-draft-summary

Generate PR-ready titles and draft descriptions from Git changes.

Updated Jan 29, 2026
One-click install
npx skills add https://github.com/NovaAI-innovation/Infinite-Agency --skill pr-draft-summary-novaai-innovation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-draft-summary
Source: https://github.com/NovaAI-innovation/Infinite-Agency/tree/main/.qwen/skills/pr-draft-summary
Command: npx skills add https://github.com/NovaAI-innovation/Infinite-Agency --skill pr-draft-summary-novaai-innovation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of a PR-ready summary block, including a title and draft description, after substantive code changes are completed.

Core Features & Use Cases

  • Automated Summary Generation: Creates a concise summary of code changes, a suggested branch name, and a draft PR title and description.
  • Change Classification: Infers change type (feature, fix, refactor, docs) and flags backward-compatibility risks.
  • Use Case: After finishing a set of bug fixes and refactoring in the src/agents/ directory, this Skill can generate the necessary PR text to submit for review.

Quick Start

Use the pr-draft-summary skill to generate a PR summary for the current changes.

Frequently Asked Questions about pr-draft-summary

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

FAQPage Schema
How do I generate a PR summary for code changes in a Git repository?

You can generate a PR summary by using this Skill to analyze Git branch status, staged and unstaged files, and commit history relative to a base reference, producing a draft title and description for your code changes.

What is the best way to automate pull request title and description creation?

Automating pull request creation involves analyzing commit history and file changes to infer the change type, flag backward-compatibility risks, and output a structured PR summary block with a title and description.

Does this PR summary tool require specific Git commands to analyze branch status?

Yes, generating the PR summary requires Git commands to analyze branch status, staged, unstaged, and untracked files, along with commit history relative to a base reference to draft the description.

Can I classify change types like features or fixes when drafting a PR description?

Yes, the PR summary generation infers the change type, such as feature, fix, refactor, or docs, and flags backward-compatibility risks while drafting the title and description for your code review.

When should I use an automated PR draft summary for my code review?

You should use an automated PR draft summary when wrapping up moderate-to-larger changes in runtime code, tests, build configurations, or documentation that have a behavioral impact on your repository.

What limitations exist when generating PR summaries for untracked Git files?

The PR summary generation works for substantive code changes but relies on Git commands to analyze untracked files and branch status, requiring a valid base reference to accurately draft the description.