Agent skill
precommit
Pre-commit checks — lint:fix -> build -> test
Install this agent skill to your Project
npx add-skill https://github.com/sd0xdev/sd0x-dev-flow/tree/main/skills/precommit
SKILL.md
Pre-Commit Checks (Full)
Trigger
- Keywords: precommit, pre-commit, lint and test, quality gate
When NOT to Use
- Quick checks without build (use
/precommit-fast) - Verification loop without lint:fix (use
/verify) - Just running tests (run directly)
Workflow Steps
| Step | Goal | Safety | Skip if Missing |
|---|---|---|---|
| lint-fix | Auto-fix code style issues | read-write | yes |
| build | Verify compilation succeeds | read-only | yes |
| test-unit | Run full test suite | read-only | yes |
Failure behavior: continue-all (run all steps, report all results)
Task
Run pre-commit checks: lint:fix -> build -> test
Step 1: Check for runner script
Use Glob to check if .claude/scripts/precommit-runner.js exists in the project root.
- Found → run:
node .claude/scripts/precommit-runner.js --mode full --tail 80- If runner succeeds, use its output and skip to the Output section.
- If runner fails, treat as a real precommit failure (do not silently fallback).
- NOT found → Auto-install attempt (see precommit-fast for identical auto-install logic), then fallback to Step 2.
Step 2: Fallback (no runner script)
Detect the project ecosystem to run steps manually.
Ecosystem detection:
| Manifest | Ecosystem | Lint-fix | Build | Test |
|---|---|---|---|---|
package.json |
Node.js | {pm} lint:fix |
{pm} build |
{pm} test:ci / test / test:fast / test:unit |
pyproject.toml |
Python | ruff check --fix . |
— | pytest tests/unit/ |
Cargo.toml |
Rust | cargo clippy --fix |
cargo build |
cargo test |
go.mod |
Go | golangci-lint run --fix |
go build ./... |
go test ./... |
build.gradle |
Java (Gradle) | ./gradlew spotlessApply |
./gradlew build |
./gradlew test |
pom.xml |
Java (Maven) | mvn spotless:apply |
mvn compile |
mvn test |
Gemfile |
Ruby | bundle exec rubocop -a |
— | bundle exec rspec |
For Node.js projects, auto-detect package manager from lockfile.
| Step | package.json script | If missing |
|---|---|---|
| lint:fix | lint:fix |
Skip with note |
| build | build |
Skip with note |
| test | test:ci → test → test:fast → test:unit |
Skip with note |
After lint:fix completes, run git diff --name-only to capture auto-fixed files.
Output
## Precommit (full)
## Results
| Step | Status | Notes |
|------|--------|-------|
| lint:fix | ✅/❌/⏭️ | skipped if no script |
| build | ✅/❌/⏭️ | skipped if no script |
| test | ✅/❌/⏭️ | skipped if no script |
## Changed Files (after lint:fix)
- <files or "(none)">
## Overall: ✅ PASS / ❌ FAIL
## Checklist
- [ ] All available checks pass
- [ ] git status reviewed
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
runbook
Generate and update feature release runbooks from existing docs and codebase. Use when: creating operational runbook, release handbook, deployment checklist, pre-release preparation. Not for: incident response (v2), code review (use codex-code-review), architecture design (use architecture).
ask
Context-aware Q&A with auto context gathering. Use when: user has a quick question about codebase, git history, rules, docs, or skills during development. Not for: code changes (use feature-dev), code review (use codex-review-fast), deep research (use deep-research), full code trace (use code-explore). Output: structured answer with source attribution.
project-brief
Convert a technical spec into a PM/CTO-readable executive summary. Simplify technical details, focus on business value.
codex-test-gen
Generate unit tests for specified functions using Codex MCP
bug-fix
Bug fix workflow. Use when: fixing bugs, resolving issues, regression fixes. Not for: new features (use feature-dev), understanding code (use code-explore). Output: fix + regression test + review gate.
skill-health-check
Validate skill quality against routing, progressive loading, and verification criteria. Use when: auditing skills, checking skill health, reviewing skill design. Not for: code review (use codex-code-review) or doc review (use doc-review). Output: health report with per-skill ratings + Gate.
Didn't find tool you were looking for?