code-review-and-quality

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

Updated May 21, 2026
One-click install
npx skills add https://github.com/nicorevo/AI-SDLC-Template --skill code-review-and-quality-nicorevo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review-and-quality
Source: https://github.com/nicorevo/AI-SDLC-Template/tree/main/.opencode/skills/code-review-and-quality
Command: npx skills add https://github.com/nicorevo/AI-SDLC-Template --skill code-review-and-quality-nicorevo

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 Findings: Categorizes feedback as Critical, Required, Nit, Optional, or FYI so authors know what must be fixed versus what is optional. - Change Sizing and Dependency Discipline: Enforces small reviewable changes, separates refactoring from feature work, and requires changelog review plus per-package isolation for dependency upgrades. - Use Case: Before merging a pull request that adds a new API endpoint, run this review to verify tests cover edge cases, inputs are validated at boundaries, no N+1 queries exist, and the change description stands alone in version control history. ## Quick Start Review the current uncommitted changes across correctness, readability, architecture, security, and performance, and report findings with severity labels.

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 such as Critical, Required, Nit, or Optional, and finish with an approve or request-changes verdict.

What should a code review checklist include?▼

A code review checklist should cover correctness against the spec, edge case and error handling, test adequacy, naming and readability, architectural fit, input validation and secret handling, and performance issues like N+1 queries. It should end with verification that tests pass and the build succeeds.

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

A pull request should change roughly 100 lines for easy review, up to 300 lines for a single logical change. Around 1000 changed lines is too large and should be split by stacking, file groups, horizontal layers, or vertical feature slices.

How should I review dependency upgrades safely?▼

Review dependency upgrades by reading the changelog rather than trusting semver, upgrading one package per change, and requiring a green test suite before and after. Also review the lockfile diff for transitive changes and never hand-edit the lockfile.

When should a code review request changes instead of approving?▼

Request changes when there are Critical issues like security vulnerabilities or broken functionality, or unresolved Required findings. Approve when the change improves overall code health even if imperfect, since the standard is continuous improvement rather than perfection.