code-review-and-quality

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

1|Updated Mar 2, 2025
One-click install
npx skills add https://github.com/marjorg/setup --skill code-review-and-quality-marjorg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review-and-quality
Source: https://github.com/marjorg/setup/tree/main/home/.agents/skills/code-review-and-quality
Command: npx skills add https://github.com/marjorg/setup --skill code-review-and-quality-marjorg

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 what must be fixed versus what is optional. - Change Sizing and Splitting Guidance: Defines thresholds for reviewable change sizes and provides strategies (stacking, horizontal, vertical) for splitting oversized PRs. - Use Case: Before merging a pull request, run the review checklist to verify tests cover the change, no secrets or injection risks exist, the diff stays within a healthy size, and the description stands alone in version control history. ## 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 and finish with an approve or request-changes verdict.

What should a code review checklist include?

A code review checklist should cover context understanding, correctness and edge cases, naming and simplicity, 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?

A pull request of around 100 changed lines is ideal, 300 is acceptable for a single logical change, and 1000 lines is too large and should be split. Split oversized changes by stacking, file groups, horizontal layers, or vertical feature slices.

How do I review AI-generated code differently?

AI-generated code needs more scrutiny, not less, because it is confident and plausible even when wrong. Apply the same five-axis review, verify tests actually test behavior, and never rubber-stamp with an unverified approval.

When should a dependency upgrade be rejected in review?

Reject bulk dependency bumps merged without changelog review or per-package isolation. Each upgrade should be reviewed individually, verified by a green test suite before and after, and include a reviewed lockfile diff.