The tight edit-verify cycle DURING implementation — after every meaningful change, run the fastest sufficient check before making the next change; never accumulate a batch of unverified edits. Trigger this continuously while writing or modifying code: after each function implemented, each bug-fix edit, each config change, each refactoring step. Do NOT confuse with verification-and-review, which is the one-time exit gate before claiming "done" — this skill is the per-edit rhythm that makes that final gate boring. Do not trigger for pure prose/documentation edits with nothing executable to check.
$npx -y skills add unpaidattention/fable5-methodology --skill verification-loopInstalls into the current project.
Run `npx skills use "https://github.com/unpaidattention/fable5-methodology" --skill "unpaidattention/fable5-methodology/verification-loop"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/unpaidattention/fable5-methodology" that are relevant to the current task. Run `npx skills add "https://github.com/unpaidattention/fable5-methodology"` and select the relevant skills, then follow their instructions.