Autoqa
Self-QA a repo's running application end-to-end — discover how it runs, build a feature×modality test plan, execute it against a live instance, and produce a witnessed pass/fail report. Use when the user says "autoqa", "QA this repo/branch", "verify every feature works", "release readiness check", "test this like a QA engineer would", or another skill needs an automated QA pass before sign-off.
Install
npx skills add wolverin0/claude-skills --skill autoqagit clone --depth 1 https://github.com/wolverin0/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/skills/autoqa ~/.claude/skills/autoqaPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# autoqa — QA any repo against its own running app You are the QA engineer for this repo. Every verdict is **witnessed** — it points at an artifact (an HTTP response, a page snapshot, a log line, a DB row) that *shows* the result, not merely a file that exists. The full witness contract is in Hard rules below. ## Phase 0 — RESOLVE Establish three facts before anything else: 1. **Target repo** — path or URL the user pointed at (ask only if truly absent). 2. **Target instance** — a running deployment to test against (URL/port), or the instruction to bring one up locally. 3. **Repo config** — look for `AUTOQA.md` at the repo root or under `docs/`. It is the repo's reusable **baseline**, not the complete plan: how to run, how to auth, optional catalog/core checks, and known env caveats. **If found, read it now and skip the generic discovery in Phase 1, but never skip Phase 2's diff discovery.** Missing config means full Phase 1 — and a repo you QA repeatedly earns one: write `AUTOQA.md` from what Phase 1 taught you so later runs can start from that baseline. Done when: repo path, instance URL (or "must boot"), and config-or-none are stated. ## Phase 1 — DISCOVER Read the repo the way a new engineer would, in this order, stopping when the three questions below are answered. Full source-priority list and what each source answers: [references/discovery.md](references/discovery.md).
Details
- Skill name
autoqa- Repository
- wolverin0/claude-skills
- Path
skills/autoqa/SKILL.md- Repo updated
- 17 November 2026
FAQ
What does the Autoqa skill do?
Self-QA a repo's running application end-to-end — discover how it runs, build a feature×modality test plan, execute it against a live instance, and produce a witnessed pass/fail report. Use when the user says "autoqa", "QA this repo/branch", "verify every feature works", "release readiness check", "test this like a QA engineer would", or another skill needs an automated QA pass before sign-off.
How do I install the Autoqa skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add wolverin0/claude-skills --skill autoqa. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Autoqa popular?
It lives in wolverin0/claude-skills, which has 41 GitHub stars and 1 forks.
Related skills
UI UX Pro Max
41wolverin0/claude-skills
UI/UX design intelligence for web and mobile. Includes 50+ styles, 161 color palettes, 57 font pairings, 161 product types, 99 UX guidelines, and 25 chart types across 10 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui, and HTML/CSS). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, and check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, and mobile app. Elements: button, modal, navbar, sidebar, card, table, form, and chart. Styles: glassmorphism,
Audit Blind Spots
41wolverin0/claude-skills
Walk the B1-B19 AI-to-AI blind-spot catalog systematically. Use during the audit pipeline AFTER hard-stops and Tambon hunt and BEFORE the 13 domain audits. Output: PRESENT / NOT PRESENT for each B-class with evidence. Findings flow into the appropriate domains.
Audit Decisions
41wolverin0/claude-skills
Standardize remediation decisions, baseline-policy entries, and legal-review banners for accepted, deferred, or policy-blocked audit findings.
Battle Test
41wolverin0/claude-skills
Run a fail-closed end-to-end project hardening cycle: static audit, exhaustive real-browser validation, semantic screenshot review, multi-role/security/visual-regression probes, isolated remediation, and re-verification. Use when the user asks to battle-test or prove production readiness. Default is the full cycle; --quick runs a clearly weaker smoke/readiness check and can never emit a battle-tested verdict. Main integration requires --push-main; deployment is never automatic. --ux curates only UX/UI and ends with its own verdict (UX SCOPE VERIFIED or UX SCOPE FAILED), never battle-tested.
Audit Domain 11 Demo Vs Prod
41wolverin0/claude-skills
Audit the gap between demo-quality and production-quality — hardcoded test data, dev-only configurations shipped, missing prod hardening. Run as part of /audit Phase E.
Forage Plants
45pjt222/agent-almanac
Identify and safely gather edible and useful wild plants. Covers safety rules and deadly plant recognition, habitat reading, multi-feature identification methodology, the universal edibility test, sustainable harvesting practices, preparation methods, reaction monitoring, and building knowledge with beginner-friendly universal species. Use when supplementing food supply in a wilderness or survival setting, needing medicinal or utility plants, identifying plants around camp for safety, or in long-term scenarios where foraging extends available rations.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.