code-review-and-quality

Reviews code changes across correctness, readability, architecture, security, and performance before merge.

5|Updated Mar 5, 2024
One-click install
npx skills add https://github.com/TRAPZZY/God-Eyes --skill code-review-and-quality-trapzzy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review-and-quality
Source: https://github.com/TRAPZZY/God-Eyes/tree/main/.skills/code-review-and-quality
Command: npx skills add https://github.com/TRAPZZY/God-Eyes --skill code-review-and-quality-trapzzy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code merged without structured review accumulates defects, security vulnerabilities, and architectural debt. This Skill enforces a consistent multi-axis review process so every change is evaluated against the same quality gates before entering the main branch. ## Core Features & Use Cases - Five-Axis Review: Evaluates every change for correctness, readability, architecture, security, and performance with concrete checklists per axis. - Severity-Labeled Feedback: Categorizes findings as Critical, Nit, Optional, or FYI so authors know what blocks merge versus what is a suggestion. - Change Sizing and Splitting Guidance: Defines target change sizes (~100 lines) and provides stacking, horizontal, and vertical splitting strategies for oversized changes. - Use Case: Before merging a pull request, run the review checklist to verify tests cover the change, no secrets or injection vulnerabilities exist, and the verification story is documented. ## Quick Start Review this pull request across correctness, readability, architecture, security, and performance, and label each finding by severity.

Frequently Asked Questions about code-review-and-quality

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

FAQPage Schema
How do I review a pull request before merging?▼

Review a pull request by first understanding its intent, then checking tests, then walking the implementation across five axes: correctness, readability, architecture, security, and performance. Label every finding with a severity prefix so the author knows what blocks merge.

What should a code review checklist include?▼

A code review checklist should cover correctness against the spec, edge case and error path handling, test adequacy, naming and readability, architectural fit, security checks like input validation and secrets, and performance issues like N+1 queries and missing pagination.

How large should a pull request be for effective review?▼

A pull request should target around 100 lines changed, with 300 lines acceptable for a single logical change. Changes near 1000 lines should be split using stacking, file-group, horizontal, or vertical splitting strategies.

Should AI-generated code be reviewed differently?▼

AI-generated code needs more scrutiny, not less, because it is confident and plausible even when wrong. Apply the same five-axis review with extra attention to correctness, security boundaries, and whether tests actually verify the intended behavior.

When is it acceptable to approve an imperfect change?▼

Approve a change when it definitely improves overall code health, even if it is not perfect or written exactly as you would write it. Do not block on personal preference, but never accept deferred cleanup promises for real issues.