Menu
This skill should be used when handling verification steps, quality gates, pre-commit checks, test failures, lint errors, build verification, or mandatory validation before task completion.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Search prior session history to recall how similar work was handled before. Use when you want to leverage a past approach, check prior experience on a topic, answer "how was this handled before", or cross-verify current handling against precedent from earlier sessions.
This skill should be used when looking up which agents own or consume specific skills, understanding skill-agent relationships, or routing tasks based on skill ownership.
This skill should be used when the user provides a vague request, asks to clarify requirements, structure a task, or refine a prompt for multi-agent orchestration.
This skill should be used when handling agent model selection, tool access permissions, behavioral guardrails, MCP tool preferences, or any question about what agents can/cannot do.
Turn any codebase into a beautiful, interactive single-page HTML course that teaches how the code works to non-technical people. Use this skill whenever someone wants to create an interactive course, tutorial, or educational walkthrough from a codebase or project. Also trigger when users mention 'turn this into a course,' 'explain this codebase interactively,' 'teach this code,' 'interactive tutorial from code,' 'codebase walkthrough,' 'learn from this codebase,' or 'make a course from this project.' This skill produces a stunning, self-contained HTML file with scroll-based navigation, animated visualizations, embedded quizzes, and code-with-plain-English side-by-side translations.
This skill should be used when classifying tasks, routing to agents, determining complexity, or handling task routing, agent selection, verification requirements, and multi-component changes.
| name | verification-gates |
| description | This skill should be used when handling verification steps, quality gates, pre-commit checks, test failures, lint errors, build verification, or mandatory validation before task completion. |
Verification gates are mandatory quality checkpoints that must pass before any implementation work is considered complete. These gates prevent broken code from being committed, ensure type safety, maintain code style consistency, and validate that all tests pass.
Owner Agent: Alphonse (Verifier Agent)
Loid (Executor) Alphonse (Verifier)
| |
Quick sanity tests Full verification gate
during implementation before completion
| |
+----------> Handoff >----+
| Check | Example Command | Timeout |
|---|---|---|
| Lint | npm run lint / ruff check | 30s |
| Format | npm run format:check / black --check | 15s |
| Quick Tests | Changed file tests only | 60s |
| Check | Example Command | Timeout |
|---|---|---|
| Full Test Suite | npm test / pytest | 300s |
| Type Checking | npx tsc --noEmit / mypy . | 120s |
| Linting | Full codebase lint | 60s |
| Build | npm run build / python -m build | 180s |
Triggered by changes to sensitive files or security-critical code:
| Check | Trigger | Action |
|---|---|---|
| Credential Scan | *.env, *secret*, *.key | Block + Alert |
| Permission Check | Auth/ACL code | Require review |
| Dependency Audit | Package files | npm audit / pip-audit |
| Action | Node.js | Python | Go | Rust |
|---|---|---|---|---|
| Test | npm test | pytest | go test ./... | cargo test |
| Types | npx tsc --noEmit | mypy . | go build | cargo check |
| Lint | npm run lint | ruff check . | golangci-lint run | cargo clippy |
| Build | npm run build | python -m build | go build | cargo build |
For complete command reference, see references/verification-commands.md.
## Verification Results
### Tests
- Status: [PASS | FAIL]
- Output: [Summary of test execution]
### Type Check
- Status: [PASS | FAIL | SKIPPED]
- Errors: [List of type errors if any]
### Lint
- Status: [PASS | FAIL | SKIPPED]
- Warnings: [Count and summary]
### Build
- Status: [PASS | FAIL | SKIPPED]
- Issues: [Build errors if any]
### Overall: [VERIFIED | FAILED | ENVIRONMENT_BLOCKED]
| Type | Severity | Action |
|---|---|---|
| Test Failure | BLOCKING | Fix and re-run |
| Type Error | BLOCKING | Resolve types |
| Lint Error | BLOCKING | Auto-fix or manual |
| Build Failure | BLOCKING | Fix compilation |
| Security Alert | CRITICAL | Immediate remediation |
| Timeout | WARNING | Retry once |
| Flaky Test | WARNING | Retry 3x, then fix |
Alphonse Reports -> Loid Reviews
| |
Simple Fix? Complex Issue?
| |
YES NO
| |
Loid Fixes Escalate to Lawliet
| |
Re-verify Architecture Review
For detailed failure protocols, see references/failure-handling.md.
any--no-verify flag| Scenario | Gate Type | Checks Run |
|---|---|---|
| Small code fix | Pre-Commit | Lint, format, affected tests |
| New feature complete | Pre-Complete | Full suite, types, lint, build |
| Security-related change | Security | Credential scan, audit, permissions |
| Cross-service change | Integration | E2E, contracts, compatibility |
Verification gates can ONLY be skipped when:
Override Documentation Required:
## Verification Override
Reason: [Explicit reason for skipping]
Requested by: [User or escalation source]
Risk Assessment: [Low/Medium/High]
Compensating Controls: [What will catch issues later]
Disagreement rule: See the canonical truth table in
commands/orchestrate.md Phase 4 (Codex co-review). The summary: Lawliet's
NEEDS_CHANGES always wins; Codex's NEEDS_CHANGES/BLOCKED requires a file:line
citation to flip the verdict.
| File | Purpose |
|---|---|
scripts/load-project-context.sh | Project type detection |
hooks/scripts/verify-completion.sh | Pre-complete gate implementation |
hooks/scripts/validate-changes.sh | Security validation |
agents/Alphonse.md | Verifier agent definition |