rey-code-review

What This Skill Does

The rey-code-review skill is a powerful tool designed for the OpenClaw AI ecosystem to perform structured, high-quality code analysis. It functions as a professional pair programmer, providing feedback based on the scope and complexity of the code provided. The skill categorizes reviews into three distinct tiers: Quick Review for rapid checks of small snippets, Standard Review for moderate refactoring or logic adjustments, and Full Review for comprehensive architectural and security assessments. It evaluates code across five critical dimensions: Correctness, Readability, Maintainability, Security, and Performance. The output is structured using a standard severity-based grading system (CRITICAL, MAJOR, MINOR, NIT) to ensure the user understands the urgency of each recommendation.

Installation

To integrate this skill into your environment, use the OpenClaw CLI: clawhub install openclaw/skills/skills/sa9saq/rey-code-review

Use Cases

• Automating Code Quality: Ensuring that pull requests adhere to team standards before human review.
• Security Hardening: Identifying potential vulnerabilities like SQL injection or weak input validation before code hits production.
• Knowledge Transfer: Helping junior developers understand why certain patterns are preferred over others through detailed, constructive feedback.
• Technical Debt Management: Using the Full Review mode to identify performance bottlenecks and architectural flaws in large, legacy modules.

Example Prompts

1. "Please run a standard code review on these three files I've uploaded to see if the error handling is sufficient."
2. "I need a quick review of this small function; I'm mainly concerned about potential edge cases and type errors."
3. "Perform a full review on the core authentication module. Pay extra attention to security vulnerabilities and long-term maintainability."

Tips & Limitations

• Context is Key: While the skill can review code in isolation, providing the surrounding context (e.g., project architecture, specific frameworks) will significantly increase the quality of the feedback.
• Balance Efficiency: Reserve 'Full Review' for major features or architectural changes, as it consumes more token budget and time compared to the 'Quick Review'.
• Security Note: While this skill checks for common vulnerabilities, it does not replace a dedicated penetration test or a deep dive by a security expert. Always cross-reference critical security findings with the security-review skill.