Commit Helper

This is a straightforward implementation of Conventional Commits that activates when you mention git commits or ask to commit changes. It walks you through the type/scope/subject format, explains what goes in the body and footer, and includes solid examples of both good and bad commits. The guidelines are sensible: imperative mood, 50 character subjects, 72 character body wrapping, proper issue references. It covers the standard types like feat, fix, docs, refactor, and handles breaking changes correctly. If you work on a team that enforces commit conventions or you just want to stop writing terrible commit messages, this gives you the structure without overthinking it.

skills.sh installs: 619
GitHub stars: 66
last updated: Jul 14, 2026

View on GitHub

Install

$ npx -y skills add charon-fan/agent-playbook --skill commit-helper --agent claude-code

Installs into .claude/skills of the current project.

Files

Commit Message Helper

A skill for creating properly formatted Git commit messages following the Conventional Commits specification.

When This Skill Activates

This skill activates when you:

Ask to commit changes
Mention commit messages
Request git commit formatting
Say "commit" or "git commit"

Commit Message Format

<type>(<scope>): <subject>

<body>

<footer>

Types

Type	Description
`feat`	A new feature
`fix`	A bug fix
`docs`	Documentation only changes
`style`	Changes that do not affect the meaning of the code (formatting, etc.)
`refactor`	A code change that neither fixes a bug nor adds a feature
`perf`	A code change that improves performance
`test`	Adding missing tests or correcting existing tests
`chore`	Changes to the build process or auxiliary tools
`ci`	Changes to CI configuration files and scripts
`build`	Changes that affect the build system or external dependencies