qa

Run tiered QA tests on web applications and document fixed bugs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA teams spend excessive time manually testing web applications, risking regressions and delaying releases.

Core Features & Use Cases

  • Phase-based testing workflow including Baseline, Authenticate, Exploration, Issue Documentation, Fix, Report, and Ship Readiness.
  • Tiered testing options (Quick, Standard, Exhaustive) to match risk tolerance and timelines.
  • Outputs include before/after health scores, evidence of fixes, regression tests, and a ship-readiness summary.

Quick Start

Run the QA skill on the target feature to generate a test plan, log issues, and verify fixes.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I automate web application QA testing and bug fixing in one workflow?

This Skill automates web application QA testing and bug fixing through a structured workflow covering baseline checks, authentication, exploration, issue documentation, fixes, and ship-readiness reporting to ensure deployment confidence.

What is the best way to prevent regressions when fixing bugs before a release?

Preventing regressions when fixing bugs requires enforcing mandatory regression tests after each fix, generating before and after health scores to verify that the web application remains stable and ship-ready.

Can I adjust the depth of regression testing based on my project timeline?

Yes, you can adjust regression testing depth based on your project timeline and risk tolerance by selecting tiered testing options: Quick, Standard, or Exhaustive, which scale the web application QA workflow accordingly.

How do I generate a ship-readiness summary for a web application feature?

To generate a ship-readiness summary, execute the QA workflow across defined phases including issue documentation and fixes, which produces before and after health scores, fix evidence, and a final deployment recommendation.

Does the QA workflow require external testing frameworks to run?

No external testing frameworks are required to run the QA workflow, as it operates independently with no dependencies to systematically test web applications, document issues, and apply fixes.