comprehensive-review-pr-enhance
Generates structured, reviewer-friendly pull request summaries from git diffs, including checklists and risk assessments.
Install
mkdir -p .claude/skills/comprehensive-review-pr-enhance && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/5229" && unzip -o skill.zip -d .claude/skills/comprehensive-review-pr-enhance && rm skill.zipInstalls to .claude/skills/comprehensive-review-pr-enhance
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
You are a PR optimization expert specializing in creating high-quality pull requests that facilitate efficient code reviews. Generate comprehensive PR descriptions, automate review processes, and ensure PRs follow best practices for clarity, size, and reviewability.Key capabilities
- →Generates structured summaries from git diffs
- →Categorizes PR changes into source/test/config/docs
- →Creates context-aware reviewer checklists
- →Flags high-risk files or large code diffs
- →Calculates rollback instructions for changes
How it works
It executes git diff statistics to categorize changed files and applies conditional template logic to generate relevant review artifacts.
Inputs & outputs
When to use comprehensive-review-pr-enhance
- →Generate a PR summary from a large diff
- →Add a testing checklist to a feature branch
- →Identify breaking changes before merging
- →Document code changes for peer review
About this skill
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
- Run
git diff <base>...HEAD --statto identify changed files and scope - Categorise changes: source, test, config, docs, build, styles
- Generate the PR description using the template below
- Add a review checklist based on which file categories changed
- Flag breaking changes, security-sensitive files, or large diffs (>500 lines)
PR Description Template
## 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
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.
Evidence and helper limits
Use the repository’s existing PR template and scale the description to the actual diff; do not invent metrics, tests, performance gains, rollback safety or issue intent. These Python fragments are incomplete sketches: status/category/impact/dependency/coverage/AI helper functions are absent, so no automated review result exists until implemented and run. Bind base/head SHAs and compare compatible coverage from the same tool/configuration and scope in isolated checkouts; unavailable coverage is unknown, not zero. Risk averages, line-count thresholds and review-time estimates are arbitrary advisory heuristics and cannot override a specific severe finding or required review. The fixed architecture diagram is illustrative, not inferred evidence. Diff-line positions need Git hunk mapping and renamed/deleted/binary-file handling; regex matches and file-name categories are not security analysis. Split branches must originate from the agreed base rather than successively cherry-picking onto branches already containing all changes. Drafting descriptions does not authorize branch pushes, PR creation, comments, reviews or merges; apply the user’s actual authorized action and repository rules.
When not to use it
- →Small trivial commits that do not require PR description structure
- →Very large refactors requiring manual architectural summaries
Prerequisites
Limitations
- →Requires high-quality commit messages to infer intent effectively
- →May flag false-positive risks on complex but safe changes
How it compares
It automates the creation of a standardized, reviewer-friendly PR document tailored to the specific type of changes present.
Compared to similar skills
comprehensive-review-pr-enhance side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| comprehensive-review-pr-enhance (this skill) | 1 | 7mo | Review | Beginner |
| resolve-conflicts | 81 | 12mo | Review | Intermediate |
| dependency-upgrade | 26 | 8mo | Review | Intermediate |
| git-commits | 21 | 7mo | No flags | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by sickn33
View all by sickn33 →You might also like
resolve-conflicts
antinomyhq
Use this skill immediately when the user mentions merge conflicts that need to be resolved. Do not attempt to resolve conflicts directly - invoke this skill first. This skill specializes in providing a structured framework for merging imports, tests, lock files (regeneration), configuration files, and handling deleted-but-modified files with backup and analysis.
dependency-upgrade
wshobson
Manage major dependency version upgrades with compatibility analysis, staged rollout, and comprehensive testing. Use when upgrading framework versions, updating major dependencies, or managing breaking changes in libraries.
git-commits
bonny
Create well-structured git commits in logical chunks following best practices
git-advanced-workflows
wshobson
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
github-multi-repo
ruvnet
Multi-repository coordination, synchronization, and architecture management with AI swarm orchestration
git-workflow-enforcer
CrazyDubya
Ensures commits follow conventional commits, branch naming conventions, and PR templates. Use when creating commits, branches, or PRs, or when user mentions git workflow.