conventional-commit-batcherlisted

# Conventional Commit Batcher Use this skill to turn a messy working tree into clean, reviewable Conventional Commit history. ## Commit Interception (MANDATORY) This skill MUST be activated for ANY commit-related operation, including: - user asks to commit, stage, or push changes - user asks to "save" or "check in" code - any workflow that would result in `git add`, `git commit`, or `git push` Do NOT run `git add` or `git commit` directly without going through this skill's workflow. ## Use This Skill When - any commit operation is performed through an agent (automatic interception) - changes from different intents are mixed in one branch - you want a plan-first commit process before opening a PR - you need reliable Conventional Commit messages across team and agents ## Skip This Skill When - the change is tiny and clearly single-intent - you only need one quick commit without batching Note: even when the skill could be skipped, if it is installed, the agent will still run the workflow and safety gates. The result may be a single batch, which is fine. ## Default Behavior: Auto-Execute By default, the skill inspects changes, splits into logical batches, runs safety gates, and commits directly — without waiting for user confirmation. To see the plan before execution, explicitly ask: ```text Show me the commit plan first before executing. ``` ## High-Success Prompt (Plan-First Mode) Use this prompt only when you want to review the plan before execution: ```text In