Agent skill · writing content · sickn33
comprehensive-review-pr-enhance
Generate structured PR descriptions from diffs, add review checklists, risk assessments, and test coverage summaries. Use when the user says "write a PR description", "improve this PR", "summarize my changes", "PR review", "pull request", or asks to document a diff for reviewers.
Why this skill is useful
Generates structured PR descriptions and checklists that streamline the review process, which the AI wouldn't reliably create on its own.
What it needs
About 2k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
Pull Request Enhancement When to Use You need to turn a git diff into a reviewer-friendly pull request description. You want a PR summary with change categories, risks, testing notes, and a checklist. The diff is large enough that reviewers need explicit structure instead of a short ad hoc summary. Workflow 1. Run git diff <base>...HEAD --stat to identify changed files and scope 2. Categorise changes: source, test, config, docs, build, styles 3. Generate the PR description using the template below 4. Add a review checklist based on which file categories changed 5. Flag breaking changes, security-sensitive files, or large diffs (>500 lines) PR Description Template Review Checklist Rules Add checklist sections only when the matching file category appears in the diff: File category Checklist items --------------- ---------------- source no debug statements, functions <50 lines, descriptive names, error handling test meaningful assertions, edge cases, no flaky tests, AAA pattern config no hardcoded secrets, env vars documented, backwards compatible docs accurate, examples included, changelog updated security-sensitive (auth, crypto, token, password in path) input validation, no secrets in logs, authz correct Splitting Large PRs When diff exceeds 20 files or 1000 lines, suggest splitting by feature area: Resources resources/implementation-playbook.md — Python helpers for automated PR analysis, coverage reports, and risk scoring Limitations Use this skill only when the task clearly matches the scope described above. Do not treat the output as a substitute for environment-specific validation, testing, or expert review. Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/comprehensive-review-pr-enhance--c2b2ad