What tool does this skill use for staging?

This skill utilizes 'git-sequential-stage' to safely and precisely stage specific parts of files (hunks) based on a generated patch file.

What is the process-commit skill?

It is a specialized Claude Code skill designed to help developers split complex code changes into smaller, logical commits using granular hunk-level staging.

Does it support staging entire files at once?

Yes, it uses wildcard patterns to stage entire files when the changes are unified, such as when adding new files or performing file-wide refactoring.

When should I trigger this skill?

You should trigger it when you have finished a coding session and need to organize your changes into a clean commit history before creating a Pull Request.

Can it group changes across multiple files?

Yes, the skill analyzes the entire diff across the repository and groups related changes into meaningful commits based on their semantic purpose.

Git Commit Splitter

Name: Git Commit Splitter
Author: HikaruEgashira

byHikaruEgashira

Developer Tools

Automates the process of splitting large code changes into logical, atomic commits using granular hunk-level staging.

About

The process-commit skill empowers Claude to autonomously organize code changes by analyzing diffs and grouping them into meaningful segments before a Pull Request is created. By leveraging the git-sequential-stage tool, it performs precise staging at the hunk level, allowing for a cleaner version control history and more effective code reviews. This skill is ideal for developers who have accumulated multiple types of changes—such as refactoring, bug fixes, and new features—and need to deconstruct them into a logical sequence of commits without manual 'git add -p' intervention.

Key Features

0 GitHub stars
Intelligent wildcard support for staging unified file changes
Autonomous analysis and semantic grouping of code changes
Sequential commit planning to maintain logical development history
Granular hunk-level staging for precise commit control
Automated temporary patch management for stable diff processing

Use Cases

Cleaning up a work-in-progress branch to meet repository commit standards before PR
Separating infrastructure or refactoring changes from functional logic updates
Deconstructing a large feature development session into smaller, reviewable commits

About

Key Features

0 GitHub stars
Intelligent wildcard support for staging unified file changes
Autonomous analysis and semantic grouping of code changes
Sequential commit planning to maintain logical development history
Granular hunk-level staging for precise commit control
Automated temporary patch management for stable diff processing

Use Cases

Cleaning up a work-in-progress branch to meet repository commit standards before PR
Separating infrastructure or refactoring changes from functional logic updates
Deconstructing a large feature development session into smaller, reviewable commits