skills.rest
kellymears
kellymearsCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

git:commits

Organize uncommitted git changes into atomic conventional commits with scoped messages.

Updated Feb 6, 2026
Search Tags:#git#version control#git workflow#conventional commits#code organization#commit history
One-click install
npx skills add https://github.com/kellymears/agents --skill git-commits-kellymears
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git:commits
Source: https://github.com/kellymears/agents/tree/main/plugins/git/skills/git-commits
Command: npx skills add https://github.com/kellymears/agents --skill git-commits-kellymears

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Messy working directories and tangled commit histories make code review painful and obscure what actually changed. This Skill surveys your git state, groups changes by logical scope, and produces a clean series of atomic conventional commits. ## Core Features & Use Cases - Change Categorization: Groups modified files by type (feat, fix, refactor, docs, style, test, chore) and scope so each commit does one thing. - History Reorganization: Uses soft reset to restage recent commits into logical units without losing work. - Safety Guardrails: Blocks force pushes to main, refuses --no-verify, stashes before destructive operations, and skips secrets like .env files. - Use Case: You have five modified files spanning an auth bug fix, a new UI button variant, and README updates. The Skill proposes three commits — fix(auth), feat(ui), docs — waits for your confirmation, then stages and commits each group with conventional messages. ## Quick Start Ask the assistant to clean up your uncommitted changes and organize them into well-scoped conventional commits.

Frequently Asked Questions about git:commits

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

FAQPage Schema
How do I split uncommitted changes into multiple commits?▼

Stage files in logical groups with git add and create a separate conventional commit for each group. Group changes by type (feat, fix, docs) and scope (module or component) so each commit does one thing.

How to reorganize recent git commits without losing work?▼

Use git reset --soft HEAD~N to undo the last N commits while keeping all changes staged, then restage and recommit them in logical groups. This preserves your work while letting you rewrite the commit structure.

What is the conventional commits format for git messages?▼

Conventional commits use the format type(scope): description, where type is feat, fix, refactor, docs, style, test, or chore, and scope names the affected module. An optional body explains the why behind the change.

Can I force push after rewriting git commit history?▼

Force pushing to main or master is blocked by this workflow's safety rules and should generally be avoided on shared branches. Rewriting published history breaks collaborators' clones, so only reorganize commits that have not been pushed.

What happens when a pre-commit hook fails during commit cleanup?▼

Fix the underlying issue reported by the hook and create a new commit rather than amending the previous one. Never bypass hooks with --no-verify, since they enforce project quality checks.

Related Skills

Explore More Software Engineering Skills→
lbusselllbussell

commit

Generate atomic Git commits with imperative subject lines and explanatory bodies.

Community
Intermediate
fallow-rsfallow-rs
4.4k

open-draft-pr

Commits, pushes, and opens a ready pull request for local changes on GitHub.

Official
Basic
nampham2nampham2

dqx-quality-gate

Run pytest suites, verify 100% coverage, and validate pre-commit hooks.

Community
Advanced
dimagidimagi
3

git-rebase

Automate git rebase workflows with fixup commits and autosquash.

Official
Intermediate