Enforces fresh execution of verification commands before any completion claim.
npx skills add https://github.com/FerEscobarDev/Specture --skill verify-ferescobardev
Please help me install this Agent Skill. Skill: verify Source: https://github.com/FerEscobarDev/Specture/tree/main/skills/verify Command: npx skills add https://github.com/FerEscobarDev/Specture --skill verify-ferescobardev
High-intent search queries and answers about installing and using this skill.
Identify the command that proves the claim, run it fresh in the current turn, read the full output and exit code, then confirm the output actually supports the claim. Only state completion after this sequence, citing the evidence.
Sufficient evidence is running the test command now and seeing zero failures in the current output. Previous runs, confidence, partial checks, or another agent's success report do not qualify as evidence.
No, a linter is not the compiler. Linting only checks style and static issues, so you must run the actual build command and confirm exit code 0 before claiming the build succeeds.
If the verification command fails due to environment issues unrelated to the work, route to debugging instead. If verification is impossible, such as hardware-specific features, state explicitly what can and cannot be verified rather than claiming completion.
Agents often rationalize with excuses like "should work now" or trust prior runs and other agents' reports. The verification gate counters this by requiring fresh command execution and output reading before any success claim.
mol4Implement user intent into code changes, specs, and review artifacts.
deerawanArchive completed milestones by compiling roadmap and requirements into versioned git artifacts.
ccakmak60Enforce a Red-Green-Refactor test-first workflow for software changes.
tsuji-tomonoriAutomate accessibility testing in CI/CD pipelines with quality gates.
