Stats
Actions
Tags
From agent-validator
Activates on explicit validator-aware commit requests to run agent-validate detect, then invoke full validation, checks-only, or skip before committing.
How this skill is triggered — by the user, by Claude, or both
Slash command
/agent-validator:validator-commitThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Commit with explicit validator validation intent. Runs `agent-validate detect` first, validates based on intent (full run, checks only, or skip), handles failures, then commits.
Commit with explicit validator validation intent. Runs agent-validate detect first, validates based on intent (full run, checks only, or skip), handles failures, then commits.
Use this skill only when the user explicitly asks to involve Agent Validator in the commit flow, including full validation, checks-only validation, or intentionally skipping validator state as part of the commit.
Do not choose this skill for a plain "commit", "make a commit", or "commit these changes" request that does not mention validator, gauntlet, checks, validation, or skip.
Run agent-validate detect using Bash:
agent-validate detect 2>&1; echo "DETECT_EXIT:$?"
Check the exit code from the DETECT_EXIT: line:
Parse $ARGUMENTS for a validation intent. Do not prompt the user if a clear intent is found.
| ARGUMENTS pattern | Action |
|---|---|
| Contains "check" or "checks" | Invoke /validator-check (Step 3b) |
| Contains "run", "full", or "all gates" | Invoke /validator-run (Step 3a) |
| Contains "skip" | Run agent-validate skip 2>&1 (Step 3c), then go to Step 4 |
| Empty or no clear intent | Present the three choices below to the user, wait for selection |
Evaluate the "check" or "checks" pattern before the generic "run" pattern, so
phrases like "run checks before commit" select /validator-check.
When prompting the user, present these choices:
Then proceed to the step matching the user's selection.
Invoke /validator-run.
/validator-run skill handles fixing and re-running. After that skill completes, ask the user: "Ready to commit?". Proceed to Step 4 only on confirmation.Invoke /validator-check.
/validator-check skill handles fixing and re-running. After that skill completes, ask the user: "Ready to commit?". Proceed to Step 4 only on confirmation.Run:
agent-validate skip 2>&1
Report the command output to the user, then go to Step 4.
Check whether you have a skill for committing git changes available (excluding validator-commit itself to avoid self-invocation).
<type>: <description>), then run git commit -m "<message>"npx claudepluginhub codagent-ai/agent-validator --plugin agent-validatorManages git commit workflows: checks status and diffs, stages changes selectively, generates and validates conventional commit messages, then executes commits.
Validates git commits against COMMIT_WORKFLOW.md standards: checks AI attribution, single focus, no secrets in diffs, and pre-commit requirements. Blocks invalid commits and provides fix instructions.
Generates conventional git commit messages with automatic type/scope detection from file changes/diffs, runs pre-commit validation for secrets/debug code/large files, stages changes, and executes commit.