Enhance Pull Request Descriptions

This skill turns a git diff into a reviewer-friendly pull request description. It runs git diff <base>...HEAD --stat to identify changed files and scope, categorizes them into source, test, config, docs, build, or styles, and fills in a PR description template with a one-paragraph summary, a table of changes by category with the key change per file, a motivation section linking the originating issue, a testing checklist, and a risks-and-rollback section stating whether the change is breaking, how to roll it back, and a risk level with a stated reason - for example, a source row noting an added OAuth2 PKCE flow paired with a test row covering the token-refresh edge case, and a config row for a new environment variable. It then adds a review checklist tailored to which file categories actually appear in the diff, and flags breaking changes, security-sensitive files, or large diffs over 500 lines.

Use it when a git diff needs to become a reviewer-friendly PR description - a summary with change categories, risks, testing notes, and a checklist - especially once the diff is large enough that reviewers need explicit structure instead of a short ad hoc summary. When the diff exceeds 20 files or 1000 lines, it suggests splitting the PR by feature area into separate branches with git cherry-pick rather than pushing one oversized review.

Inputs: a git diff between a base branch and HEAD, obtained via git diff <base>...HEAD --stat. Outputs: a filled PR description (summary, a changes table by category, why, a testing checklist, risks and rollback), plus a review checklist assembled only from the categories present in the diff - source changes get checked for debug statements, function length under 50 lines, descriptive names, and error handling; test changes for meaningful assertions, edge cases, no flaky tests, and the AAA pattern; config changes for hardcoded secrets, documented env vars, and backward compatibility; docs changes for accuracy, examples, and changelog updates; and security-sensitive files (paths containing auth, crypto, token, or password) for input validation, no secrets in logs, and correct authorization.

Git (git diff --stat, git checkout -b, git cherry-pick), plus resources/implementation-playbook.md, which holds Python helpers for automated PR analysis, coverage reports, and risk scoring.

git diff <base>...HEAD --stat

Developers opening pull requests, or reviewers who want a large or unstructured diff turned into a categorized summary with a matching review checklist and risk assessment.