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.
Best use case
comprehensive-review-pr-enhance is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using comprehensive-review-pr-enhance should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/comprehensive-review-pr-enhance/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How comprehensive-review-pr-enhance Compares
| Feature / Agent | comprehensive-review-pr-enhance | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Pull Request Enhancement ## 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 ```markdown ## Summary <!-- one-paragraph executive summary: what changed and why --> ## Changes | Category | Files | Key change | |----------|-------|------------| | source | `src/auth.ts` | added OAuth2 PKCE flow | | test | `tests/auth.test.ts` | covers token refresh edge case | | config | `.env.example` | new `OAUTH_CLIENT_ID` var | ## Why <!-- link to issue/ticket + one sentence on motivation --> ## Testing - [ ] unit tests pass (`npm test`) - [ ] manual smoke test on staging - [ ] no coverage regression ## Risks & Rollback - **Breaking?** yes / no - **Rollback**: revert this commit; no migration needed - **Risk level**: low / medium / high — because ___ ``` ## 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: ``` git checkout -b feature/part-1 git cherry-pick <commits-for-part-1> ``` ## Resources - `resources/implementation-playbook.md` — Python helpers for automated PR analysis, coverage reports, and risk scoring
Related Skills
django-perf-review
Django performance code review. Use when asked to "review Django performance", "find N+1 queries", "optimize Django", "check queryset performance", "database performance", "Django ORM issues", or audit Django code for performance problems.
django-access-review
django-access-review
architect-review
Master software architect specializing in modern architecture
cc-skill-security-review
Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment/sensitive features. Provides comprehensive security checklist a...
vibers-code-review
Human review workflow for AI-generated GitHub projects with spec-based feedback, security review, and follow-up PRs from the Vibers service.
performance-testing-review-multi-agent-review
Use when working with performance testing review multi agent review
performance-testing-review-ai-review
You are an expert AI-powered code review specialist combining automated static analysis, intelligent pattern recognition, and modern DevOps practices. Leverage AI tools (GitHub Copilot, Qodo, GPT-5, C
error-debugging-multi-agent-review
Use when working with error debugging multi agent review
enhance-prompt
Transforms vague UI ideas into polished, Stitch-optimized prompts. Enhances specificity, adds UI/UX keywords, injects design system context, and structures output for better generation results.
lightning-architecture-review
Review Bitcoin Lightning Network protocol designs, compare channel factory approaches, and analyze Layer 2 scaling tradeoffs. Covers trust models, on-chain footprint, consensus requirements, HTLC/PTLC compatibility, liveness, and watchtower support.
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
receiving-code-review
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performat...