qa-tester

Verify active task acceptance criteria and record QA sign-off in docs/ROADMAP.md.

Updated Mar 2, 2026
One-click install
npx skills add https://github.com/supermalang/ai-augmented-coding --skill qa-tester-supermalang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-tester
Source: https://github.com/supermalang/ai-augmented-coding/tree/main/.claude/skills/qa-tester
Command: npx skills add https://github.com/supermalang/ai-augmented-coding --skill qa-tester-supermalang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes guesswork from release validation by checking whether a task truly works from the user's perspective, using the running app, screenshots, and roadmap criteria instead of code review.

Core Features & Use Cases

  • User-facing validation: Confirms acceptance criteria, UAT scenarios, and visual expectations in the browser.
  • Roadmap sign-off: Updates the QA status in docs/ROADMAP.md when the task is ready for human UAT at the PR.
  • Quality gate: Stops the handoff if unit tests, E2E tests, or visual checks are failing.
  • Use case: A feature looks complete in code, but QA still needs to verify the actual page behavior, screenshot quality, and task checklist before the PR can move forward.

Quick Start

Use the qa-tester skill to inspect the active task in docs/ROADMAP.md, verify the app in a browser, and sign off QA only when the acceptance criteria and screenshots are conformant.

Frequently Asked Questions about qa-tester

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify acceptance criteria for a browser-ready task before PR review?

To verify acceptance criteria before PR review, validate the running app visually in the browser, review screenshots, and confirm roadmap status to ensure the task meets user expectations without modifying source code.

Can I perform visual review and UAT without altering source code or tests?

Yes, you can perform UAT and visual review without altering source code, tests, or schema files by validating the running app, test outputs, and roadmap status to record QA sign-off.

What is the best way to record QA sign-off in the roadmap for release readiness?

The best way to record QA sign-off for release readiness is to inspect the active task in docs/ROADMAP.md, verify the app in a browser, and update QA status only when acceptance criteria and screenshots are conformant.

Does the QA testing process stop the handoff if E2E tests or visual checks are failing?

Yes, the QA testing process acts as a quality gate that stops the handoff to human UAT at the PR if unit tests, E2E tests, or visual screenshot checks are failing.

When do I need to run user acceptance testing for tasks awaiting PR review?

You need to run UAT for tasks awaiting PR review when a feature looks complete in code but still requires verifying actual page behavior, screenshot quality, and the task checklist against acceptance criteria.

Are there limitations to checking page behavior strictly from a user perspective?

A limitation of checking page behavior from a user perspective is that it only validates the running app and visual expectations, meaning it cannot replace deep code review or modify source code, tests, and schema files.