diff-report

Name: diff-report
Availability: InStock
Author: kage1020

Analyze branch changes and generate a five-section Markdown diff report.

Updated Mar 15, 2026

Search Tags:#git #analysis #branching #code-review #version-control #diff-report

Ready to run

npx skills add https://github.com/kage1020/dotfiles --skill diff-report

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: diff-report
Source: https://github.com/kage1020/dotfiles/tree/main/dot_claude/skills/diff-report
Command: npx skills add https://github.com/kage1020/dotfiles --skill diff-report

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ベースブランチと現在のフィーチャーブランチの差分を分析し、変更統計・機能サマリー・技術ポイント・理解度チェック・コミット履歴の5セクションからなるレポートを自動生成します。

Core Features & Use Cases

差分統計の自動生成と要約
コミット履歴の表示・比較
機能サマリーと技術的ポイントの抽出
レビュー・リリース準備における差分理解の促進

Quick Start

現在のフィーチャーブランチの差分レポートを生成するには、/diff-report <base-branch> を実行してください。

Frequently Asked Questions about diff-report

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

FAQPage Schema

How do I generate a git diff report for a feature branch?▼

To generate a git diff report, execute the diff-report command with an optional base-branch argument to compute the merge-base and output a structured Markdown summary of changes.

What is included in a feature branch diff analysis report?▼

A diff analysis report includes five sections: diff statistics, feature summary, technical points, comprehension check, and commit history comparison between the base and feature branches.

Can I use a custom base branch for code review diff statistics?▼

Yes, you can specify a custom base branch as an input argument to compute the merge-base and generate accurate diff statistics for collaborative code review workflows.

How does version control branch comparison help with release readiness?▼

Version control branch comparison helps with release readiness by summarizing changes, extracting technical points, and displaying commit history to ensure all modifications are reviewed before merging.

Do I need any dependencies to analyze changes between git branches?▼

No external dependencies are required to analyze changes between git branches, as the skill operates independently to compute merge-base, diff statistics, and log history for Markdown reporting.

What's the best way to summarize commits for a code review?▼

The best way to summarize commits for a code review is to automate a structured diff report that extracts commit log history and diff statistics directly from the version control system.