What problem does it solve? Writing consistent, well-formatted commit messages is repetitive and often skipped under time pressure, leading to unreadable git histories. This Skill inspects your current changes and drafts a conventional commit message that matches your project's existing style. ## Core Features & Use Cases - Context Gathering: Runs git diff (staged and unstaged), git status, and recent git log in parallel to understand the full scope of changes. - Scope Detection: Automatically prefers staged changes, falls back to unstaged changes, and reports when there is nothing to commit. - Conventional Commits Output: Produces a type-prefixed message (feat, fix, refactor, chore, docs, test, perf) with an imperative summary under 72 characters and an optional body for non-obvious changes. - Use Case: After staging a bug fix across several files, ask for a commit message and receive a ready-to-paste conventional commit that matches the style of your last ten commits, without running git commit yourself. ## Quick Start Ask the assistant to generate a commit message for your current staged changes.
