commit

Plan and execute single-responsibility git commits from staged and unstaged changes.

Updated May 6, 2026
One-click install
npx skills add https://github.com/Roy-wonji/claude-config --skill commit-roy-wonji
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/Roy-wonji/claude-config/tree/main/skills/commit
Command: npx skills add https://github.com/Roy-wonji/claude-config --skill commit-roy-wonji

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents messy, multi-purpose commits by analyzing your git changes and restructuring them into small, single-responsibility commits that are easier to review, revert, and maintain.

Core Features & Use Cases

  • SRP-based commit splitting: Separates mixed changes into distinct commits by purpose (feat/fix/refactor/test/chore/docs/style).
  • Dependency-aware grouping: Keeps logically coupled files together (e.g., implementation with tests, Protocol + Conformance, model + dependent code).
  • Interactive safety checks: Shows a commit plan for approval and avoids running commits before confirmation.

Quick Start

Describe your desired outcome, and ask the AI to run the commit planner for your current working tree and propose an SRP-aligned commit sequence for user approval.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I split mixed git changes into single-responsibility commits?

Split mixed git changes into single-responsibility commits by analyzing staged and unstaged diffs, grouping coupled files by purpose, and executing sequential conventional commits after user confirmation. This prevents messy multi-purpose commits by structuring changes according to the single-responsibility principle.

What is the best way to plan conventional commits for refactoring and feature work?

Plan conventional commits by gathering git status, diffs, and history to produce a structured commit sequence with conventional types like feat, fix, and refactor. The plan separates refactoring, feature work, and tests into distinct commits, requiring user approval before executing sequential commits using explicitly staged files.

Can I group implementation files with their tests when splitting git commits?

Group implementation files with their tests using dependency-aware commit planning that keeps logically coupled files together. This ensures protocol and conformance pairs or model and dependent code remain in the same single-responsibility commit rather than being separated into isolated chunks.

Does this commit planning approach run git commits automatically without user confirmation?

This commit planning approach does not run git commits automatically without user confirmation. It presents a structured commit plan for approval and avoids executing sequential commits before the user explicitly confirms, preventing unsafe bulk adds and ensuring safe application of staged files.

How do I avoid unsafe bulk git adds when separating formatting changes from feature changes?

Avoid unsafe bulk git adds by using a commit planner that stages files explicitly based on a structured commit plan. It separates formatting and linting changes from feature changes by analyzing diffs and applying each purpose group as a distinct commit without using unsafe bulk add commands.