agentic-verification-disciplinelisted

Build trustworthy evidence for agent-generated changes and make required verification enforceable locally and in GitHub. Use when converting accepted findings into fail-before-fix regression tests; defining or weakening numeric gates and coverage floors; recording red/green evidence in a PR; creating or selecting a repository-owned GitHub Actions required check and its check source; verifying ruleset enforcement; preventing unexpected skips, enforcing a skip budget, or pinning a smoke inventory; testing stable documentation promises; synchronizing tool ignore lists; deciding where a regression test belongs; or diagnosing a local-versus-CI difference where CI enforces a gate the local run does not. Do not use for ordinary CI log debugging that changes no verification contract, for designing a test plan or test strategy that carries no gate or enforcement change, or for deciding product scope and finding disposition.
gidde032/agentic-workflow · ★ 0 · AI & Automation · score 63

Install: claude install-skill gidde032/agentic-workflow

# Agentic Verification Discipline How agent-built code earns trust, one finding at a time. **Numeric gates** — setting floors, ratcheting, and handling a missed prediction: `references/numeric-gates.md`. **GitHub Actions and rulesets** — workflow requirements, required-check activation order, and configured-versus-enforced reporting: `references/github-actions-contract.md`. **Worked examples and provenance** — the evidence behind every rule here: `examples.md`. --- ## 1. The Core Contract > **No accepted defect disappears without durable evidence or a durable > disposition.** Every accepted finding receives one terminal disposition: - **Repair now** — reproduce the failure, fix it, add the smallest faithful regression test, record red/green evidence. - **Defer** — create or link an Issue containing the finding, evidence, impact, and acceptance criteria. - **Reject** — record evidence showing the finding is incorrect or outside the accepted contract. - **Duplicate** — link the existing Issue. - **Outside contract** — name the governing boundary and why no action is warranted. "Remember later," a handoff bullet, or an unlinked review report is not a terminal disposition. For a repaired finding: 1. Observe the failure before applying the fix when safely possible. 2. Add the smallest test that faithfully reproduces the defect. 3. Confirm that test fails for the defect mechanism. 4. Apply the fix. 5. Confirm the targeted test passes. 6. Run the broader required g