process-commit

Automate split commit preparation with git-sequential-stage and hunk planning.

1|1|Updated Nov 27, 2025
One-click install
npx skills add https://github.com/HikaruEgashira/agent-skills --skill process-commit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: process-commit
Source: https://github.com/HikaruEgashira/agent-skills/tree/main/wf/skills/process-commit
Command: npx skills add https://github.com/HikaruEgashira/agent-skills --skill process-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill autonomously triggers when a split commit is needed before creating a PR, enabling you to prepare and assemble logical commits from a set of changes.

Core Features & Use Cases

  • Analyze changed hunks and group related changes into coherent commits.
  • Plan commit boundaries by file and logical change.
  • Automate staging of selected hunks using git-sequential-stage and guide the commit creation workflow.

Quick Start

Navigate to the repository root and run the split-commit workflow to generate staged, logically separated commits before creating a PR.

Frequently Asked Questions about process-commit

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

FAQPage Schema
How do I split staged changes into logical commits before creating a PR?

To split staged changes into logical commits before a PR, you can automate the grouping of changed hunks by file and logical boundary. This process plans commit borders and executes sequential staging with safety checks to ensure a coherent code review history.

What is the best way to group related git hunks into separate commits?

The best way to group related git hunks into separate commits is to analyze the changed hunks and plan commit boundaries by logical change. Automated staging tools can then sequentially stage selected hunks to assemble coherent, logically separated commits.

Can I automate staging selected hunks across multiple files for a release workflow?

Yes, you can automate staging selected hunks across multiple files for a release workflow. By using deterministic steps with sequential staging, the automation guides the commit creation workflow while applying necessary safety checks before finalizing the PR preparation.

When do I need to split commits by hunk before a code review?

You need to split commits by hunk before a code review when large changes require logical commits across multiple files and hunks. This separation ensures that distinct logical changes are isolated, making the review process and release workflow more manageable.

Does automated commit splitting work without manual git staging?

Automated commit splitting handles the staging process by sequentially staging selected hunks based on a planned boundary. It executes the commit creation workflow deterministically, reducing the need for manual git staging while maintaining safety checks.