Is this report suitable for non-developers?

Yes, it is specifically designed for Product Owners and stakeholders, focusing on functional changes and business impact rather than raw code diffs.

What does the Git Release Impact Reporter actually generate?

It produces a self-contained HTML file containing visual charts, business impact summaries, and technical statistics comparing any two git branches.

How do I specify which branches to compare?

You provide a source branch (like a release branch) and a target branch (like main or develop) as arguments to the command.

Where is the report saved?

By default, reports are saved in the .claude/reports directory of your project for easy access and sharing.

Does it require any external dependencies?

The skill uses standard git commands and Python3 for data processing, which are typically available in most development environments.

Git Release Impact Reporter

Name: Git Release Impact Reporter
Author: atournayre

byatournayre

•

コラボレーションツール

Generates professional, PO-oriented HTML impact reports comparing git branches to visualize release changes and business impact.

This skill automates the creation of detailed release reports by analyzing the differences between two Git branches. It goes beyond simple diffs to provide a high-level overview suitable for Product Owners and stakeholders, featuring visual KPIs, business domain impact analysis, and technical debt evolution. By extracting features from commit messages and quantifying changes across different file types, it transforms raw code updates into an actionable, styled HTML document that facilitates better communication during the release cycle.

主な機能

01Automated HTML report generation with inline CSS and responsive design.

02Granular file type distribution (PHP, JS, Twig, etc.) and impact levels.

03Visual KPI dashboard showing code modification percentages and net variations.

04Business-centric analysis of features and bug fixes extracted from commit history.

058 GitHub stars

06Functional domain grouping to identify which parts of the application changed most.

ユースケース

01Documenting the technical and functional evolution of a specific version for audit or historical purposes.

02Preparing for a production release by generating a summary for non-technical stakeholders.

03Reviewing the scope of a feature branch before merging it into the main development line.

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add atournayre/claude-marketplace release-report

For use in Claude.ai and ChatGPT

Download Skill