{"id":"86d2f9d1-96c4-454e-9a40-b35c5f64da96","shortId":"bTCzUS","kind":"skill","title":"commit-message-storyteller","tagline":"Analyzes git diffs or staged changes and generates narrative commit messages that explain WHY a change was made, not just what changed — following Conventional Commits format. Use when asked to \"write a commit message\", \"generate a commit\", \"describe my changes\", \"what should I c","description":"# Commit Message Storyteller\n\nTransforms raw git diffs and change descriptions into clear, story-driven commit messages that follow the [Conventional Commits](https://www.conventionalcommits.org/) specification. Instead of \"update file.js\", you get messages that communicate intent, context, and impact.\n\n## When to Use This Skill\n\n- User says \"write a commit message\", \"help me commit\", or \"generate a commit\"\n- User pastes a git diff or describes code changes\n- User says \"what should I commit this as?\" or \"summarize my diff\"\n- User wants better commit history for their team or open-source project\n- User is preparing a pull request and wants meaningful commit messages\n\n## Prerequisites\n\nHave at least one of the following ready:\n- Output from `git diff` or `git diff --staged`\n- A description of what you changed and why\n- A list of modified files\n\n## How It Works\n\n### Step 1: Gather the Change Context\n\nAsk the user (or infer from the diff) for:\n\n1. **What changed** — files, functions, logic affected\n2. **Why it changed** — bug fix, new feature, refactor, performance, etc.\n3. **Who/what triggered it** — issue number, user request, tech debt, etc.\n\nIf the user provides a raw `git diff`, extract this context automatically from the diff.\n\n### Step 2: Identify the Commit Type\n\nMap the change to a Conventional Commits type using this guide:\n\n| Type | Use When |\n|------|----------|\n| `feat` | A new feature or capability is added |\n| `fix` | A bug or incorrect behavior is corrected |\n| `refactor` | Code restructured without changing behavior |\n| `perf` | A change that improves performance |\n| `docs` | Documentation only changes |\n| `style` | Formatting, whitespace, missing semicolons (no logic change) |\n| `test` | Adding or updating tests |\n| `chore` | Build process, dependency updates, config changes |\n| `ci` | CI/CD pipeline changes |\n| `revert` | Reverting a previous commit |\n\nSee `references/conventional-commits-guide.md` for detailed examples.\n\n### Step 3: Write the Commit Message\n\nFollow this structure:\n\n```\n(): \n\n\n\n