skills.rest
Jaykaijack
JaykaijackCOMMUNITY
Explore all skills by this author →
GitHub

qa

Identifies and reproduces web app bugs, applies atomic fixes, and verifies results with health scores and ship-readiness summaries.

Updated Mar 15, 2026
Search Tags:#automation#testing#reports#qa#verification#bug-fix
One-click install
npx skills add https://github.com/Jaykaijack/openclaw-backup --skill qa-jaykaijack
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/Jaykaijack/openclaw-backup/tree/main/skills/gstack/qa
Command: npx skills add https://github.com/Jaykaijack/openclaw-backup --skill qa-jaykaijack

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

QA testing and bug-fix orchestration for web apps, with automated verification and evidence.

Core Features & Use Cases

  • Systematic manual-and-automated QA to uncover bugs across browsing flows and forms.
  • Atomic fixes: commit each bug fix separately and re-run verification to confirm outcomes.
  • Generate before/after health scores and a ship-readiness summary to guide release decisions.

Quick Start

Run the QA workflow on your active feature branch or a target URL to begin the test-fix-verify cycle.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I automate QA testing and bug fixing for a web app?▼

Automate QA testing by running a test-fix-verify cycle that identifies bugs, applies atomic commits to fix them, and re-verifies outcomes to confirm the web app is stable.

What is a ship-readiness summary in automated QA reports?▼

A ship-readiness summary is a release decision guide generated after QA testing that calculates before and after health scores based on bug verification outcomes.

Do I need a clean Git working tree to run automated verification?▼

Yes, you need a clean Git working tree before running automated verification, because the QA workflow applies atomic commits for each bug fix separately.

Can I run QA testing on a target URL instead of a local feature branch?▼

Yes, you can run the QA workflow on a target URL or an active feature branch to initiate the test-fix-verify cycle and identify bugs across browsing flows.

What is the best way to track bug fixes during web app QA testing?▼

Track bug fixes by committing each fix as a separate atomic commit, re-running verification, and recording test outcomes in detailed QA reports for audit purposes.

When should I not use automated QA testing workflows?▼

Avoid automated QA testing workflows when your Git working tree is unclean, as the process requires committing atomic bug fixes and maintaining detailed reports for audit.

Related Skills

Explore More Software Engineering Skills→
Knuckles-TeamKnuckles-Team
2

git-status-reset

Inspect Git working directory state and reset or clean uncommitted changes.

Official
Intermediate
giljaegiljae
1

gstack-canary

Monitor live web apps for console errors, performance, and visual regressions post-deploy.

Community
Intermediate
ligianehualigianehua

qa-only

Test web applications and generate QA reports with health scores and screenshots.

Community
Intermediate
wojonswojons
4

testing-unit

Execute unit tests across programming languages and testing frameworks.

Community
Basic