pr-draft-summary_skill

Overview

This skill produces a ready-to-paste PR title and draft description when substantive code work is complete. It collects repository state, infers the change type and impact, and emits a concise PR block that matches this repo's conventions. Use it when finishing moderate-or-larger changes touching runtime, tests, build config, or docs with behavioral impact.

How this skill works

The skill inspects the git branch, working tree, staged/unstaged/untracked files, and commits ahead of the base fork point to determine what changed. It classifies the change (feature, fix, refactor, or docs-with-impact), assesses backward-compatibility risk for runtime edits, summarizes top file paths and diff stats, suggests a branch name, and drafts a PR title and description using the repository's template. If no relevant changes are detected it reports that and skips the PR block.

When to use it

• You finished a change that touched runtime code, tests, examples, or build/test configuration.
• You updated docs that may affect behavior or developer experience.
• You have staged or committed work and are about to mark the task ready for review.
• You want a concise, repo-compliant PR title and description without composing it manually.

Best practices

• Run the skill after committing or staging all intended work so summaries reflect final state.
• Keep commits focused; the skill uses commit messages when the working tree is clean but commits are ahead of base.
• Prefer short, descriptive top-level file paths — the summary highlights the top five touched paths.
• If changes touch runtime code, add a short compatibility note in the description — the skill flags risk but you should review details.
• If you want a specific branch name, create it first; otherwise accept the suggested kebab-case branch based on the change.

Example use cases

• Finishing a new feature that adds a runtime package and example — generate a 'feat/...' branch name and feature PR text.
• Wrapping up a bug fix that updates tests and a package file — produce a 'fix/...' title and description that explains the bug and fix.
• Refactoring core helper modules across multiple packages — produce an 'improves' style description and highlight potential compatibility notes.
• Updating documentation that changes agent behavior examples — produce a docs-with-impact PR draft that calls out behavior changes.