git-commit

Create well-structured git commits with convention-aware messages from working tree changes.

6|2|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/Jerrylalala/compound-engineering --skill git-commit-jerrylalala
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/Jerrylalala/compound-engineering/tree/main/plugins/compound-engineering/skills/git-commit
Command: npx skills add https://github.com/Jerrylalala/compound-engineering --skill git-commit-jerrylalala

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing clear, consistent commit messages is tedious and often skipped, leaving repositories with vague history that is hard to review or revert. This Skill automates the creation of well-structured git commits that follow your repository's existing conventions. ## Core Features & Use Cases - Convention Detection: Infers commit message style from project instructions or recent commit history, falling back to conventional commit format (feat, fix, docs, etc.). - Logical Commit Splitting: Groups changed files into separate commits when they represent distinct concerns, keeping history clean. - Branch Safety Checks: Warns before committing directly to main/master and handles detached HEAD states by offering to create a feature branch. - Use Case: After finishing a bug fix and a small refactor in the same session, ask for a commit and get two separate, properly formatted commits with messages matching your repo's style. ## Quick Start Ask the assistant to commit my current changes with a clear message following the repo's conventions.

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 good git commit message automatically?▼

This Skill analyzes your working tree diff and recent commit history to generate a commit message matching your repo's conventions. If no pattern exists, it defaults to conventional commit format like 'feat(scope): description' with an optional explanatory body.

How to split changes into multiple logical commits?▼

The Skill scans changed files for naturally distinct concerns, such as a refactor in one directory and a feature in another, and creates separate commits per group. Grouping happens at the file level only, keeping two or three logical commits rather than many tiny ones.

Does it follow conventional commit format?▼

Yes, conventional commits are the default when no repo convention is detected. It first checks project instructions like AGENTS.md or CLAUDE.md, then recent commit history, and only falls back to the type(scope): description format if neither provides a pattern.

What happens if I commit directly on the main branch?▼

The Skill detects when the current branch is main, master, or the remote default branch and warns you before committing. It asks whether to continue or create a feature branch first, deriving the branch name from the change content.

Can it commit when git is in detached HEAD state?▼

Yes, but it first explains that a branch is required if you want the work attached to one. It asks whether to create a feature branch; if you decline, it proceeds with the detached HEAD commit.