PR Description Generator

The problem

Developers often write vague or incomplete pull request descriptions that force reviewers to hunt through the diff for context. This slows down the review cycle and leaves a poor trail of documentation in the project history.

What it does

• Identifies the correct conventional commit type (feat, fix, refactor, docs) from rough notes.
• Generates concise, 70-character titles using the type(scope): description format.
• Drafts a structured body including motivation, a bulleted list of changes, and testing notes.
• Includes risk assessments or rollback notes for broad structural changes.

Why this beats prompting it yourself

General-purpose prompts often produce overly verbose "fluff" or forget the conventional commit structure. This skill enforces strict scannability and prevents the use of vague terms like "updates" or "misc," ensuring every PR meets a high professional standard without manual editing.

Use cases

• Generating a PR draft immediately after finishing a local feature branch.
• Standardizing PR quality across a distributed engineering team.
• Explaining the "why" behind complex refactors for future maintainers.

Known limitations

It cannot invent test results or verify if a test passed; it only documents the testing process provided in the input.