validation-gates
Use when validating DaoFlow changes before commit or push, including format, tests, lint, typecheck, conditional instruction checks, and CI follow-through.
Best use case
validation-gates is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Use when validating DaoFlow changes before commit or push, including format, tests, lint, typecheck, conditional instruction checks, and CI follow-through.
Teams using validation-gates should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/validation-gates/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How validation-gates Compares
| Feature / Agent | validation-gates | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Use when validating DaoFlow changes before commit or push, including format, tests, lint, typecheck, conditional instruction checks, and CI follow-through.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# Validation Gates Use this skill before every DaoFlow `git commit` and `git push`. ## Load First 1. Repository root [AGENTS.md](../../../AGENTS.md) 2. The nearest package-level `AGENTS.md` for files you will edit 3. [.agents/workflows/pre-commit.md](../../workflows/pre-commit.md) when you need the full recovery flow ## Gate Order Run these checks in order: 1. `bun run format` 2. `bun run test:unit` 3. `bun run lint` 4. `bun run typecheck` 5. `bun run contracts:check` 6. If the diff touches `AGENTS.md`, `.agents/`, or `.codex/skills/`, run `bun run skills:check` 7. Run changed-surface checks for the files you touched 8. Run [acpx-review](../acpx-review/SKILL.md) ## Push Follow-Through - Ensure Git hooks are installed via `bun install` or `bun run hooks:install`. - Use a conventional commit message. - After push, verify GitHub Actions with `gh run list --limit 2 --json databaseId,status,conclusion,name`. - If CI fails, inspect the failing run with `gh run view <RUN_ID> --log-failed` and loop back to step 1. ## Pass Criteria - Formatting applied cleanly - `bun run test:unit` passes - `bun run lint` reports 0 errors - `bun run typecheck` passes - `bun run contracts:check` passes - `bun run skills:check` passes when instruction files changed - Changed-surface checks pass - ACPX review has no blocking findings - Required CI checks are green after push