draft-commitlisted

# 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 messag