the-reviewer

Review code changes across correctness, readability, architecture, security, and performance.

2|Updated May 23, 2026
One-click install
npx skills add https://github.com/fworks-tech/agenthood --skill the-reviewer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: the-reviewer
Source: https://github.com/fworks-tech/agenthood/tree/main/members/the-reviewer
Command: npx skills add https://github.com/fworks-tech/agenthood --skill the-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Reviewer ensures high-quality code by evaluating changes across multiple dimensions before they are merged, preventing defects and drift.

Core Features & Use Cases

  • Five-Axis Review: Correctness, Readability, Architecture, Security, and Performance assessments for every change.
  • Change Sizing & Standards: Applies rigorous gatekeeping, flags issues, and enforces project conventions.
  • Usage Scenarios: Use on feature branches, bug fixes, refactors, or when evaluating code produced by others.

Quick Start

Activate the reviewer to perform a five-axis code review on the current changes before merging.

Frequently Asked Questions about the-reviewer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I perform a code review before merging a feature branch?

Run a pre-merge code review by evaluating changes across five axes: correctness, readability, architecture, security, and performance. This enforces quality gates and prevents defects from reaching the main branch.

What is a five-axis code review and how does it enforce project standards?

A five-axis code review assesses correctness, readability, architecture, security, and performance. It enforces project standards by rigorously gatekeeping, flagging issues, and verifying tests for every change.

Can I use this automated code review for refactoring and bug fixes in any language?

Yes, the automated code review applies to feature branches, bug fixes, and refactors across any language. It evaluates changes and enforces project conventions regardless of the programming language.

Does the code review process check tests and security vulnerabilities?

Yes, the code review process verifies tests and evaluates security vulnerabilities. It ensures thorough verification by reviewing tests alongside the five-axis assessment to enforce quality gates before merges.

What is the best way to enforce quality gates and prevent code drift before a merge?

The best way to enforce quality gates is by performing a multi-axis code review that evaluates correctness, readability, architecture, security, and performance. This prevents defects and drift before merging changes.

Why should I review code produced by others using a multi-axis evaluation?

You should review code produced by others using a multi-axis evaluation to ensure correctness, readability, architecture, security, and performance. This provides clear, categorized feedback and prevents defects from merging.