// Run a read-only verification pass after implementation to check whether completion claims are real, validation actually ran, and obvious edge cases or regressions were missed.
Consolidate recent logs, sessions, and existing memory files into durable topic memories, normalize dates, prune stale entries, and keep MEMORY.md short enough for prompt use.
Build a lightweight proactive mode with scheduled checks, sleep intervals, concise user briefs, and expiry safeguards so an agent can work in the background without becoming an uncontrolled daemon.
Extract durable memories from recent conversation turns into user, feedback, project, and reference categories while avoiding stale code-state facts.
Compress a long agent conversation into a nine-part continuation summary that preserves request, files, errors, user messages, current work, and the next aligned step.
Coordinate multiple agents by splitting work into research, synthesis, implementation, and verification, assigning ownership, and keeping the coordinator focused on integration rather than raw exploration.
| name | verification-gate |
| description | Run a read-only verification pass after implementation to check whether completion claims are real, validation actually ran, and obvious edge cases or regressions were missed. |
Use this skill when the implementation should not be accepted without a separate challenge pass.
Collect a verification context from a git repo:
python3 {baseDir}/scripts/verification_context.py --repo /path/to/repo
Then run the portable verifier prompt from references/prompt-template.md.
python3 {baseDir}/scripts/verification_context.py ...