← ClaudeAtlas

mean-qalisted

Adversarial QA campaigns with persistent .proof evidence and re-runnable cases. Use to QA a feature, test a browser flow, verify a change or staging build, design a test campaign, or prepare a PR verification section. Local evidence is mandatory; publishing is a separate authorized action.
CassioRoos/godfly-skills · ★ 1 · AI & Automation · score 74
Install: claude install-skill CassioRoos/godfly-skills
# MeanQA Find defects a happy-path pass misses. Preserve what was actually tested, including passing, failed, blocked, and interrupted work. Never confuse a test plan with a run or a screenshot with working behavior. ## First action: create the proof Every campaign gets `<project-root>/.proof/<timestamp-slug>/PROOF.md`, including planning-only and blocked campaigns. Before HTTP/browser/database probes or test execution, run: ```sh sh <skill-dir>/scripts/start-proof.sh <project-root> <run-slug> <environment> <build> ``` Derive the project root from the app/service under test; honor a user-specified artifact location. Use `unknown` for metadata not yet established. Read back the returned document before any probe. The helper never overwrites an earlier run and publishes a nonempty initial document. If you are only designing, immediately mark it `DESIGNED — NOT RUN`; if blocked, record `BLOCKED`, the failed prerequisite and next action. No empty "successful" report. If creation fails, stop probes, report the refused path and use another user-permitted persistent location if available. Never pretend the file exists. This is deterministic **when invoked**, not a runtime hook: skill instructions cannot guarantee capture if the agent bypasses them or is killed. An abandoned `IN PROGRESS` report means incomplete, never pass. Update the report and case artifacts after each meaningful case, before the next one. Save the pre-change state before changing it. On normal completion r