skills.rest
shuymn
shuymnCOMMUNITY
Explore all skills by this author →
Website𝕏@shuymnGitHub

commit

Group code diffs into single, well-scoped git commits.

1|Updated Mar 8, 2015
Search Tags:#git#commit#branching#version-control#diff-analysis#one-change#safe-commit
One-click install
npx skills add https://github.com/shuymn/dotfiles --skill commit-shuymn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/shuymn/dotfiles/tree/main/etc/claude/skills/commit
Command: npx skills add https://github.com/shuymn/dotfiles --skill commit-shuymn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you ensure each git commit represents a single, meaningful change by analyzing code diffs and guiding the commit creation process, reducing messy history and enabling clean rollbacks.

Core Features & Use Cases

  • One-change commits: automatically identify and group changes into discrete commits.
  • Branch support: option to create a new branch before committing.
  • Language support: supports --japanese commit messages when requested and formats messages consistently.
  • Use Case: when preparing a release, use this Skill to craft a series of focused commits that describe each logical change.

Quick Start

Describe the changes you want to commit or paste a diff, and I will generate a single logical commit (with optional branch) ready to apply.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I create a git commit for a single logical change?▼

To create a single logical git commit, provide a patch-ready diff or staged changes and invoke the process to automatically identify each logical unit of change and translate it into a well-scoped commit.

What is the best way to split multiple file changes into discrete git commits?▼

Splitting multiple file changes into discrete git commits requires analyzing code diffs to group modifications into logical units, ensuring each commit represents one meaningful change for clean history and safe rollbacks.

Can I create a new branch before committing my current changes?▼

Yes, you can create a new branch before committing current changes by using the optional branch flag to automatically switch contexts and isolate the staged changes.

Does this workflow support generating commit messages in Japanese?▼

Yes, this workflow supports generating consistent commit messages in Japanese by applying the optional Japanese flag during the commit creation process.

Do I need to stage my changes before generating a focused git commit?▼

You need to provide either staged changes or patch-ready diffs before generating a focused git commit, as explicit invocation requires distinct patch inputs to identify each logical scope.

Why should I avoid committing multiple unrelated changes at once?▼

Avoiding multiple unrelated changes in one git commit prevents messy history, enabling clean rollbacks by ensuring each commit represents a single, well-scoped logical unit of work.

Related Skills

Explore More Software Engineering Skills→
bitsocialnetbitsocialnet
1

commit

Generates logical, formatted git commits from analyzed diffs and predefined scopes.

Official
Intermediate
bswrundquistbswrundquist

commit-and-push

Commit staged changes using conventional commits and push them to the remote repository.

Community
Basic
mathiasbourgoinmathiasbourgoin
2

git-conventions

Standardize git commit messages, branch names, and pull request descriptions.

Community
Intermediate
ebknebkn
8

commit

Stage and commit changes with conventional messages and logical grouping.

Community
Intermediate