skills.rest
achyutkneupane
achyutkneupaneCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

atomic-semantics-commits

Generates atomic Git commit messages following a modified Conventional Commits specification.

Updated Nov 29, 2025
Search Tags:#git#changelog#version control#conventional commits#commit messages#code history#atomic commits
One-click install
npx skills add https://github.com/achyutkneupane/Blog-Kit --skill atomic-semantics-commits-achyutkneupane
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: atomic-semantics-commits
Source: https://github.com/achyutkneupane/Blog-Kit/tree/main/.ai/skills/atomic-semantics-commits
Command: npx skills add https://github.com/achyutkneupane/Blog-Kit --skill atomic-semantics-commits-achyutkneupane

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing consistent, meaningful Git commit messages is hard to enforce across a project, leading to vague titles, bundled changes, and unreadable history. This Skill enforces a strict commit format so every commit is atomic, traceable, and changelog-friendly. ## Core Features & Use Cases - Strict Type Prefixes: Restricts commits to a fixed set of types (feat, fix, refactor, perf, docs, test, chore, and more) with no scopes or sub-typing allowed. - Formatting Enforcement: Applies third-person present tense verbs, a 72-character title limit, no emojis, and mandatory blank-line separation between title and body. - Breaking Change Handling: Requires an explicit BREAKING CHANGE: note in the body when a commit introduces breaking changes. - Use Case: After staging changes for a new navigation feature, ask the assistant to write the commit message and receive a compliant message like feat: adds sub-navigation with context moved to the body. ## Quick Start Ask the assistant to write a commit message for your staged changes following the atomic semantic commit rules.

Frequently Asked Questions about atomic-semantics-commits

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

FAQPage Schema
How do I write a conventional commit message without scopes?▼

Use a type prefix followed by a colon and a third-person present tense verb, such as `feat: adds sub-navigation`. Never include scopes like `feat(ui):`, and keep the title under 72 characters with context moved to the body.

What commit types are allowed in Conventional Commits?▼

This skill allows feat, fix, improvements, perf, build, ci, refactor, docs, test, style, chore, and other. Each type maps to a specific change category, and alternative words like `feature` are not permitted.

How do I mark a breaking change in a commit message?▼

Include the exact phrase `BREAKING CHANGE:` in the commit body, followed by a space and an explanation of what breaks. The body must be separated from the title by a single blank line.

Why should commits be atomic in Git history?▼

Atomic commits isolate one logical change per commit, making history readable, reviews easier, and rollbacks safer. Bundling a bug fix with a new feature in one commit makes changes harder to trace and revert.

When should a commit message include a body?▼

Add a body only when extra context, reasoning, or explanation is truly necessary, such as explaining why a change was made. Simple changes like dependency bumps need only a title, for example `chore: bumps Laravel to v11.7.0`.

Related Skills

Explore More Software Engineering Skills→
diriendirien
19

commit

Create atomic Git commits using Conventional Commits conventions.

Community
Intermediate
koralliskorallis
90

changelog-generator

Generates changelogs from Git history, commit messages, and pull requests.

Community
Basic
owenlamontowenlamont
1

python-lint-format

Automate Python code linting and formatting with pre-commit hooks.

Community
Advanced
pcsensorpcsensor

chinese-commit-conventions

Configure Chinese Conventional Commits with commitlint, Husky, and Commitizen.

Community
Intermediate