commit-hd

Name: commit-hd
Availability: InStock
Author: kangmomin

Organize code changes into logical Git commits with consistent messages.

1|1|Updated Apr 9, 2026

Search Tags:#git #workflow #commit #history #code-quality #version-control

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

개발자는 변경 내용을 논리적 단위로 분리해 커밋하는 것이 어려운 경우가 많습니다. 이 스킬은 작업을 의미 있는 커밋 단위로 나누고 일관된 커밋 메시지로 기록하도록 돕습니다.

Core Features & Use Cases

변경 사항을 기능 단위, 버그 수정, 리팩토링 등으로 그룹화하고 각 그룹마다 독립적인 커밋을 생성합니다.
커밋 메시지 규칙에 따라 일관된 포맷으로 메시지를 작성해 깔끔한 히스토리를 유지합니다.
Use Case: 새로운 기능 구현 중 여러 파일이 하나의 기능 변경에 속하는 경우, 해당 변경을 하나의 커밋으로 묶고 이후 수정은 별도의 커밋으로 남깁니다.

Quick Start

Split your ongoing changes into logical commits as you work to create a clean git history.

Frequently Asked Questions about commit-hd

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

FAQPage Schema

How do I split scattered git changes into logical commits?▼

A clean git commit history requires grouping related file changes into independent units. Categorize ongoing changes as features, bug fixes, or refactoring, then stage and commit each group separately with consistent messages.

What is the best way to write consistent git commit messages for refactoring?▼

Consistent git commit messages are produced by following a defined commit convention. Categorize changes as features, bug fixes, or refactoring, then compose structured messages for each staged group to maintain a clean project history.

How do I group multiple files into a single feature commit?▼

Group multiple files into a single feature commit by identifying changes belonging to one feature, staging only those related files, and committing them as one unit. Leave unrelated modifications for separate, subsequent commits.

Can I use this workflow for any Git repository?▼

Yes, this structured commit workflow applies to any Git repository. It categorizes changes, stages related files, composes meaningful commit messages, and validates the history across typical software development tasks.

When do I need to organize code changes into logical commit units?▼

Organize code changes into logical commit units when your working directory has mixed modifications. Splitting simultaneous feature work, bug fixes, and refactoring into separate commits prevents a scattered and confusing project history.

Does organizing commits by logical units affect version control history validation?▼

Yes, organizing commits by logical units directly improves version control history validation. Structured commits with consistent messages make it easier to review project history clarity and identify specific modifications during audits.