Menu

Individual skill

git-commit-helper-guide

0upvotes

A practical guide to crafting atomic commits and clear Conventional-Commit messages — use when committing or standardizing team history.

skills/git-commit-helper-guide/SKILL.md

Read pinned source

Source commit faf37c0859ebf627bfcb5225e8057d088691e0ae

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 8, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
56
Repository last updated
Oct 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

## Overview

Good commits are small, self-explanatory units of change with messages that tell
future readers why the change exists. This guide covers the full craft:
splitting work into atomic commits, writing messages in the Conventional
Commits style, and keeping branch history reviewable — whether you write
messages by hand or draft them with AI assistance.

## When to use

- Turning a messy working tree into clean, logical commits
- Writing commit messages that explain rationale, not just content
- Adopting Conventional Commits (`feat:`, `fix:`) on a team
- Tidying a branch before opening a pull request
Back to top