code-review

Audit multi-file codebases for spec conformance, testing, security, and readability.

319|74|Updated May 17, 2025
One-click install
npx skills add https://github.com/m-xlsea/ruoyi-plus-soybean --skill code-review-m-xlsea
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/m-xlsea/ruoyi-plus-soybean/tree/main/.claude/skills/code-review
Command: npx skills add https://github.com/m-xlsea/ruoyi-plus-soybean --skill code-review-m-xlsea

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code review is time-consuming and error-prone; this Skill standardizes and accelerates the process by applying structured checks and an objective LLM-based judge to assess code quality.

Core Features & Use Cases

  • Spec Compliance & TDD: Verifies each MUST requirement is implemented and each source file has accompanying tests.
  • Boundary & Security: Evaluates handling of edge cases (empty input, high load) and checks for secure coding practices.
  • Readability & Simplicity: Enforces clarity, limited function length, and strong type usage.
  • LLM-as-Judge Output: Produces a consistent JSON verdict with level, issues, and summary for automation pipelines.
  • Use Case: Integrate into CI as a gate between PR review and merge to ensure code quality.

Quick Start

Review the target project codebase for spec compliance, tests, boundaries, security, readability, and simplicity.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I automate code reviews for multi-file software projects?

Automate code reviews by applying a structured, rule-based process that audits spec compliance, testing, boundaries, security, readability, and simplicity across multi-file projects to generate objective quality assessments.

What is the LLM-as-Judge evaluation format for CI pipelines?

The LLM-as-Judge evaluation format is a deterministic process that audits code quality and produces a consistent JSON verdict containing the review level, identified issues, and a summary for automated CI gates.

How do I enforce TDD and spec compliance in an automated pull request review?

Enforce TDD and spec compliance by running automated checks that verify each MUST requirement is implemented and confirm every source file has accompanying tests before generating a review report.

Can I check boundary handling and security vulnerabilities automatically during code review?

You can check boundary handling and security vulnerabilities automatically by evaluating edge cases like empty input and high load, and scanning for secure coding practices during the structured review process.

Does automated code review work as a gate between PR review and merge?

Automated code review works as a CI gate by outputting a structured JSON report with a defined level, issues, and summary, allowing pipelines to block merges based on objective quality thresholds.

What are the limitations of using an LLM to judge code readability and simplicity?

Limitations of using an LLM to judge code readability and simplicity include its reliance on deterministic rule-based checks for function length and strong type usage, which may miss nuanced context-specific architectural decisions.