check

Invoke the check skill on your uncommitted changes and it detects the repo's own toolchain — package.json scripts, Turbo, Makefile, pyproject.toml, Cargo.toml, or go.mod — then runs static analysis, build, and tests, auto-fixing safe failures until the run converges.

The check skill prefers the repo's Turbo pipeline when turbo.json exists, scoping typecheck, lint, build, and test to changed packages. It iterates up to 5 times, applying auto-fixable fixes like missing imports and simple type mismatches, then reports anything needing human review.

Yes. It detects pyproject.toml tools like ruff, mypy, and pytest, runs cargo check, clippy, and test for Rust, and go vet, build, and test for Go. It always uses the repo's own commands rather than hardcoding a stack.

The check skill fixes mechanical failures — types, lint, format, build, and test errors — in a fast local loop. It does not hunt correctness bugs, which is code-review's job, and does not exercise runtime behavior, which is verify's job.

Complex generic or inference errors, changes in generated-code directories, public API or contract changes, circular dependencies, and security concerns like hardcoded secrets are flagged for human review rather than auto-fixed. The skill stops after 5 iterations and reports remaining failures.