code-review

Review code iteratively using the Rule of 5 methodology.

1|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/charly-vibes/wai --skill code-review-charly-vibes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/charly-vibes/wai/tree/main/.agents/skills/code-review
Command: npx skills add https://github.com/charly-vibes/wai --skill code-review-charly-vibes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of code review by guiding the user through a structured, five-stage methodology to ensure code quality, correctness, and production readiness.

Core Features & Use Cases

  • Rule of 5 Methodology: Implements a systematic approach covering structure, correctness, clarity, edge cases, and production readiness.
  • Iterative Refinement: Provides feedback and suggestions at each stage, allowing for progressive improvement.
  • Use Case: A developer submits a new feature's code. This Skill can be invoked to perform an initial, thorough review, identifying potential issues and suggesting improvements before human review.

Quick Start

Review the provided code using the Rule of 5 methodology, starting with Stage 1: Draft.

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 before production deployment?

Perform a structured code review by applying the Rule of 5 methodology, which evaluates structure, correctness, clarity, edge cases, and production readiness. This systematic approach guides you through five distinct refinement stages to ensure software quality assurance.

Does the Rule of 5 methodology work for general software development workflows?

Yes, the Rule of 5 methodology works for software development workflows requiring systematic quality assurance. It applies iterative refinement to evaluate code structure, correctness, and edge cases, ensuring your feature is production ready regardless of the specific tech stack.

How do I start an iterative code review using the Rule of 5?

To start an iterative code review, submit your code and begin with Stage 1: Draft. The methodology then guides you sequentially through five refinement stages, asking specific questions and setting output expectations for each phase of the review.

What are the limitations of using automated iterative refinement for code quality?

Iterative refinement focuses on structure, correctness, clarity, and edge cases but serves as an initial review before human oversight. It automates feedback across five stages, yet production deployment still requires manual verification to catch context-specific business logic flaws.