commit

Name: commit
Availability: InStock
Author: kangmomin

Organize code changes into logical commits with standardized messages.

1|1|Updated Apr 9, 2026

Search Tags:#git #workflow #commit #code-review #version-control #change-management

Ready to run

npx skills add https://github.com/kangmomin/harness-plugins --skill commit-kangmomin

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/kangmomin/harness-plugins/tree/main/be-harness/skills/commit
Command: npx skills add https://github.com/kangmomin/harness-plugins --skill commit-kangmomin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Organize changes into logical commits, helping maintain a clean project history and simpler review.

Core Features & Use Cases

Structured Commit Workflow: Split related changes into self-contained commits.
Clear Commit Messages: Follow the provided conventions to describe each change type.
Guided Workflow: Steps for reviewing status, grouping changes, and sequentially committing them.

Quick Start

Split your current changes into logical commits following the guided steps and commit from the core change to the smallest unit.

Frequently Asked Questions about commit

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

FAQPage Schema

How do I split changes into logical commits for code review?▼

To split changes into logical commits, you categorize edits by type, group related modifications into self-contained units, and commit sequentially from the core change to the smallest unit. This maintains a clean project history and simplifies collaborative reviews.

Why should I use one commit per change in version control?▼

Using one commit per change ensures each modification is self-contained and logically grouped. This change management practice keeps your project history clean, making collaborative code reviews simpler and more focused on individual features or fixes.

What is the best way to write clear git commit messages for mixed changes?▼

The best way to write clear git commit messages for mixed changes is to split them into self-contained commits first, then apply a standardized commit message format to describe each specific change type, such as features, fixes, or refactors.

Can I group related code edits into a single git commit?▼

Yes, you can group related code edits into a single git commit. The workflow reviews your current status, categorizes modifications, and sequentially commits related edits together, ensuring each commit represents one logical change.

Does this commit workflow handle features, fixes, and refactors together?▼

Yes, this commit workflow handles features, fixes, refactors, and docs together. It guides you through categorizing these mixed changes and grouping related edits into separate, self-contained commits for cleaner collaborative project history.

What are the limitations of manually organizing git commits?▼

Manually organizing git commits lacks enforced steps, risking mixed changes in a single commit. This workflow overcomes limitations by prescribing a standardized commit message format and enforcing one-commit-per-change sequentially from core to smallest unit.