code-review

Analyze git diffs against the main branch from four review perspectives.

2|Updated Dec 1, 2025
One-click install
npx skills add https://github.com/Shirataki2/discalendar-next-v2 --skill code-review-shirataki2
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/Shirataki2/discalendar-next-v2/tree/main/.claude/skills/code-review
Command: npx skills add https://github.com/Shirataki2/discalendar-next-v2 --skill code-review-shirataki2

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Git差分ベースのコードレビューを自動化し、複数の専門家が並列に変更箇所を分析して統合レポートを出力します。

Core Features & Use Cases

  • 四観点の並列レビュー(Architecture / Type Safety / Code Quality / Security)で差分を評価
  • 重要度別の統合レポートを生成し、変更点を要約
  • Use-case: ブランチを切って自動レビューを依頼すると、複数レビュアーが同時に指摘事項を取得できる

Quick Start

Create a feature branch and run this skill to generate a four-viewpoint code review report.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I automate a diff-based code review for a feature branch?▼

A diff-based code review analyzes your branch changes against the main branch from four parallel perspectives—architecture, type safety, code quality, and security—then consolidates findings into a severity-based report.

What perspectives are covered in an automated parallel code review?▼

Automated parallel code review covers four perspectives: architecture, type safety, code quality, and security. Each reviewer analyzes the diff simultaneously to deliver a consolidated, severity-based report.

Can I get a severity-based report from automated code review?▼

Yes, automated code review generates a severity-based report that prioritizes findings from the four parallel reviewers, summarizing all change points into one consolidated output.

Does this automated code review work with server-side action workflows?▼

Yes, this automated code review uses standardized interfaces and a server-side action workflow to ensure the diff analysis process is safe and auditable.

What is the best way to review branch changes for security and type safety?▼

The best way to review branch changes for security and type safety is running an automated diff-based review, which deploys dedicated parallel reviewers to evaluate each aspect against the main branch.