pr-draft-summary

Generates a PR-ready summary block with branch suggestion, title, and draft description from git changes.

Updated May 23, 2026
One-click install
npx skills add https://github.com/kiranimmadi2/promptforge-ai --skill pr-draft-summary-kiranimmadi2
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-draft-summary
Source: https://github.com/kiranimmadi2/promptforge-ai/tree/main/openai-agents-python/.agents/skills/pr-draft-summary
Command: npx skills add https://github.com/kiranimmadi2/promptforge-ai --skill pr-draft-summary-kiranimmadi2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After finishing substantive code work in the openai-agents-python repository, developers still need to manually write a PR title, description, and branch name. This Skill automates that final handoff step by inspecting the git working tree and producing a paste-ready pull request draft block. ## Core Features & Use Cases - Automatic Git Inspection: Collects branch name, staged/unstaged/untracked changes, diff stats, and commits ahead of the base fork point without asking the user. - Change Classification: Infers whether the work is a feature, fix, refactor, or docs change from touched paths, and flags backward-compatibility risk against the latest release tag. - Structured PR Output: Emits a Markdown block with a branch name suggestion, an imperative PR title, and a description starting with "This pull request <verb> ...", including auto-closing issue references for issue-<number> branches. - Use Case: After implementing a bug fix and running tests, invoke this Skill to instantly receive a complete PR draft block ready to paste into GitHub. ## Quick Start Use the pr-draft-summary skill to generate the PR-ready summary block, title, and draft description for my 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 pull request title and description automatically?

Run this Skill after completing code changes; it inspects git status, diffs, and commits ahead of the base branch, then outputs a Markdown block with a branch suggestion, imperative title, and a description beginning with "This pull request <verb> ...".

When should the PR draft summary be skipped?

Skip it for trivial or conversation-only tasks, repo-meta or doc-only changes without behavior impact, or when the user explicitly says not to include the PR draft block. It is the default final step only for substantive code work.

Does it handle untracked files in the git working tree?

Yes. It runs git ls-files --others --exclude-standard alongside git status -sb to surface untracked files, since git diff --stat does not include them, and explicitly calls them out in the summary.

How does it detect backward-compatibility risk?

It flags risk only when the diff changes released public APIs, external config, persisted data, serialized state, or wire protocols, judging against the latest release tag rather than unreleased branch-only churn.

What happens on branches named issue-<number>?

The branch suggestion is kept as-is, and the description references the corresponding GitHub issue URL with an auto-closing line such as "This pull request resolves #<number>." Issue context lookup is optional and non-blocking.