qa

Test web applications end-to-end, record issues with evidence, and verify fixes via atomic commits.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/amanik/sailor-score-debug --skill qa-amanik
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/amanik/sailor-score-debug/tree/main/.claude/skills/gstack/qa
Command: npx skills add https://github.com/amanik/sailor-score-debug --skill qa-amanik

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA engineers spend excessive time manually testing and reproducing bugs across web applications. This skill provides a structured, repeatable approach to test user flows, capture evidence, and verify fixes through atomic commits.

Core Features & Use Cases

  • Systematic end-to-end testing across pages and interactions, with evidence capture.
  • Iterative bug fixing with atomic commits and re-verification to confirm ship-readiness.
  • Health-score style reporting and a ship-readiness summary for stakeholders.

Quick Start

Run /qa against your app URL to start a repeatable QA cycle that tests, fixes, and re-validates changes.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I automate end-to-end testing and bug fixing for a web application?

End-to-end testing and bug fixing can be automated by running a QA workflow that systematically tests user flows, records issues with evidence, and verifies fixes through atomic commits. This provides reproducible test scenarios and ship-readiness confirmation.

What is the best way to capture bug evidence during automated QA testing?

The best way to capture bug evidence during automated QA testing is using a workflow that records issues systematically during end-to-end web app testing. It generates health-score style reporting and before/after evidence for stakeholders.

How do you verify code fixes without re-testing the entire web application?

You verify code fixes without re-testing everything by applying atomic commits to bug fixes and re-running reproducible test scenarios. This iterative re-verification confirms that specific changes are ship-ready without redundant manual checks.

Can I run automated QA cycles across multiple web pages and user flows?

Yes, you can run automated QA cycles across multiple web pages and user flows. The workflow applies to web apps with configurable scopes and environments, enabling systematic testing of diverse interactions and capturing evidence for each scenario.

Does automated QA testing support configurable environments and reporting?

Automated QA testing supports configurable scopes, environments, and reporting. It generates health scores and a ship-readiness summary, providing structured evidence and validation results for stakeholders after each testing cycle.

Why should I use atomic commits when fixing bugs in an automated testing workflow?

Atomic commits isolate individual bug fixes during an automated testing workflow, enabling precise re-verification of each change. This approach maintains reproducible test scenarios and ensures ship-readiness by verifying fixes against captured evidence.