What problem does it solve? Writing meaningful commit messages is often rushed or skipped, leaving future developers without context about why changes were made. This Skill generates detailed Conventional Commits messages that capture the what, why, and problem solved, enriched with Jira ticket context. ## Core Features & Use Cases - Storytelling Commit Messages: Produces structured messages covering why the change was needed, what changed, and what problem it solves, following Conventional Commits types (feat, fix, refactor, etc.). - Jira Integration: Parses the branch name for ticket IDs (e.g., PROJ-123) and fetches ticket details via the Zapier MCP server to add business context and a Refs footer. - Human-in-the-Loop Context: Asks the user why the change was made with multiple-choice options inferred from the actual diff, then commits and pushes only after explicit confirmation. - Use Case: After finishing a bug fix on branch feature/AGP-582-timeout, say "commit this" and receive a complete message referencing the Jira ticket, your stated motivation, and a technical summary of the staged diff. ## Quick Start Say "commit my changes" after staging your files and confirm the generated commit message when prompted.