/SKILL.md
Auto-split mixed changes into logical commit batches with validated Conventional Commit messages. MUST BE USED for ANY git add, git commit, or git push operation.
npx skillsauth add cnkang/conventional-commit-batcher conventional-commit-batcherInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use this skill to turn a messy working tree into clean, reviewable Conventional Commit history.
This skill MUST be activated for ANY commit-related operation, including:
git add, git commit, or git pushDo NOT run git add or git commit directly without going through this
skill's workflow.
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.
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:
Show me the commit plan first before executing.
Use this prompt only when you want to review the plan before execution:
Inspect my current git changes and split them into logical Conventional Commit batches.
Output a full Commit Plan first.
Do not run git add or git commit until I confirm the plan.
After confirmation, execute each batch one by one.
In auto-execute mode (default), the agent outputs a brief per-batch summary as each batch is committed.
In plan-first mode (user requested), the agent outputs the full plan before any staging/commit:
Commit Plan
Batch #1: <type(scope): subject>
Intent: <why this batch exists>
Files/Hunks:
- <path> (...)
Staging commands:
- git add ...
Commit command:
- git commit -m "..."
references/core-rules.md first.references/core-rules.md as the single source of truth.python3 scripts/precommit_safety_gate.py before every commit attempt
when Python is available; otherwise run the equivalent manual gate checks
from references/core-rules.md..gitignore/local-artifact gate before every commit and require
explicit user confirmation if suspicious files are present.--no-verify.SKILL.mdAGENTS.mdCLAUDE.md, .claude/agents/conventional-commit-batcher.md, .claude/commands/commit-batch.md.kiro/agents/conventional-commit-batcher.json, .kiro/steering/commit-batching.md.agents/skills/conventional-commit-batcher/SKILL.md.agents/agents/conventional-commit-batcher.mdagents/openai.yamlreferences/core-rules.mdreferences/plan-examples.mdreferences/commit-batching-guide.mdreferences/commit-msg-hook-example.mdreferences/codex-setup.mdreferences/claude-setup.mdreferences/kiro-setup.mdreferences/kimi-setup.mdreferences/qwen-setup.mdreferences/gemini-setup.mdscripts/validate_conventional_commit.pyscripts/precommit_safety_gate.pyscripts/test_validate_conventional_commit.pyscripts/test_precommit_safety_gate.pytesting
Auto-split mixed changes into logical commit batches with validated Conventional Commit messages. Activate when user wants to git add, git commit, stage, or push changes.
testing
Create, edit, improve, or audit AgentSkills. Use when creating a new skill from scratch or when asked to improve, review, audit, tidy up, or clean up an existing skill or SKILL.md file. Also use when editing or restructuring a skill directory (moving files to references/ or scripts/, removing stale content, validating against the AgentSkills spec). Triggers on phrases like "create a skill", "author a skill", "tidy up a skill", "improve this skill", "review the skill", "clean up the skill", "audit the skill".
testing
Host security hardening and risk-tolerance configuration for OpenClaw deployments. Use when a user asks for security audits, firewall/SSH/update hardening, risk posture, exposure review, OpenClaw cron scheduling for periodic checks, or version status checks on a machine running OpenClaw (laptop, workstation, Pi, VPS).
testing
Create, edit, improve, or audit AgentSkills. Use when creating a new skill from scratch or when asked to improve, review, audit, tidy up, or clean up an existing skill or SKILL.md file. Also use when editing or restructuring a skill directory (moving files to references/ or scripts/, removing stale content, validating against the AgentSkills spec). Triggers on phrases like "create a skill", "author a skill", "tidy up a skill", "improve this skill", "review the skill", "clean up the skill", "audit the skill".