← ClaudeAtlas

ai-agents-validation-and-qalisted

What counts as evidence in ai-agents and how to produce it. Covers the TESTING-RIGOR pos+neg+edge bar, test layout and collection reality, coverage proof commands, runtime-contract tests with negative controls, and ADR-034 QA skip semantics at session end. Use when you say `what counts as evidence`, `how do I test this change`, `run skill tests`, `can I skip QA`. Do NOT use for CI failure triage (use `ai-agents-debugging-playbook`) or measurement tooling (use `ai-agents-diagnostics-toolkit`).
rjmurillo/ai-agents · ★ 38 · AI & Automation · score 77
Install: claude install-skill rjmurillo/ai-agents
# ai-agents Validation and QA <!-- vendor-portability: contributor-facing knowledge pack for the rjmurillo/ai-agents repo itself; intentionally references upstream paths (.agents/, .claude/, scripts/, build/) because its audience is repo contributors, not plugin consumers (issue #2050) --> This repo runs verification-based governance: a claim is true when a gate, test, or command output says it is, not when an agent asserts it. This skill defines the evidence bar for code changes, where tests live and how they are collected, the anti-pattern canon (each entry paid for by a real incident), and the QA gate semantics at session end. Audience: a zero-context contributor (human or model) about to write, run, or skip tests in this repository. ## Triggers - `what counts as evidence` - `how do I test this change` - `run skill tests` - `can I skip QA` ## Scope Boundaries | You want | Use instead | |----------|-------------| | Triage a red CI check or a blocked push | `ai-agents-debugging-playbook` | | Measure drift, budgets, telemetry, coverage trends | `ai-agents-diagnostics-toolkit` | | Probe an external tool's runtime behavior empirically | `ai-agents-empirical-probe-toolkit` | | Understand which gates a change class triggers | `ai-agents-change-control` | | Session-end mechanics beyond the QA row | `session-end` skill | ## Process ### Phase 1: Internalize the evidence bar `.agents/governance/TESTING-RIGOR.md` is BLOCKING for code changes (its own Status line, TESTING-RIGO