code-review-and-quality

Reviews code across correctness, readability, architecture, security, and performance with severity-labeled findings.

2|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/d0whc3r/statsig-browser-extension --skill code-review-and-quality-d0whc3r
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review-and-quality
Source: https://github.com/d0whc3r/statsig-browser-extension/tree/main/.agents/skills/code-review-and-quality
Command: npx skills add https://github.com/d0whc3r/statsig-browser-extension --skill code-review-and-quality-d0whc3r

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents low-quality, risky, or incorrect changes from being merged by running a structured, multi-axis review before code reaches the main branch.

Core Features & Use Cases

  • Five-Axis Code Review: evaluates correctness, readability & simplicity, architecture fit, security exposure, and performance impact.
  • Quality-Gated Approval Standard: establishes a clear “approve when it improves health” criterion to avoid rubber-stamping while still enabling progress.
  • Review Process & Severity Labeling: enforces test-first review, categorized findings, verification expectations, and consistent severity prefixes (Critical/Required vs Optional/Suggestion).
  • Change Sizing Guidance: helps reviewers request splitting when changes are too large and encourages separate refactoring vs feature work.
  • Dead Code Hygiene & Verification Checks: prompts explicit identification of dead code and confirmation that verification details are documented.

Quick Start

Use the code-review-and-quality skill to review a proposed change across correctness, readability, architecture, security, and performance, and return prioritized findings labeled 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 conduct a structured code review for a pull request?

A structured code review evaluates proposed changes across correctness, readability, architecture fit, security exposure, and performance impact to prevent risky modifications from merging into the main branch.

What is test-first review and why does it matter for code quality?

Test-first review requires reading tests before evaluating the implementation logic to ensure edge cases and error paths are covered, establishing a quality-gated approval standard that prevents rubber-stamping changes.

How do I label code review findings by severity?

Code review findings are labeled using consistent severity prefixes, categorized as Critical or Required for mandatory fixes, and Optional or Suggestion for improvements, which helps prioritize bug fixes before merging.

Can I use this code review process for agent-generated patches and refactoring work?

Yes, the multi-axis review process applies to refactors, bug fixes, and agent- or human-generated patches, evaluating correctness and maintainability while providing change sizing guidance to separate refactoring from feature work.

What is the best way to handle large pull requests during code review?

For large pull requests, the review process provides change sizing guidance to request splitting, encouraging separate commits for refactoring versus feature work to improve overall code health and verification.

How do I identify dead code and document verification during a security review?

A security review prompts explicit identification of dead code for hygiene purposes and requires confirmation that concrete verification details are documented, ensuring error paths and edge cases are validated before approval.