This repository provides a cross-CLI commit batching skill.
When the user asks to commit, stage, push changes, or when you are about to run
git add, git commit, or git push, you MUST follow the commit batching
workflow defined in references/core-rules.md BEFORE executing any git
staging or commit command.
Do NOT run git add or git commit directly. Always:
- Read
references/core-rules.md - Inspect changes and split into logical batches
- Run safety gates before each commit
- Auto-execute by default: stage and commit directly
- Only output the full Commit Plan and wait for confirmation if the user explicitly asks to review the plan first
- Validate each commit message
This applies to ALL commit scenarios, not just when the user explicitly asks for "batching".
- Always treat
references/core-rules.mdas the authoritative workflow. - Do not duplicate or redefine commit batching rules in loader files.
- Codex:
SKILL.md,AGENTS.md - Claude Code:
.claude/agents/conventional-commit-batcher.md,.claude/commands/commit-batch.md - Kiro CLI:
.kiro/agents/conventional-commit-batcher.json,.kiro/steering/commit-batching.md - Kimi CLI:
.agents/skills/conventional-commit-batcher/SKILL.md - Qwen Code:
.agents/skills/conventional-commit-batcher/SKILL.md,.agents/agents/conventional-commit-batcher.md - Gemini CLI:
.agents/skills/conventional-commit-batcher/SKILL.md,.agents/agents/conventional-commit-batcher.md - OpenAI:
agents/openai.yaml
All entrypoints delegate to references/core-rules.md.