code-review-excellence

Review pull requests with structured checklists, severity labels, and constructive feedback techniques.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/SanketAdlak/PDMProjectDesign --skill code-review-excellence-sanketadlak
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review-excellence
Source: https://github.com/SanketAdlak/PDMProjectDesign/tree/main/.agents/skills/code-review-excellence
Command: npx skills add https://github.com/SanketAdlak/PDMProjectDesign --skill code-review-excellence-sanketadlak

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code reviews often become bottlenecks, sources of team friction, or rubber-stamp approvals that miss critical bugs. This Skill provides a systematic review process that catches defects early while keeping feedback constructive and maintaining team morale. ## Core Features & Use Cases - Four-Phase Review Process: Structured workflow covering context gathering, high-level architecture review, line-by-line analysis, and summary decisions with clear verdicts. - Severity-Labeled Feedback: Standardized labels (blocking, important, nit, suggestion, praise) that differentiate must-fix issues from optional improvements. - Language-Specific Guidance: Concrete Python and TypeScript/JavaScript anti-patterns to check, including mutable defaults, broad exception handling, and unhandled async errors. - Use Case: When reviewing a teammate's 300-line pull request, follow the phased checklist to verify security, performance, and test coverage, then deliver prioritized feedback using the comment template. ## Quick Start Review this pull request using the code review checklist and provide 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 four-phase process: gather context from the PR description, review architecture and file organization, do a line-by-line check for logic and security issues, then summarize with a clear verdict. Keep reviews under 60 minutes and PRs under 400 lines.

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 during a code review?

Check logic correctness, edge cases, security vulnerabilities like SQL injection and XSS, performance issues 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?

Watch for mutable default arguments, overly broad exception handling, and mutable class attributes shared across instances. These are frequent bugs that reviewers should flag with corrected examples.

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 avoid blocking progress over style preferences or non-critical improvements.