Test a session's or a plan's work the way a QA engineer would: derive cases from the requirement and the diff, run them against the live app with the project's own test tool (playwright-cli as the fallback), fix critical and high findings, retest once, and record learnings in .ac/qa/learnings.md. Use when the user explicitly asks for QA, a test pass, or a browser walk-through of recent work, and when the execute skill reaches Phase 3e with a plan. Not proactive: never start it on your own…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
<!-- ported-from: plugins/ac/skills/qa/SKILL.md sha256:9523ac1c7175e79a8bfff34e91e51c63d8af3ad429c5b5499aa3c92132503c14 -->
# qa
Orchestrates one QA run: scope the change, boot the app, brief a fresh-context `ac/qa-tester`, fix what it finds, retest once, and curate what the run learned. The tester derives and runs the cases; you own the brief, the fixes and the learnings file.
Input: the request text. `--plan <slug>` in it selects a plan run; the rest is the focus text.
## Standing rules
These hold for the whole run, including after a compaction, so they sit before the procedure.
- Never call the `question` tool and never raise a BLOCKER. An environment failure (app will not boot, tool missing, browser missing, credentials absent) ends the run as `could-not-run`, recorded in the report and in `## Known gaps`, and the run still prints its `QA result:` block.
…
The line at the top of this page pins the label git:20261023.9acc08b, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_aijtfbox6ob3pcpy
GET https://markdownregistry.com/api/v1/resolve?ref=anilcancakir/claude-code/qa
GET https://markdownregistry.com/api/v1/blob/7f73dc21cf63230c433a86db6894589f362f6df9cebcbf39dd847c3e9b4aa15d
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
anilcancakir/claude-code · opencode/ac/skills/architecture-md-writer/SKILL.md · Write or audit an ARCHITECTURE.md for agents: boundaries, invariants with verify commands, flows and a change guide…
anilcancakir/claude-code · opencode/ac/skills/auto/SKILL.md · Away mode: carry the run in progress, or a new request, to completion unattended, ending at one verification gate. Use…
anilcancakir/claude-code · opencode/ac/skills/commit/SKILL.md · Split the working-tree changes into atomic commits, preflight and push them; also rebase, squash and trace history. Add…
anilcancakir/claude-code · opencode/ac/skills/coordinate/SKILL.md · Turn a large request into a reviewed roadmap of bundles and drive them through parallel ac/lane worktrees. Use when a…
anilcancakir/claude-code · opencode/ac/skills/design-md-writer/SKILL.md · Write or audit a visual-identity DESIGN.md: design tokens plus rationale in the Google Labs format, for UI agents. Use…
anilcancakir/claude-code · opencode/ac/skills/execute/SKILL.md · Run an approved ac plan to completion, wave by wave, with cost-tiered workers, per-wave verification and a final…
anilcancakir/claude-code · opencode/ac/skills/flow/SKILL.md · Run a medium or large request on the main thread: parallel research, interview, build in slices, oracle review. Use…
anilcancakir/claude-code · opencode/ac/skills/frontend-design/SKILL.md · Build distinctive, accessible web and mobile UI from a committed design direction and token plan. Use when building or…
anilcancakir/claude-code · opencode/ac/skills/github-cli/SKILL.md · Work with GitHub repositories, issues, PRs, releases and Actions runs through the gh CLI instead of web fetches. Use…
anilcancakir/claude-code · opencode/ac/skills/plan/SKILL.md · Plan a change interactively: research in parallel, ask the decisions only you can make, then write a tiered plan…
anilcancakir/claude-code · opencode/ac/skills/product/SKILL.md · Turn an idea into a feasibility-checked PRD and a parallel-ready roadmap through research and an interview. Runs when…
anilcancakir/claude-code · opencode/ac/skills/project-md-writer/SKILL.md · Write or audit a PROJECT.md (what, scope, constraints, decisions) for agents; commands and conventions go in AGENTS.md…
suboss87/fdeops · skills/qa/SKILL.md · Exercise the delivered customer journey using real runtime or browser evidence. Use for functional acceptance testing…
asymmetric-al/core · .agents/skills/qa/SKILL.md · Interactive QA session where user reports bugs or issues conversationally, and the agent files GitHub issues. Explores…
arcee-ai/nac · .agents/skills/qa/SKILL.md · Run scalable, isolated live QA for nac development. The top-level local orchestrator must parse n (default 4), dispatch…
genai-io/san · .san/skills/qa/SKILL.md · Regression test a San feature by name. Looks for a feature doc in docs/reference/ or docs/packages/2-feature/, runs…
rudycity/superagent · .agents/skills/qa/SKILL.md · Interactive QA session where user reports bugs or issues conversationally, and the agent files GitHub issues. Explores…
