Stats
Actions
Tags
From build
Runs git test precommit checks with build validation, skips on battery power, analyzes and fixes failures until passing. Use after any code changes.
How this skill is triggered — by the user, by Claude, or both
Slash command
/build:precommitThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**CRITICAL**: Before running any build or test commands, check if the machine is on battery power:
CRITICAL: Before running any build or test commands, check if the machine is on battery power:
${CLAUDE_PLUGIN_ROOT}/scripts/check-battery || { echo "⚡ Skipping precommit on battery power"; exit 0; }
git test run HEAD --retest --verbose --verbose
Run git test run HEAD --retest --verbose --verbose to validate code:
git test add (typically autoformatting, builds, tests, and other quality checks)If git test is not configured for this repository, clearly explain the situation and suggest running /build:test-setup to configure it.
When precommit fails (due to: type checking errors, test failures, linting issues, build errors):
Your final message MUST start with one of:
| Task | Use |
|---|---|
| Run precommit and fix | build:precommit-runner agent |
| Test all branch commits | /build:test-branch command |
| Test and autosquash | build:build-fixer-autosquash agent |
npx claudepluginhub motlin/claude-code-plugins --plugin buildRuns pre-commit checks in the order: lint:fix, build, test. Supports multiple ecosystems (Node.js, Python, Rust, Go, Java, Ruby) by detecting project files.
Runs pre-commit workflow: audits staged files for 'any' types, empty catch blocks, console.logs, bugs; executes full test suite; reports commit readiness.
Runs quick validation, pytest suite, and smoke tests before staging and committing Python changes with conventional commit messages. Use when ready to commit.