verify-app
When to use
Use this skill whenever:
- •Code changed and you need to confirm it is correct.
- •Tests or lint are failing and you need to debug/fix them.
- •You are about to claim "done" and need a verification transcript.
Rules
- •If the task uses staged delivery, explicitly note whether the verified stage is complete in
20_verification.md(and add a brief note to10_impl_notes.mdwhen requested). - •Read
AGENTS.mdCommands for canonical checks. - •Read the task brief and implementation notes in the active task folder.
- •If
.venvexists, activate it or use.venv\\Scripts\\python.exefor all checks. - •If commands are missing, follow the sanity run protocol in
AGENTS.mdand note gaps. - •Record a full transcript in
tasks/<date>_<slug>/20_verification.md.
Method
- •Read
tasks/<date>_<slug>/00_task_brief.mdand10_impl_notes.md. - •Run the smallest relevant checks first, then full checks if configured.
- •Fix failures minimally and re-run failed checks.
- •Write the exact commands and results to
20_verification.md.
Output requirements
- •
20_verification.mdincludes environment, commands, results, and any rerun transcript.