comprehensive-review-pr-enhance
An expert tool for creating high-quality, reviewable pull requests with clear documentation.
Install
mkdir -p .claude/skills/comprehensive-review-pr-enhance-comeonoliver && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/13152" && unzip -o skill.zip -d .claude/skills/comprehensive-review-pr-enhance-comeonoliver && rm skill.zipInstalls to .claude/skills/comprehensive-review-pr-enhance-comeonoliver
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
- →Analyze code diffs to identify intent and scope
- →Summarize changes, tests, and risks
- →Highlight breaking changes and rollout notes
- →Add checklists and reviewer guidance
- →Generate complete PR descriptions
How it works
The skill analyzes a code diff to identify its intent and scope, then summarizes changes, tests, and risks. It highlights breaking changes and rollout notes, and adds checklists and reviewer guidance.
Inputs & outputs
When to use comprehensive-review-pr-enhance
- →Write PR descriptions
- →Summarize code changes
- →Create review checklists
- →Identify breaking changes
About this skill
Pull Request Enhancement
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.
Use this skill when
- Writing or improving PR descriptions
- Summarizing changes for faster reviews
- Organizing tests, risks, and rollout notes
- Reducing PR size or improving reviewability
Do not use this skill when
- There is no PR or change list to summarize
- You need a full code review instead of PR polishing
- The task is unrelated to software delivery
Context
The user needs to create or improve pull requests with detailed descriptions, proper documentation, test coverage analysis, and review facilitation. Focus on making PRs that are easy to review, well-documented, and include all necessary context.
Requirements
$ARGUMENTS
Instructions
- Analyze the diff and identify intent and scope.
- Summarize changes, tests, and risks clearly.
- Highlight breaking changes and rollout notes.
- Add checklists and reviewer guidance.
- If detailed templates are required, open
resources/implementation-playbook.md.
Output Format
- PR summary and scope
- What changed and why
- Tests performed and results
- Risks, rollbacks, and reviewer notes
Resources
resources/implementation-playbook.mdfor detailed templates and examples.
When not to use it
- →There is no PR or change list to summarize
- →A full code review is needed instead of PR polishing
Limitations
- →Cannot perform a full code review
- →Requires a PR or change list to summarize
- →Limited to tasks related to software delivery
How it compares
This skill automates the creation of detailed PR descriptions and reviewer guidance, unlike manual PR creation.
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) | 0 | 4mo | No flags | Beginner |
| deepwiki-rs | 25 | 9mo | Review | Intermediate |
| python-code-style | 9 | 6mo | Review | Intermediate |
| code-review-excellence | 19 | 5mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by ComeOnOliver
View all by ComeOnOliver →You might also like
deepwiki-rs
sopaco
AI-powered Rust documentation generation engine for comprehensive codebase analysis, C4 architecture diagrams, and automated technical documentation. Use when Claude needs to analyze source code, understand software architecture, generate technical specs, or create professional documentation from any programming language.
python-code-style
wshobson
Python code style, linting, formatting, naming conventions, and documentation standards. Use when writing new code, reviewing style, configuring linters, writing docstrings, or establishing project standards.
code-review-excellence
wshobson
Master effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing review standards, or mentoring developers.
code-walk-thru
pchalasani
Use this when user wants you to walk through (code or text) files in a EDITOR to either explain how some code works, or to show the user what changes you made, etc. You would typically use this repeatedly to show the user your changes or code files one by one, sometimes with specific line-numbers. This way the user is easily able to follow along in their favorite EDITOR as you point at various files possibly at specific line numbers within those files.
cookbook-audit
anthropics
Audit an Anthropic Cookbook notebook based on a rubric. Use whenever a notebook review or audit is requested.
schema-markup
davila7
When the user wants to add, fix, or optimize schema markup and structured data on their site. Also use when the user mentions "schema markup," "structured data," "JSON-LD," "rich snippets," "schema.org," "FAQ schema," "product schema," "review schema," or "breadcrumb schema." For broader SEO issues, see seo-audit.