skills.rest
nntoan
nntoanCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

code-review-and-quality

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

Updated Sep 5, 2026
Search Tags:#code review#pull request#refactoring#merge#security review#quality gates#dependency upgrade
One-click install
npx skills add https://github.com/nntoan/ultra-omp --skill code-review-and-quality-nntoan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review-and-quality
Source: https://github.com/nntoan/ultra-omp/tree/main/packages/proflow/skills/code-review-and-quality
Command: npx skills add https://github.com/nntoan/ultra-omp --skill code-review-and-quality-nntoan

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, Required, Nit, Optional, or FYI so authors know exactly what must be addressed before merge. - Change Sizing and Splitting: Provides thresholds (~100/~300/~1000 lines) and splitting strategies (stack, file group, horizontal, vertical) for oversized changes. - Dependency Discipline: Covers changelog review, one-dependency-per-change upgrades, lockfile diff review, and audit triage. - Use Case: Before merging a pull request, run the review checklist to verify tests, catch an N+1 query, flag a missing auth check, and produce a structured verdict of Approve or Request changes. ## Quick Start Review this pull request across correctness, readability, architecture, security, and performance, then give me a severity-labeled findings list and an approve or request-changes verdict.

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?▼

Follow a five-step process: understand the change's intent, review the tests first, walk the implementation across five axes (correctness, readability, architecture, security, performance), categorize findings by severity, and verify the author's testing evidence before approving.

What should a code review checklist include?▼

A review checklist should cover correctness against the spec, edge case and error handling, naming and readability, architectural fit, security checks like input validation and secrets, performance issues like N+1 queries, and verification that tests and builds pass.

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

Around 100 changed lines is ideal and reviewable in one sitting; 300 lines is acceptable for a single logical change; 1000 lines is too large and should be split using stacking, file-group, horizontal, or vertical splitting strategies.

How do I review dependency upgrades safely?▼

Read the changelog rather than trusting semver, upgrade one dependency per change so failures are attributable, require a green test suite before and after, and review the lockfile diff since a single bump can pull in many transitive changes.

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, not perfection.

Is AI-generated code safe to merge without review?▼

No. AI-generated code needs more scrutiny, not less, because it is confident and plausible even when wrong. Review it with the same five-axis process, paying extra attention to correctness, security boundaries, and architectural fit.

Related Skills

Explore More Software Engineering Skills→
lapaixkemsdortshlee-svglapaixkemsdortshlee-svg

requesting-code-review

Review completed code changes against stated requirements with severity-ranked findings.

Community
Intermediate
MartyBonacciMartyBonacci
65

specswarm-ship

Require explicit confirmation before merging or deploying to production.

Community
Intermediate
OneWave-AIOneWave-AI
245

code-review-pro

Review code for security vulnerabilities, performance bottlenecks, and maintainability issues.

Official
Basic
awinogradovawinogradov
5

pr:monitor

Monitor pull requests for review approval and CI check status.

Community
Intermediate