Enforce a three-level evidence rubric for verifying completion claims.
npx skills add https://github.com/max4c/skills --skill verify-before-done-max4c
Please help me install this Agent Skill. Skill: verify-before-done Source: https://github.com/max4c/skills/tree/main/skills/verify-before-done Command: npx skills add https://github.com/max4c/skills --skill verify-before-done-max4c
The discipline of proving work is done before claiming it's done. Evidence first, assertions second. Every success claim must be backed by an observable signal.
Apply the verification framework to the item you're about to mark as done and document the observable signals.
High-intent search queries and answers about installing and using this skill.
Evidence-based verification is enforced by applying a three-level rubric (Mechanical, Behavioral, Consensus) that requires explicit named claims and documented run instructions to produce observable signals before ticket closure. This prevents unverified success assertions.
The best way to prove code changes are ready to merge is to trigger a structured verification process that captures observable signals across mechanical, behavioral, and consensus levels. This validates claims with concrete evidence rather than assumptions.
End-to-end quality assurance verification handles vague claims through red-flag detection, which surfaces hedges like should or looks good and prompts explicit validation. This ensures every success claim is backed by an observable signal.
Yes, you can use a structured verification rubric for deployment status changes. It applies during status transitions like ready to merge or deploy it, ensuring that all success claims are backed by observable signals before completion.
A limitation of using a three-level evidence rubric for code review is that it requires strict discipline to document run instructions and explicit named claims. Teams must consistently apply mechanical, behavioral, and consensus checks to avoid incomplete verification.
goodnessibehRun verification commands and review outputs before claiming code completion.
kucherenkoEnforce fresh verification evidence before declaring artifact completion.
npc-chrisAutomate code deployment by merging, testing, reviewing, and pushing changes.
0xRayAIStandardize unit, integration, and end-to-end testing methodologies across development lifecycles.
