Commit Analysis Skill

Analyze git diffs to detect commit type, scope, and atomicity.

9|2|Updated Oct 13, 2025
One-click install
npx skills add https://github.com/dhofheinz/open-plugins --skill commit-analysis-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Commit Analysis Skill
Source: https://github.com/dhofheinz/open-plugins/tree/main/plugins/git-commit-assistant/commands/commit-analysis
Command: npx skills add https://github.com/dhofheinz/open-plugins --skill commit-analysis-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Understanding the scope, type, and atomicity of changes within a Git commit is crucial for effective code reviews and project management, but manually analyzing diffs can be time-consuming. This skill automates the analysis of Git changes, providing insights into file statistics, commit types, and atomicity, saving you time and improving review efficiency.

Core Features & Use Cases

  • Change Analysis: Provides detailed statistics on added, modified, and deleted lines, giving a clear overview of the changes.
  • Type & Scope Detection: Automatically identifies the type (e.g., feat, fix, refactor) and scope of a commit, aiding in categorization.
  • Atomicity Assessment: Evaluates if a commit represents a single, logical change, promoting cleaner history.
  • Use Case: A reviewer needs to quickly understand the impact of a pull request. They use this skill to analyze the commits, getting a summary of changes, identifying the primary purpose (e.g., a new feature vs. a bug fix), and assessing if the changes are logically grouped, streamlining the review process.

Quick Start

Use the commit-analysis skill to analyze the changes in the last Git commit.

Frequently Asked Questions about Commit Analysis Skill

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

FAQPage Schema
How do I analyze git commit changes to understand what was modified?

Commit analysis automatically examines git diffs to provide detailed statistics on added, modified, and deleted lines, giving you a clear overview of all changes in a commit and their scope across files.

Can I automatically identify commit types like feat, fix, and refactor from code changes?

Yes, commit analysis detects conventional commit types (feat, fix, docs, refactor, style, test, build, ci) by examining the nature and scope of changes, helping categorize modifications by their purpose.

How do I check if my git commits are atomic and logically grouped?

Commit analysis assesses atomicity by evaluating whether a commit represents a single logical change, promoting cleaner git history and identifying when changes should be split into separate commits.

What's the best way to streamline code review workflows with git diff analysis?

Commit analysis produces structured JSON output summarizing commit type, scope, file statistics, and atomicity, enabling reviewers to quickly understand impact and integration with CI/CD pipelines for automated categorization.

Can I use commit analysis to detect which feature area or scope a change affects?

Commit analysis automatically identifies affected scope by categorizing changes by feature area (auth, api, docs), helping you understand which parts of the codebase a commit modifies.

Does this work for identifying changes that should be split into multiple commits?

Yes, atomicity assessment detects when a commit mixes unrelated changes, highlighting scenarios where modifications should be split to maintain a clean, logical commit history.