code-reviewer

Review code changes against approved plans for correctness and risk.

160|20|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/tctinh/agent-hive --skill code-reviewer-tctinh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/tctinh/agent-hive/tree/main/packages/opencode-hive/skills/code-reviewer
Command: npx skills add https://github.com/tctinh/agent-hive --skill code-reviewer-tctinh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of reviewing code changes, ensuring they align with approved plans, maintain high quality, and avoid common pitfalls like dead code or risky patterns.

Core Features & Use Cases

  • Plan Adherence Check: Verifies that code changes directly address the requirements of the approved task or plan.
  • Quality Assurance: Identifies correctness issues, potential bugs, and edge cases.
  • Simplicity & YAGNI: Flags unnecessary complexity, dead code, and speculative features.
  • Risk Assessment: Checks for security vulnerabilities, performance bottlenecks, and maintainability concerns.
  • Use Case: Before merging a feature branch, use this Skill to perform a thorough review, ensuring all requirements are met and the code is clean and safe.

Quick Start

Use the code-reviewer skill to review the attached code changes against the task description 'Implement user authentication'.

Frequently Asked Questions about code-reviewer

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

FAQPage Schema
How do I check if my code changes align with the approved plan requirements?

You can check plan adherence by comparing code implementation changes against the approved task intent and plan requirements to identify missing requirements and ensure full alignment before merging.

What is a YAGNI violation in code review and how do I detect it?

A YAGNI violation in code review involves implementing speculative features or unnecessary complexity. You can detect it by flagging dead code and unused logic during a simplicity check against the approved plan.

How do I perform a risk assessment on code changes before merging?

To perform a risk assessment on code changes, review the implementation for risky patterns, security vulnerabilities, and performance bottlenecks to ensure maintainability and mitigate risks before merging a feature branch.

Can I get an effort estimate as part of a structured code review?

Yes, you can get an effort estimate as part of a structured code review by providing task intent, plan requirements, and code changes as input to receive a categorized output of critical, major, and minor issues.

What is the best way to automate catching dead code during development tasks?

The best way to automate catching dead code during development tasks is to perform a structured review between tasks that checks for simplicity, YAGNI violations, and unnecessary complexity against the approved plan.