git-commits

Create consistent git commits with staged change analysis and conventional classification.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/rghamilton3/mission-control-rack --skill git-commits-rghamilton3
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commits
Source: https://github.com/rghamilton3/mission-control-rack/tree/main/.claude/skills/git-commits
Command: npx skills add https://github.com/rghamilton3/mission-control-rack --skill git-commits-rghamilton3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces mandatory, consistent commit creation and intelligible commit messages at the end of development sessions to prevent lost work and unclear version history.

Core Features & Use Cases

  • Mandatory Auto-Commit Enforcement: Defines explicit triggers and a required workflow to create commits when sessions complete.
  • Pre-Commit Analysis & Classification: Scans staged files, classifies changes into types like feat/fix/refactor/docs, and recommends logical grouping.
  • Commit Message Generation & Multi-Commit Strategy: Produces session-referenced, formatted commit messages and coordinates multi-commit workflows when changes span areas.
  • Execution Protocol & Safety Rules: Provides status checks, pre-commit validation steps, smart staging guidance, verification, and explicit rules to never push or force-push without permission.
  • Use Case: After finishing a focused coding session, run the protocol to produce one or more clear commits that summarize the session and prepare it for archival.

Quick Start

Create commits for all completed tasks in the current session by analyzing staged changes, classifying them by type, and generating session-referenced commit messages.

Frequently Asked Questions about git-commits

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

FAQPage Schema
How do I automate git commits at the end of a development session?

To automate git commits at the end of a session, this Skill triggers a mandatory workflow that analyzes staged files, classifies changes into conventional types, generates formatted commit messages, and verifies the final commit.

How does pre-commit analysis work for grouping staged changes?

Pre-commit analysis scans your staged files and classifies the modifications into conventional types like feat, fix, refactor, or docs. It then recommends logical grouping to orchestrate multiple commits if changes span different areas like frontend and backend.

Can I generate conventional commit messages automatically for staged files?

Yes, you can generate conventional commit messages automatically. The Skill analyzes your staged changes, classifies them by type, and constructs session-referenced messages that summarize your completed development work clearly.

What is the best way to split multi-commit workflows across frontend and backend changes?

The best way to handle multi-commit workflows is to use a Skill that orchestrates commits by classifying staged files and grouping them logically. This ensures frontend, backend, and database changes are separated into distinct, clearly referenced commits.

Does this git automation push or force-push commits to remote repositories?

No, this git automation does not push or force-push to remote repositories. It enforces strict safety rules that prevent pushing without explicit permission, focusing solely on safe, local commit creation and pre-commit validation.

Why should I use automated commit message generation for version control?

You should use automated commit message generation to prevent lost work and maintain a clear version history. It enforces consistent commit creation and produces intelligible, session-referenced messages after focused coding sessions.