Agent skill · software engineering · vishalsachdev
agentic-validators
Design and install validation hooks for coding agents (e.g., Claude Code) to make AI changes safer and more deterministic. Use when you want post-tool-use or stop hooks, automated tests/linters/formatters, parallel subagents with per-file validation, or a repeatable “agent pipeline” with audit logs.
Why this skill is useful
Adds specific patterns and strategies for implementing validation hooks that enhance the safety and determinism of AI-generated code changes.
What it needs
Requires git, node, python installed locally. About 2k tokens when loaded. Last updated 2026-08-01. 4 stars on the source repository.
What this skill does
Agentic Validators Goal Turn “agent wrote code” into “agent wrote code and the change is validated automatically.” This skill helps you: choose the right validation strategy (per-file vs repo-wide) implement post-tool-use and stop hooks create narrow validators (fast, deterministic checks) structure work so multiple agents can run in parallel without losing correctness Mental model Agents are non-deterministic; validators are deterministic. Context is fragile; validation + logs are durable. Prefer small, fast checks close to the change (per-file) + a final global gate (repo-wide). When to use which hook Post-tool-use hook (best default) Use when: you want immediate feedback after edits you can validate the specific file(s) that were touched you want high signal without running the full test suite Typical checks: formatting (prettier/black) linting (eslint/ruff) typecheck for that file/module (tsc --noEmit with project config) Stop hook (end-of-run gate) Use when: you need repo-wide invariants you want one last “exit criteria” check Typical checks: unit tests build integration tests Step-by-step: add validators to a repo 1) Identify file types and fast checks JS/TS: prettier + eslint + typecheck Python: ruff + pytest (optional) Go: gofmt + go test (optional) 2) Implement per-file validator(s) A validator should be: fast (<5–30s) deterministic clear output safe to run repeatedly 3) Wire into hooks Implement post-tool-use hook calling validator with the file path. 4) Add logs Write to a predictable location (e.g., .agent-logs/validators.log) 5) Add a stop-hook “final gate” Run the broader checks once. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills vishalsachdev/agentic-validators