All authors
Claude Skills by ArtJack
github.com/ArtJack5 skills0 installs3 views
- Verdict Flaky TriageClassify an intermittent test failure with evidence — REAL_DEFECT, STALE_EXPECTATION, BRITTLE_TEST, ENVIRONMENT or FLAKY — and decide quarantine with a mandatory expiry. Use when a test fails one run in five, when CI is "just flaky", or before anyone skips a test.Votes: 0GitHub stars: 2
- Verdict Release RiskRun a measured, skeptical QA pass on a repository and produce a release verdict you can defend — evidence-cited findings, a stated not-tested list, baseline → delta memory. Use before a merge or release, after a feature lands, or for a scheduled QA run. Reports and specifies; never fixes.Votes: 0GitHub stars: 2
- Verdict Root CauseTrace a failure to its root cause with proof, not a story — a four-link chain (symptom, mechanism, origin, class), a counterfactual in an isolated scratch copy, trigger separated from cause, and a diagnosis of where the fix belongs. Use on a failing test, a bug report, or a finding whose cause is disputed.Votes: 0GitHub stars: 2
- Verdict Spec ReviewJudge a specification, issue or PRD for testability before any code exists — inventory the requirements, find the untestable, contradictory, unbounded and silent ones with a verbatim quote each, and rewrite the core as Given/When/Then acceptance criteria. Use when a spec is about to be implemented.Votes: 0GitHub stars: 2
- Verdict Verify FixProve that a fix fixed the defect — re-run the guarding test at the previous commit and at HEAD, re-inject the defect in an isolated scratch copy, and let the harness record fix_verified from measurement, never from a claim. Use after you (the coding agent) fixed a finding and before you call it done.Votes: 0GitHub stars: 2