commit

Analyze code diffs to propose structured Conventional Commits and branch plans.

1|Updated Oct 13, 2022
One-click install
npx skills add https://github.com/kryota-dev/dotfiles --skill commit-kryota-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/kryota-dev/dotfiles/tree/main/.bin/.claude/skills/commit
Command: npx skills add https://github.com/kryota-dev/dotfiles --skill commit-kryota-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes code diffs to propose structured, logical commits that improve traceability and review efficiency.

Core Features & Use Cases

  • Analyze diffs to group changes by feature, module, or change type.
  • Propose a branch name and an ordered plan of commits that follow Conventional Commits.
  • Provide a clear commit plan and messages; execute changes after user confirmation.

Quick Start

Provide the repository context (and optional branch name) and the tool will propose a branch and a sequence of logical commits.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I analyze code diffs to create conventional commits automatically?

To analyze code diffs for conventional commits, you provide the repository context and an optional branch name. The tool groups changes by feature or module, then proposes an ordered sequence of structured commit messages following the Conventional Commits specification.

What is the best way to group multiple file changes into logical commits?

The best way to group file changes into logical commits is by analyzing code diffs to detect change groups based on feature, module, or change type. This allows you to plan commit granularity and generate separate messages for each logical unit of work.

Can I automate branch creation when starting new feature work on main?

Yes, you can automate branch creation when on main by providing the repository context. The tool detects the current branch, proposes a fitting branch name for your feature or bug fix, and plans the commits before executing any changes after your confirmation.

How do I plan commit granularity for a refactoring task across multiple modules?

To plan commit granularity for refactoring, the tool analyzes the code diff to identify distinct change groups across modules. It then proposes an ordered plan of commits, ensuring each refactoring step is isolated and traceable with structured messages.

Does the commit planning tool execute Git commands automatically without user confirmation?

No, the commit planning tool does not execute Git commands automatically without user confirmation. It provides a clear commit plan and generated messages first, then executes the branch creation and commits only after you explicitly confirm the proposed changes.