skills.rest
ArMaTeC
ArMaTeCCOMMUNITY
Explore all skills by this author →
GitHub

git-commit

Analyzes staged changes and creates conventional git commits with structured messages.

Updated Mar 9, 2026
Search Tags:#git#code review#version control#commit#conventional commits#staging#diff
One-click install
npx skills add https://github.com/ArMaTeC/Redball --skill git-commit-armatec
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/ArMaTeC/Redball/tree/main/.devin/skills/git-commit
Command: npx skills add https://github.com/ArMaTeC/Redball --skill git-commit-armatec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing clear, consistent commit messages is tedious and often neglected, leading to messy git histories that are hard to review, search, and revert. This Skill analyzes your working tree and produces well-structured conventional commits with properly staged files. ## Core Features & Use Cases - Change Analysis: Reviews git status and diffs (staged and unstaged) to understand exactly what is being committed. - Commit Splitting: Detects unrelated changes mixed together and splits them into separate logical commits. - Conventional Commit Messages: Generates messages following the type(scope): subject format with rules for imperative mood, length limits, body, and footer conventions. - Use Case: After finishing a bug fix plus an unrelated config tweak, ask the assistant to commit your work; it stages each group separately and creates two clean commits such as fix(auth): handle expired tokens and chore(config): update build settings. ## Quick Start Ask the assistant to review my current git changes and create well-structured conventional commits for them.

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

Use the format type(scope): subject, where type is feat, fix, refactor, docs, test, chore, perf, or ci. Keep the subject in imperative mood, lowercase, under 70 characters, and explain what and why in the body wrapped at 72 characters.

How do I split mixed changes into multiple git commits?▼

Review git status and diffs to identify logical groupings of related changes, then stage and commit each group separately. Stage specific files rather than using git add . to keep unrelated work out of a single commit.

What commit types exist in conventional commits?▼

The common types are feat for new features, fix for bug fixes, refactor for code restructuring, docs for documentation, test for test changes, chore for maintenance, perf for performance, and ci for pipeline changes.

What if nothing is staged when I try to commit?▼

The Skill reads the unstaged diff to understand what could be committed, then stages the appropriate specific files before creating the commit. It avoids blanket staging commands to keep commits focused.

When should I not use conventional commit splitting?▼

Avoid splitting when all changes belong to one logical unit of work, since fragmenting a coherent change creates noisy history. Splitting is only appropriate when unrelated changes are mixed together.

Related Skills

Explore More Software Engineering Skills→
evanpurkhiserevanpurkhiser
33

git-status

Scan local directories for git repositories and report uncommitted and unpushed changes.

Community
Intermediate
VYRE-StudiosVYRE-Studios

commit-push-pr

Commit staged changes, push the branch, and open a pull request via GitHub CLI.

Official
Intermediate
owenlamontowenlamont
1

python-lint-format

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

Community
Advanced
fullykubedfullykubed
2

Git

Automate Git commits, rebases, and squashes with safety prompts.

Community
Advanced