Agent skill · writing content · aiskillstore
draft-commit
Draft clear commit messages from staged Git changes without modifying the repository.
Why this skill is useful
Codifies a structured approach to drafting commit messages, which the AI could infer but now has clear guidelines.
What it needs
About 5k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Draft a Commit Create a thoughtful, supportive commit message from your staged changes. Welcome Writing good commit messages is an art. This skill helps you capture the essence of your changes in a clear, inviting way that your future self (and teammates) will appreciate. Your staged changes tell a story. Let's write that story together. --- What You're Doing You're about to: 1. Review what you've staged 2. Understand the nature of your changes 3. Create a commit message that captures both what AND why 4. Copy that message and use it when you commit --- How It Works Step 1: Analyzing Staged Changes First, we'll look at your staged changes using git diff --cached. This shows us: What files changed: Which files did you touch? What changed in them: Added lines? Deleted? Refactored? Patterns: Can we detect what you were working on? Step 2: Understanding Intent From the changes, we infer: Type of work: Feature? Bug fix? Refactoring? Documentation? Scope: Which part of the system? Impact: What improves? What does this enable? Step 3: Drafting the Message We craft a message that: Is specific: Not "Update files" but "Add StandardsRepository abstraction" Explains why: Not just what changed, but why it matters Shows confidence: Your changes are worth celebrating Invites understanding: Future readers will understand your intent Step 4: Sharing with You We display the drafted message so you can: Review it Copy it Use it in your git commit command --- Configuration Loading Configuration The skill reads from .claude/skills/draft-commit/config.json: style: How the message sounds ("supportive" or "concise") format: Message structure ("descriptive" or "conventional") messageLength: How much detail ("concise" or "detailed") includeContext: Add explanatory context (true/false) includeFileCounts: Show file/line counts (true/false) Customizing Behavior Edit config.json to change defaults: --- Process Get Staged Changes Categorize Changes Analyze the diff to understand: Added files, dele …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/draft-commit