code-review

Review code against .agents/rules/ security, reliability, and maintainability standards.

150|48|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/irahardianto/awesome-agv --skill code-review-irahardianto
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/irahardianto/awesome-agv/tree/main/.agents/skills/code-review
Command: npx skills add https://github.com/irahardianto/awesome-agv --skill code-review-irahardianto

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you systematically review code quality by checking security, reliability, architecture, and maintainability issues that many surface-level checks miss.

Core Features & Use Cases

  • Structured review protocol: Reviews code in priority order (Critical/Must Fix, Major/Should Fix, Minor/Nice to Fix) to produce consistent outcomes.
  • Rule-set alignment: Loads and applies the full rule set from .agents/rules/, using rule-priority.md for severity and tagging issues by category.
  • Language anti-pattern enforcement: Automatically treats language-specific anti-pattern files as immediate findings when relevant language patterns are present.
  • Audit-grade reporting: Produces a well-structured findings report and, when run via /audit, persists it to docs/audits/ for reuse across conversations and agents.
  • When to use: Use for your own code, code produced by an AI agent, or during the /audit workflow (Phase 1: Code Review), preferably in a fresh context to reduce confirmation bias.

Quick Start

Use the code-review skill to audit the files related to the feature "billing" from the repository.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I perform a structured code review for security and maintainability issues?▼

You can review AI-generated code by running a structured code review protocol that checks for security, architecture, and maintainability defects, categorizing findings by rule priority to surface issues many surface-level checks miss.

How do I generate an audit findings report for my codebase?▼

To generate an audit findings report, run the code review via the /audit workflow, which categorizes defects by dimension tags and persists the structured findings report to the docs/audits/ directory for reuse across conversations.

Can I enforce language-specific anti-pattern checks during a code review?▼

Yes, language-specific anti-pattern checks are enforced by treating relevant language anti-pattern files as immediate findings when matching language patterns are detected during the code review process.

What is the best way to audit code quality without confirmation bias?▼

The best way to audit code quality without confirmation bias is to run the code review in a fresh context, systematically evaluating security and architecture defects against a loaded rule set from .agents/rules/.

Do I need custom rules in .agents/rules/ to review my code?▼

Yes, you need rules in .agents/rules/ because the review loads the full rule set from this directory, using rule-priority.md to determine severity and tag issues by category during the audit.