Code Review Excellence

Code review excellence

by davila7 · MIT license · ★ 32,299 on GitHub

Code review excellence cover

Transform code reviews from gatekeeping to knowledge sharing through constructive feedback, systematic analysis, and collaborative improvement.

---
name: code-review-excellence
description: "Transform code reviews from gatekeeping to knowledge sharing through constructive feedback, systematic analysis, and collaborative improvement."
risk: safe
source: community
date_added: "2026-02-27"
---

# 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

Overview

Transform code reviews from gatekeeping to knowledge sharing through constructive feedback, systematic analysis, and collaborative improvement.

What you get

  • High-level summary of findings
  • Issues grouped by severity (blocking, important, minor)
  • Suggestions and questions
  • Test and coverage notes
Manual install (npx, ZIP)
Claude Codenpx skills add davila7/claude-code-templates --skill code-review-excellence -g -a claude-code
Claude Code (degit)npx degit davila7/claude-code-templates/cli-tool/components/skills/productivity/code-review-excellence#main ~/.claude/skills/code-review-excellence-davila7
Claude.ai / desktopZip the folder and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • SKILL.md1.4 KB
Read SKILL.md here
davila7/main1 file shown
SKILL.md
Show the full text44 lines
code-review-excellence-davila7/SKILL.md44 lines · 1.4 KB

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.
1---
2name: code-review-excellence
3description: "Transform code reviews from gatekeeping to knowledge sharing through constructive feedback, systematic analysis, and collaborative improvement."
4risk: safe
5source: community
6date_added: "2026-02-27"
7---
8 
9# Code Review Excellence
10 
11Transform code reviews from gatekeeping to knowledge sharing through constructive feedback, systematic analysis, and collaborative improvement.
12 
13## Use this skill when
14 
15- Reviewing pull requests and code changes
16- Establishing code review standards
17- Mentoring developers through review feedback
18- Auditing for correctness, security, or performance
19 
20## Do not use this skill when
21 
22- There are no code changes to review
23- The task is a design-only discussion without code
24- You need to implement fixes instead of reviewing
25 
26## Instructions
27 
28- Read context, requirements, and test signals first.
29- Review for correctness, security, performance, and maintainability.
30- Provide actionable feedback with severity and rationale.
31- Ask clarifying questions when intent is unclear.
32- If detailed checklists are required, open `resources/implementation-playbook.md`.
33 
34## Output Format
35 
36- High-level summary of findings
37- Issues grouped by severity (blocking, important, minor)
38- Suggestions and questions
39- Test and coverage notes
40 
41## Resources
42 
43- `resources/implementation-playbook.md` for detailed review patterns and templates.
44 
View all files on GitHub →

Details

License
MIT
Stars on the repo
★ 32,299
Checked
Source
davila7/claude-code-templates ↗
Creator
davila7 · 212 listings
View creator

Similar skills

See all →
SkillCode Review Feedback Analyzerobra/superpowers · by obraUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation★ 290k GitHub starsSkillCode Review ExpertHoangNguyen0403/agent-skills-standard · by HoangNguyen0403Conduct high-quality, persona-driven code reviews. Use when reviewing PRs, critiquing code quality, or analyzing changes for team feedback.★ 569 GitHub starsSkillContent ExplainerJohnQinAMD/llm-output-explainer · by JohnQinAMDExplain something in the format that is fastest to understand, from controlled English (ASD-STE100 style), to a diagram, to an interactive HTML page, to a narrated explainer video. Check facts against their sources, using parallel subagents for independent evidence streams when the host supports them. Use when the user wants to understand a substantial concept, algorithm, code change, pull request, paper, benchmark result, or agent output, or asks for an explainer, diagram, HTML explanation, STE, or video. Not for one-line answers, drafting a pull request description, or code review.★ 4 GitHub starsSkillCode Review Requesterobra/superpowers · by obraUse when completing tasks, implementing major features, or before merging to verify work meets requirements★ 290k GitHub starsSkillMulti-Axis Code Reviewaddyosmani/agent-skills · by addyosmaniConducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch.★ 98.7k GitHub starsSkillCode Clarity Simplifieraddyosmani/agent-skills · by addyosmaniSimplifies code for clarity. Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend than it should be. Use when reviewing code that has accumulated unnecessary complexity.★ 98.7k GitHub stars

More from davila7

Skill2D Game Developmentdavila7/claude-code-templates · by davila72D game development principles. Sprites, tilemaps, physics, camera.★ 32.3k GitHub starsSkill3D Game Development Principlesdavila7/claude-code-templates · by davila73D game development principles. Rendering, shaders, physics, cameras.★ 32.3k GitHub starsSkill3D Web Experience Builderdavila7/claude-code-templates · by davila7Expert in building 3D experiences for the web - Three.js, React Three Fiber, Spline, WebGL, and interactive 3D scenes. Covers product configurators, 3D portfolios, immersive websites, and bringing depth to web experiences. Use when: 3D website, three.js, WebGL, react three fiber, 3D experience.★ 32.3k GitHub starsSkillSplit Test Setupdavila7/claude-code-templates · by davila7When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," or "hypothesis." For tracking implementation, see analytics-tracking.★ 32.3k GitHub starsAgentResearch Literature Synthesizerdavila7/claude-code-templates · by davila7Academic research synthesis specialist. Use PROACTIVELY for comprehensive research on academic topics, literature reviews, technical investigations, and well-cited analysis combining multiple sources. <example>Context: A podcast episode needs a segment grounded in peer-reviewed evidence with formal citations. user: "Research the current state of transformer efficiency techniques for the episode, with proper academic citations." assistant: "I'll use the academic-research-synthesizer agent to search arXiv and Semantic Scholar, extract full-text findings via WebFetch, and produce a cited literature synthesis with confidence levels." <commentary>Use academic-research-synthesizer (not comprehensive-researcher) when the episode segment needs peer-reviewed sourcing, formal citation format, and explicit confidence tagging rather than general-purpose multi-source coverage.</commentary></example> <example>Context: The episode-orchestrator has routed a "literature review" request for a technical deep-dive segment. user: "Summarize the research landscape on federated learning privacy guarantees." assistant: "I'll invoke academic-research-synthesizer to systematically search academic sources, note peer-review status per source, and synthesize consensus vs. open debates."</example>★ 32.3k GitHub starsAgentAcademic Research Specialistdavila7/claude-code-templates · by davila7Academic research specialist for scholarly sources, peer-reviewed papers, and academic literature. Use PROACTIVELY for research paper analysis, literature reviews, citation tracking, and academic methodology evaluation. <example>Context: The research-orchestrator has kicked off Phase 4 parallel research on 'efficacy of intermittent fasting' and needs peer-reviewed evidence. user: "Find the academic evidence on intermittent fasting outcomes." assistant: "I'll use the academic-researcher agent to search Semantic Scholar, PubMed, and OpenAlex for peer-reviewed studies and write structured findings to academic-research.md." <commentary>The request is specifically for scholarly/peer-reviewed evidence rather than general web coverage or code, so academic-researcher (not web-researcher or technical-researcher) is the right specialist.</commentary></example> <example>Context: The user wants a literature review comparing methodologies across studies on a topic. user: "Can you review the literature on transformer model interpretability and identify research gaps?" assistant: "Let me invoke the academic-researcher agent to pull foundational and recent papers, extract methodologies, and surface open research gaps." <commentary>Literature review, methodology extraction, and research-gap identification are core academic-researcher capabilities, distinct from technical-researcher's focus on code repositories and implementations.</commentary></example>★ 32.3k GitHub stars