agentic-validators
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).
More from vishalsachdev/claude-code-skills
paper-writing
Expert guidance for writing high-quality academic and research papers. Use when the user wants to write, structure, revise, or improve academic papers, research articles, conference papers, or technical reports. Provides comprehensive support for all stages from planning to final polish.
744formbuilder-admin
>
5tweet-series-extractor
|
1start-session
Use when user says "let's get started", "where are we", or at beginning of a session. Reads project context from CLAUDE.md, checks git status and recent commits, and provides orientation for the session. Works across all repo types (code, research, mixed).
1codebase-singularity
Apply the codebase singularity approach: reliable codebase understanding and change with a repeatable workflow, guardrails, and verification gates. Use for repo work (feature, bugfix, refactor, migration) when you need high trust, minimal diffs, and explicit validation and exit criteria.
1wrap-up-session
Use when user says "let's wrap up", "close shop", "done for today", or wants to end a session. Handles session wrap-up including git operations, documentation updates, roadmap updates, and preparing for next session. Works across all repo types.
1