code-review

Coordinate parallel code reviews across five perspectives with integrated reporting.

1|Updated Sep 8, 2023
One-click install
npx skills add https://github.com/cmb-sy/dotfiles --skill code-review-cmb-sy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/cmb-sy/dotfiles/tree/main/claude/skills/code-review
Command: npx skills add https://github.com/cmb-sy/dotfiles --skill code-review-cmb-sy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

複数観点によるコード変更のレビューを自動化・統合し、品質と安全性を高めます。

Core Features & Use Cases

  • 複数観点の並列レビュー (simplify, code-quality, code-security, code-performance, code-test) を同時に実行
  • 統合レポートの作成と承認済み指摘のみの適用
  • Codex 指定時の追加メタレビュー対応

Quick Start

Start a Code Review session to begin Phase 1 Scope Detection.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I automate parallel code reviews for multiple perspectives?

Parallel code reviews are coordinated by collecting diffs and evaluating them simultaneously across five perspectives: simplify, code-quality, code-security, code-performance, and code-test, followed by integrated reporting.

What is the best way to integrate security checks into a code review workflow?

Integrating security checks into code review workflows is handled by executing a dedicated code-security perspective alongside other quality evaluations in parallel, ensuring security findings are consolidated into a final integrated report.

How do I generate an integrated report from multiple code review perspectives?

Integrated reports from multiple code review perspectives are generated by collecting diffs, running parallel evaluations across five distinct viewpoints, and consolidating the findings into a unified output that applies only approved suggestions.

Does the code review process support Codex-based evaluations?

Codex-based evaluations are supported as an optional feature, enabling additional meta-reviews alongside the standard parallel evaluations of code changes across the five designated perspectives.

Can I review code changes without setting up complex dependencies?

Reviewing code changes without complex dependencies is possible because the review orchestrator operates independently, requiring no external dependencies to collect diffs and execute parallel multi-perspective evaluations.

What are the limitations of using YAML frontmatter in code review reporting?

YAML frontmatter in code review reporting provides metadata support but does not replace the core diff evaluation logic, serving only as an optional metadata layer within the integrated reporting phase.