multiAI Summary Pending
code-review-excellence
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.
231 stars
Installation
Claude Code / Cursor / Codex
$curl -o ~/.claude/skills/code-review-excellence/SKILL.md --create-dirs "https://raw.githubusercontent.com/aiskillstore/marketplace/main/skills/sickn33/code-review-excellence/SKILL.md"
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/code-review-excellence/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How code-review-excellence Compares
| Feature / Agent | code-review-excellence | Standard Approach |
|---|---|---|
| Platform Support | multi | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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.
Which AI agents support this skill?
This skill is compatible with multi.
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
# Code Review Excellence Transform code reviews from gatekeeping to knowledge sharing through constructive feedback, systematic analysis, and collaborative improvement. ## Use this skill when - Reviewing pull requests and code changes - Establishing code review standards - Mentoring developers through review feedback - Auditing for correctness, security, or performance ## Do not use this skill when - There are no code changes to review - The task is a design-only discussion without code - You need to implement fixes instead of reviewing ## Instructions - Read context, requirements, and test signals first. - Review for correctness, security, performance, and maintainability. - Provide actionable feedback with severity and rationale. - Ask clarifying questions when intent is unclear. - If detailed checklists are required, open `resources/implementation-playbook.md`. ## Output Format - High-level summary of findings - Issues grouped by severity (blocking, important, minor) - Suggestions and questions - Test and coverage notes ## Resources - `resources/implementation-playbook.md` for detailed review patterns and templates.