skills.rest
gonzoblasco
gonzoblascoCOMMUNITY
Explore all skills by this author →
𝕏@gonzoblascoGitHub

commit

Generate Git commit messages following the Conventional Commits specification.

1|Updated Jul 20, 2026
Search Tags:#git#changelog#code review#version control#git workflow#conventional commits#commit message
One-click install
npx skills add https://github.com/gonzoblasco/ai-developer-stack --skill commit-gonzoblasco
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/gonzoblasco/ai-developer-stack/tree/main/languages-standards/commit
Command: npx skills add https://github.com/gonzoblasco/ai-developer-stack --skill commit-gonzoblasco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Inconsistent or vague Git commit messages make history unreadable, block automated changelog generation, and complicate audits. This Skill enforces the Conventional Commits specification so every commit is structured, reviewable, and machine-parseable. ## Core Features & Use Cases - Standardized Message Format: Enforces the type(scope): description structure with a 72-character header limit, lowercase imperative descriptions, and optional body and footer sections. - Type and Scope Taxonomy: Provides eight commit types (feat, fix, refactor, test, docs, chore, perf, ci) plus conventions for consistent scope naming across an epic. - Hybrid CLI and IDE Workflow: Guides pre-commit review with git status and git diff --staged, then generates the message in a terminal or fills the IDE commit box. - Use Case: After staging changes for a new signup email verification feature, invoke the Skill to produce feat(auth): add email verification on signup with a body explaining the business reason. ## Quick Start Ask the AI to review your staged changes with git status and git diff, then write a Conventional Commits message for them.

Frequently Asked Questions about commit

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): description, where type is one of feat, fix, refactor, test, docs, chore, perf, or ci. Keep the first line under 72 characters, start the description in lowercase, and use imperative mood like "add feature" rather than "added feature".

What commit types are allowed in Conventional Commits?▼

This Skill supports eight types: feat for new features, fix for bug corrections, refactor for behavior-neutral code changes, test for test changes, docs for documentation, chore for maintenance, perf for performance work, and ci for pipeline changes.

How do I choose the right scope for a commit?▼

Scopes name the system layer or business domain that changed, such as auth, db, api, catalog, or payments. Keep scopes consistent across commits in the same epic, and omit the scope entirely when a change spans multiple areas.

What should I do when a commit mixes multiple types?▼

Split the work into two separate commits, one per type, whenever reasonably possible. If the changes cannot be divided cleanly, use the dominant type that best represents the primary purpose of the commit.

Where do breaking changes go in a commit message?▼

Breaking changes belong in the footer as a BREAKING CHANGE note, not in the subject line. The header should still follow the standard type(scope): description format describing the change itself.

When should I not use this commit formatting skill?▼

Do not use it to commit directly to main or an epic branch, since it requires a feature branch as a precondition. It also does not replace environment-specific validation, testing, or expert review of the changes being committed.

Related Skills

Explore More Software Engineering Skills→
theslashdojotheslashdojo

git-diff

Identify and review exact changes across git states with unified diff output.

Official
Advanced
Fabric-ProFabric-Pro
3

changelog-generator

Generate changelogs and release notes from Git commit history.

Official
Basic
HugoAlmeidaMoreiraHugoAlmeidaMoreira

requesting-code-review

Identify and reject code changes failing security, quality, or style gates.

Community
Advanced
dennisonbertramdennisonbertram
1

changelog-gen

Generate release notes from Git history using Conventional Commits and git-cliff.

Community
Advanced