review-code

Evaluate pull requests for code quality and business impact.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/t-hasuike/CLysis --skill review-code-t-hasuike
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-code
Source: https://github.com/t-hasuike/CLysis/tree/main/legacy-execution/skills/review-code
Command: npx skills add https://github.com/t-hasuike/CLysis --skill review-code-t-hasuike

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematically evaluate PRs by analyzing code quality and business implications to support informed approvals.

Core Features & Use Cases

  • Structured PR evaluation: Assess code quality, readability, and consistency with project patterns.
  • Business perspective alignment: Link changes to domain rules, user impact, and release risk.
  • Actionable outputs: Provide an approval judgment rationale and concrete improvement suggestions.

Quick Start

Provide a PR number and repository context to generate a comprehensive review report.

Frequently Asked Questions about review-code

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

FAQPage Schema
How do I automate PR code quality reviews?

Automate PR code quality reviews by providing a PR number and repository context to generate a structured evaluation. This assesses readability, consistency with project patterns, and cross-repository duplication to support informed approvals.

Can I evaluate business impact and release risk during a pull request review?

Yes, you can evaluate business impact during a pull request review by aligning changes with domain rules and user impact. The review generates a rationale for approval judgments and concrete suggestions to mitigate release risk.

What is the best way to check pull requests for maintainability and security?

Checking pull requests for maintainability and security is handled through structured evaluation with optional focus areas. The process analyzes code quality standards and alignment with domain rules to produce actionable improvement suggestions.

Does the automated code review work with test coverage and domain rules?

Yes, the automated code review satisfies checks for test coverage and alignment with domain rules as defined by project guidelines. It links code changes to business perspectives and evaluates overall release risk.

How do I get approval judgments and improvement suggestions for code changes?

Get approval judgments and improvement suggestions by running a structured evaluation on your pull requests. The evaluation analyzes code quality and business implications to output an approval rationale and concrete next steps.

When do I need a systematic PR code quality and business review?

You need a systematic PR code quality and business review when evaluating changes across repositories that require standardized checks. It ensures code quality consistency and evaluates business impact before approving releases.