skills.rest
BTreeMap
BTreeMapOFFICIAL
Explore all skills by this author →
WebsiteGitHub

git-commit

Drafts and reviews Conventional Commits messages with tiered effort levels and optional push.

2|2|Updated Jun 21, 2026
Search Tags:#git#code review#version control#conventional commits#commit message#git push#breaking change
One-click install
npx skills add https://github.com/BTreeMap/SKILLs --skill git-commit-btreemap
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/BTreeMap/SKILLs/tree/main/git-commit
Command: npx skills add https://github.com/BTreeMap/SKILLs --skill git-commit-btreemap

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Writing consistent, well-formed commit messages is tedious and often skipped, leaving repositories with vague history that is hard to audit, search, or revert. This Skill drafts and reviews Conventional Commits messages that explain why a change was made, not just what changed. ## Core Features & Use Cases - Tiered effort levels: Choose lite (subject line only), full (scoped subject plus wrapped body and footer), or ultra (adds atomicity and history-consistency audits) to match the cost to the task. - Conventional Commits enforcement: Validates type, scope, imperative mood, 70-character subjects, 72-character body wrapping, and footer placement for issue references and breaking changes. - One-step commit and push: With the push verb, stages, commits, and pushes to the tracked remote, reporting the pushed range in one line. - Use Case: After staging a fix across the auth module, run the ultra level to audit atomicity, detect a breaking change in a removed endpoint, and produce a commit message with the correct scope and a BREAKING CHANGE footer. ## Quick Start Ask the agent to draft a Conventional Commits message for the currently staged changes, optionally specifying lite, full, or ultra and whether to push.

Frequently Asked Questions about git-commit

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

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

Stage your changes with git add, then invoke the skill to draft a message in the format type(scope): subject. The default full level adds a wrapped body explaining what changed and why, plus a footer for issue references.

What is the difference between lite, full, and ultra commit levels?▼

Lite outputs only a subject line with scope derived from staged paths. Full adds a wrapped body, footer, and scope resolved from recent git history. Ultra runs atomicity, scope-consistency, and breaking-change audits before drafting.

Can the skill commit and push in one step?▼

Yes, passing the push verb stages as directed, commits, and pushes to the tracked remote, then reports the pushed range in one line. Without an explicit level, push implies lite; an explicit level like full push drafts at that level first.

How are breaking changes handled in commit messages?▼

Breaking changes always require a BREAKING CHANGE: footer followed by the concrete migration path. At the ultra level, the staged diff is scanned for removed public functions, endpoints, CLI flags, config keys, and schema changes to detect them.

Does the skill rewrite bot or merge commits?▼

No, bot-authored commits and platform-generated merge commits are retained exactly as they are. The formatting rules apply only to messages the skill drafts or reviews for regular commits.

Related Skills

Explore More Software Engineering Skills→
nsollazzonsollazzo

smart-commit

Clusters uncommitted git changes into logical groups with conventional commit messages.

Community
Intermediate
Dev10x-GuruDev10x-Guru
7

Dev10x:gh-pr-create

Automate GitHub pull request creation with ticket extraction and Job Story summaries.

Official
Advanced
pd-phucpd-phuc

implement

Implements work items from a PRD or issues using TDD and code review.

Community
Basic
Unique-AGUnique-AG
5

changelog-pyproject

Update CHANGELOG.md and pyproject.toml versions from commit history.

Official
Intermediate