skills.rest
JacobThree
JacobThreeCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

code-review-and-quality

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

Updated Apr 28, 2026
Search Tags:#testing#code review#pull request#refactoring#merge#security review#quality gates
One-click install
npx skills add https://github.com/JacobThree/zero-bloat-mcp-stack --skill code-review-and-quality-jacobthree
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review-and-quality
Source: https://github.com/JacobThree/zero-bloat-mcp-stack/tree/main/ai_blueprints/agent-skills/skills/code-review-and-quality
Command: npx skills add https://github.com/JacobThree/zero-bloat-mcp-stack --skill code-review-and-quality-jacobthree

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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 optional. - Change Sizing and Splitting: Provides thresholds (~100/~300/~1000 lines) and splitting strategies (stack, file group, horizontal, vertical) 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 by severity 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 handling, test coverage, 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 review?▼

A pull request should target around 100 lines changed, with 300 acceptable for a single logical change. Changes near 1000 lines should be split using stacking, file grouping, horizontal layering, or vertical feature slices.

Does AI-generated code need code review?▼

AI-generated code needs more scrutiny, not less, because it is confident and plausible even when wrong. Review it across all five axes, verify tests actually test behavior, and never rubber-stamp with an unexamined approval.

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

Request changes when Critical issues exist, such as security vulnerabilities, data loss risks, or broken functionality. Approve when the change improves overall code health even if imperfect, and never accept deferred cleanup promises.

Related Skills

Explore More Software Engineering Skills→
lenadlmlenadlm

test-driven-development

Automate the RED-GREEN-REFACTOR cycle for Test-Driven Development.

Community
Advanced
tayiorbeiitayiorbeii

gstack-ship

Automates the ship workflow of testing, versioning, committing, pushing, and creating pull requests.

Community
Advanced
HerbertJulioHerbertJulio
20

audit

Audit codebases for security flaws, performance bottlenecks, architectural risk, and dependency health.

Community
Advanced
Open-PawsOpen-Paws
3

code-review

Automate layered code review for pull requests in CI pipelines.

Official
Advanced