skills.rest
Wizarck
WizarckCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

git-commit-helper

Generates Conventional Commits messages with type, scope, and breaking-change footers for staged changes.

2|Updated Apr 19, 2026
Search Tags:#git#changelog#version control#conventional commits#semantic commits#commit message
One-click install
npx skills add https://github.com/Wizarck/nexandro --skill git-commit-helper-wizarck
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit-helper
Source: https://github.com/Wizarck/nexandro/tree/main/skills/git-commit-helper
Command: npx skills add https://github.com/Wizarck/nexandro --skill git-commit-helper-wizarck

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing consistent, informative git commit messages is tedious and often inconsistent across a team. This Skill drafts or rewrites commit messages that follow the Conventional Commits specification, making history searchable and changelog-friendly. ## Core Features & Use Cases - Conventional Commits Formatting: Produces messages with the correct type (feat, fix, docs, refactor, perf, test, chore, ci, build), optional scope, and imperative-mood subject lines under 50 characters. - Structured Body and Footers: Adds explanatory bodies wrapped at 72 characters plus footers for issue references (Fixes #123), BREAKING CHANGE notes, and co-authors. - Use Case: After staging a bug fix in your API module, ask for a commit message and receive something like "fix(api): Prevent race condition in order processing" with a proper body and breaking-change footer. ## Quick Start Ask the assistant to write a Conventional Commits message for your currently staged changes, describing what the change does.

Frequently Asked Questions about git-commit-helper

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

FAQPage Schema
How do I write a Conventional Commits message?▼

Use the format type(scope): subject, where type is one of feat, fix, docs, style, refactor, perf, test, chore, ci, or build. Write the subject in imperative mood under 50 characters, then add an optional body explaining what and why, wrapped at 72 characters.

How to indicate a breaking change in a commit message?▼

Add a footer line starting with BREAKING CHANGE: followed by a description of the breakage and migration impact. Place it in the footer section after the body, alongside any issue references like Fixes #123.

What commit types does Conventional Commits support?▼

Common types include feat for new features, fix for bug fixes, docs for documentation, style for formatting, refactor for restructuring, perf for performance, test for tests, chore for maintenance, ci for pipelines, and build for build system changes.

Can I reference issues and co-authors in commit messages?▼

Yes, use footer lines such as Fixes #123 to link issues and Co-authored-by: Name <email> to credit collaborators. Footers go at the end of the message, separated from the body by a blank line.

Why should commit subjects use imperative mood?▼

Imperative mood ("Add" not "Added") keeps subjects concise and consistent with git's own generated messages like merge commits. It also makes history read like a set of instructions applied to the codebase.

Related Skills

Explore More Software Engineering Skills→
ebknebkn
8

commit

Stage and commit changes with conventional messages and logical grouping.

Community
Intermediate
p-o-ke-naep-o-ke-nae

changelog-automation

Generate changelogs from commits, pull requests, and releases.

Community
Advanced
pandaworks-software-pltpandaworks-software-plt

hermes-commit

Verify code review and lint checks, then execute atomic commits.

Official
Advanced
JiangAustinJiangAustin

chinese-commit-conventions

Standardize Chinese Git commit messages with commitlint, husky, and commitizen.

Community
Intermediate