Why does the skill enforce imperative mood?

Using the imperative mood (e.g., 'add' instead of 'added') is a git best practice because it describes what the commit *does* to the code, matching the style of git's built-in commands.

What is the Conventional Commits 1.0.0 specification?

It is a lightweight convention for commit messages that provides a set of rules for creating an explicit commit history, making it easier for automated tools to manage versions and generate changelogs.

Can I use custom scopes with this skill?

Yes. While the skill provides common examples for different project types, you can define any scope that matches your specific project architecture.

How does this skill handle breaking changes?

It supports two standard methods: adding an exclamation mark (!) before the colon in the header, or including a 'BREAKING CHANGE:' footer at the bottom of the message.

Semantic Git Commits

Name: Semantic Git Commits
Author: maledorak

bymaledorak

•

개발자 도구

Standardizes your git commit history by enforcing the Conventional Commits 1.0.0 specification with automated formatting and validation.

This skill empowers developers to maintain a professional and machine-readable git history by guiding the creation of semantic commit messages. It automates the selection of commit types—such as features, fixes, and documentation—while providing a structured framework for scopes and breaking changes. By adhering to the Conventional Commits 1.0.0 standard, it facilitates automated changelog generation and ensures consistent communication across development teams, making the repository's evolution transparent and easy to navigate for both humans and automation tools.

주요 기능

01Provides context-aware scope suggestions for Web, CLI, and Infrastructure architectures.

022 GitHub stars

03Ensures git best practices such as imperative mood, lowercase descriptions, and character limits.

04Supports multiple breaking change indicators including '!' syntax and 'BREAKING CHANGE' footers.

05Automatically appends Claude Code attribution and co-author metadata to every commit.

06Enforces Conventional Commits 1.0.0 types like feat, fix, docs, and refactor for SemVer clarity.

사용 사례

01Explicitly marking breaking API changes to ensure accurate semantic versioning (SemVer) releases.

02Improving codebase auditability by requiring detailed context in commit bodies and issue references.

03Standardizing commit messages across distributed teams to enable automated changelog generation.

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add maledorak/maledorak-marketplace git-commit

For use in Claude.ai and ChatGPT

Download Skill