commit

Analyze staged diffs and generate atomic conventional commits.

10|2|Updated Mar 2, 2026

Search Tags:#git #commit #backlog #pre-commit #code-review #conventional-commits #diff-analysis

Ready to run

npx skills add https://github.com/dixus/claudeframework --skill commit-dixus

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/dixus/claudeframework/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/dixus/claudeframework --skill commit-dixus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generating atomic, well-structured commits from evolving code improves traceability and review.

Core Features & Use Cases

Analyze diffs to identify logical concerns and propose one commit per concern
Enforce conventional commit messages and optional scopes for consistent history
Backlog integration: detect task IDs in messages and reference them in commits
Guide staging, splitting, and committing in a safe, repeatable workflow

Quick Start

Provide your changes and any task identifiers, and the tool will generate one or more atomic commits with conventional messages.

Frequently Asked Questions about commit

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

FAQPage Schema

How do I generate conventional commit messages from staged git changes?▼

To generate conventional commit messages, provide your staged changes and any task identifiers. The tool analyzes the diff and outputs one or more atomic commits with properly formatted conventional messages.

How does diff analysis help split mixed changes into atomic commits?▼

Diff analysis identifies distinct logical concerns within your staged changes. It then proposes splitting the changes so each concern becomes its own atomic commit, improving traceability and simplifying code review.

Can I integrate backlog task IDs into my conventional commit messages?▼

Yes, backlog integration detects task IDs you provide and references them directly in the generated commit messages, linking your atomic commits to specific project backlog items.

Do I need external dependencies or plugins to run pre-commit checks for commits?▼

No external dependencies or plugins are required. The tool enforces pre-commit checks and guides staging, splitting, and committing using only standard Git tooling available in your environment.

What is the best way to ensure consistent git history with conventional commits and optional scopes?▼

The best way to ensure consistent git history is enforcing conventional commit messages with optional scopes. The tool guides you through a safe, repeatable workflow to structure each atomic commit correctly.

When should I not use automated conventional commit generation for my project?▼

You should avoid automated conventional commit generation when your changes are entirely unrelated to a backlog or when your project does not use conventional commit standards, as enforcing these formats may create unnecessary overhead.