code-review-excellence

Guides structured pull request reviews with checklists, feedback techniques, and severity labels.

Updated May 28, 2026
One-click install
npx skills add https://github.com/changfengpro/agent-skills --skill code-review-excellence-changfengpro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review-excellence
Source: https://github.com/changfengpro/agent-skills/tree/main/skills/code-review-excellence
Command: npx skills add https://github.com/changfengpro/agent-skills --skill code-review-excellence-changfengpro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code reviews often become inconsistent, overly nitpicky, or delayed, leading to missed bugs, hurt team morale, and slow merge cycles. This Skill provides a systematic review process with checklists, feedback frameworks, and language-specific patterns so reviews catch real issues while fostering knowledge sharing. ## Core Features & Use Cases - Phased Review Process: A four-phase workflow covering context gathering, high-level design review, line-by-line analysis, and a summarized decision with clear verdicts. - Feedback Techniques: Question-based feedback, severity labels (blocking, nit, suggestion, praise), and collaborative phrasing to keep reviews constructive. - Language-Specific Checklists: Python and TypeScript/JavaScript anti-patterns such as mutable default arguments, broad exception handling, unhandled async errors, and prop mutation. - Use Case: When reviewing a teammate's 300-line pull request, use this Skill to run through the security, performance, and testing checklists, then deliver prioritized feedback with severity labels and a clear approve/request-changes decision. ## Quick Start Review this pull request using the code review checklist and provide prioritized feedback with severity labels.

Frequently Asked Questions about code-review-excellence

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a pull request effectively?

Follow a phased process: gather context from the PR description and CI status, review architecture and file organization, then do a line-by-line pass for logic, security, and performance issues. Finish with a summary and a clear approve, comment, or request-changes decision.

How to give constructive code review feedback?

Make feedback specific, actionable, and focused on the code rather than the person. Use questions instead of commands, label comments by severity such as blocking or nit, and balance criticism with praise for good work.

What should I check in a code review checklist?

Check logic correctness and edge cases, security issues like SQL injection and input validation, performance problems like N+1 queries, test coverage, and error handling. Skip formatting and linting since automated tools handle those.

What are common Python code review issues?

Common Python issues include mutable default arguments shared across calls, overly broad except clauses that swallow errors, and mutable class attributes shared across instances. Use None defaults, catch specific exceptions, and initialize mutable state in __init__.

When should I request changes versus approve a pull request?

Request changes only for blocking issues like security vulnerabilities or correctness bugs. Approve with comments for minor suggestions and nits, and avoid blocking progress over style preferences that linters can enforce.