code-review-excellence

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

1|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/dominionism/Noesis --skill code-review-excellence-dominionism
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review-excellence
Source: https://github.com/dominionism/Noesis/tree/main/assets/skills/code-review-excellence
Command: npx skills add https://github.com/dominionism/Noesis --skill code-review-excellence-dominionism

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code reviews often become inconsistent, overly nitpicky, or delayed, leading to missed bugs, security vulnerabilities, and strained team dynamics. This Skill provides a systematic review process that catches real issues while keeping feedback constructive and actionable. ## Core Features & Use Cases - Phased Review Process: A four-phase workflow covering context gathering, high-level design review, line-by-line analysis, and summary decisions with clear verdicts. - Severity-Labeled Feedback: Standardized labels (blocking, important, nit, suggestion, praise) that prioritize comments and prevent trivial issues from blocking merges. - Language-Specific Checklists: Concrete bug patterns for Python and TypeScript/JavaScript, plus security, performance, and testing checklists. - Use Case: When reviewing a teammate's 300-line pull request, follow the phased process to check architecture fit, scan for SQL injection and race conditions, then deliver a structured summary with labeled comments and a clear approve/request-changes decision. ## Quick Start Review this pull request using the code review excellence process and give me structured 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 and CI status, review architecture and file organization, do a line-by-line pass for logic, security, and performance issues, then summarize with a clear approve 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 recognition of 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, error handling, and architectural fit. Leave formatting and linting to automated tools.

What are common Python bugs to catch in code review?▼

Watch for mutable default arguments shared across calls, overly broad except clauses that swallow errors, and mutable class attributes shared across instances. These are frequent sources of subtle bugs in Python code.

When should I request changes instead of approving a pull request?▼

Request changes only for blocking issues like security vulnerabilities, correctness bugs, or missing critical tests. Minor style preferences and nice-to-have suggestions should be labeled as nits and not block the merge.