What problem does it solve? Commit histories often get cluttered with noisy messages containing Co-authored-by trailers, plan numbers, tool references, and review narration, making it hard for maintainers to understand what actually changed. This Skill enforces a clean, developer-friendly commit style for the gokit repository. ## Core Features & Use Cases - Focused staging discipline: Inspects staged versus unstaged changes with git status and git diff --cached, and splits mixed concerns into separate coherent commits. - Message conventions: Produces a single compact imperative subject line under ~72 characters, optionally matching Conventional Commit prefixes when the surrounding history uses them. - Strict exclusions: Never adds Co-authored-by trailers, plan/batch/PR numbers, or tool and session references, and never amends pushed history or runs destructive git commands. - Use Case: After finishing a bug fix in the gokit di module, ask for a commit and receive a message like "Rename Resolve to MustResolve in di container" with nothing extra attached. ## Quick Start Ask the assistant to commit your staged changes in the gokit repository with a clean message describing what changed.