commit

Plan logical Git commits with structured messages and staged changes.

4|1|Updated May 31, 2015

Search Tags:#git #workflow #planning #commit #diff #message-template

Ready to run

npx skills add https://github.com/samcdavid/dotfiles --skill commit-samcdavid

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/samcdavid/dotfiles/tree/main/claude/skills/commit
Command: npx skills add https://github.com/samcdavid/dotfiles --skill commit-samcdavid

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers avoid large, unfocused commits by guiding them to break changes into small, logical units and to write clear, structured commit messages that include Why, How, Side Effects, and Related Cards.

Core Features & Use Cases

Guided commit planning: analyze the diff and determine logical units of work.
Commit message templating: enforce subject lines and a multi-part message structure (Why, How, Side Effects, Related Cards).
Safe workflow: support partial staging and prevent inclusion of secrets or unrelated changes.
Verification and governance: ensures each commit is independently understandable and ready for review.

Quick Start

Plan your commits with the tool, then execute them using the full commit workflow described.

Frequently Asked Questions about commit

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

FAQPage Schema

How do I split a large git diff into small logical commits?▼

To split a large git diff into small logical commits, this skill reads your full diff, plans multiple independent commits based on logical units of work, and generates structured messages before you execute them.

What is the best way to structure a git commit message template?▼

A structured git commit message template should include subject lines and multi-part bodies covering Why, How, Side Effects, and Related Cards to ensure each commit is independently understandable and ready for review.

How do I avoid committing secrets when staging partial git changes?▼

To avoid committing secrets during partial git staging, this workflow verifies your staged changes and prevents the inclusion of secrets or unrelated files before confirming and executing the final commit.

Can I include ticket references in my git commit workflow?▼

Yes, you can include ticket references in your git commit workflow. The generated commit message template supports optional ticket references within its Related Cards section to link changes directly to your tracking system.

What to do when my git workflow has unfocused commits across multiple files?▼

When your git workflow produces unfocused commits across multiple files, this skill guides you through a four-step process to analyze diffs, plan logical units, format messages, and confirm execution for precise governance.