code-review-excellence

Reviews pull requests and diffs with structured checklists, severity labels, and feedback templates.

Updated Oct 7, 2022
One-click install
npx skills add https://github.com/tamagusko/linux-cfg --skill code-review-excellence-tamagusko
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review-excellence
Source: https://github.com/tamagusko/linux-cfg/tree/main/dotfiles/claude/skills/code-review-excellence
Command: npx skills add https://github.com/tamagusko/linux-cfg --skill code-review-excellence-tamagusko

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve? Code reviews often become inconsistent, slow, or overly nitpicky, blocking merges and frustrating teams. This Skill provides a systematic review process with phased analysis, severity-tagged comments, and language-specific bug patterns so reviews stay constructive and thorough. ## Core Features & Use Cases - Phased Review Process: Four-phase workflow covering context gathering, high-level architecture review, line-by-line analysis, and a summarized verdict. - Severity-Labeled Feedback: Standardized labels (blocking, important, nit, suggestion, praise) plus templates for clear, actionable review comments. - Language-Specific Checklists: Python and TypeScript/JavaScript anti-patterns, security review guides, and a PR analyzer script that summarizes diff size for review planning. - Use Case: A reviewer facing a 600-line pull request runs the pr-analyzer script to gauge scope, then applies the security and testing checklists to produce a structured review comment with prioritized required changes. ## Quick Start Review the current pull request diff and produce a structured review comment with severity-labeled feedback.

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, review architecture and file organization, then check line-by-line for logic, security, and performance issues. Finish with a summarized verdict using severity labels like blocking, important, or nit.

How to write constructive code review comments?

Make feedback specific, actionable, and focused on the code rather than the author. Ask questions instead of issuing commands, suggest alternatives with examples, and tag comments with severity labels so authors know what must change before merge.

What should a code review checklist include?

Cover input validation, parameterized SQL queries, authorization checks, error handling, test coverage of edge cases, and performance risks like N+1 queries. Automate formatting and linting checks so manual review focuses on logic and design.

How do I measure pull request size before reviewing?

Run the included pr-analyzer.py script against a git repository to count changed files and added or deleted lines between two revisions. Pull requests over roughly 400 lines are harder to review well and should be split.

When should a code review request changes instead of approving?

Request changes for blocking issues such as security vulnerabilities, correctness bugs, or missing authorization checks. Approve with comments for nits and suggestions, and avoid blocking merges over formatting or personal style preferences.