skills.rest
CaltexBevo
CaltexBevoCOMMUNITY
Explore all skills by this author →
GitHub

qa

Test web applications, fix bugs via atomic commits, and re-verify.

Updated Feb 5, 2026
Search Tags:#commit#qa#evidence#regression#web-testing#bug-fix
One-click install
npx skills add https://github.com/CaltexBevo/ihe-pulse --skill qa-caltexbevo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/CaltexBevo/ihe-pulse/tree/main/.claude/skills/gstack.bak/qa
Command: npx skills add https://github.com/CaltexBevo/ihe-pulse --skill qa-caltexbevo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

QA testing of web applications is challenging and error-prone without a structured workflow. This Skill guides teams to systematically test, reproduce bugs, fix them atomically, and re-verify to ensure quality before shipping.

Core Features & Use Cases

  • End-to-end QA cycles: supports Quick, Standard, and Exhaustive tiers to cover critical flows, regression risks, and cosmetic issues.
  • Fix-before-ship discipline: enforces atomic commits, before/after health scores, and ship-readiness summaries to document impact.
  • Evidence-driven verification: generates test evidence and regression checks to validate fixes across the codebase.

Quick Start

Run a full QA pass on the current site, report issues, implement fixes, and re-verify.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I systematically test a web application, identify bugs, and fix them?▼

You can systematically test a web application by running structured QA cycles that test critical flows, reproduce bugs atomically, implement fixes, and re-verify to ensure quality before shipping. This process generates before/after health scores and ship-readiness summaries.

What is the best way to enforce fix-before-ship discipline during regression testing?▼

Fix-before-ship discipline is enforced through atomic commits, before/after health scoring, and ship-readiness summaries. Evidence-driven verification generates regression checks to validate fixes across the codebase, ensuring no regressions are shipped.

Can I run a quick QA pass on my site to check critical flows without a full regression suite?▼

Yes, you can run a Quick QA tier to cover critical flows rapidly. The tool supports Quick, Standard, and Exhaustive tiers, allowing you to scale testing from basic checks to comprehensive regression risks and cosmetic issues.

How does evidence-driven verification work when fixing bugs in a web application?▼

Evidence-driven verification works by generating test evidence and regression checks to validate bug fixes across the codebase. It uses atomic commits to isolate changes and produces before/after health scores to document the impact of each fix.

Does this QA workflow support generating ship-readiness summaries for web testing?▼

Yes, the QA workflow supports generating ship-readiness summaries for web testing. It calculates before/after health scores and documents evidence to validate that fixes are complete and the application is ready for deployment.

Why should I use atomic commits when fixing bugs during web testing?▼

Atomic commits isolate each bug fix to ensure evidence-driven verification and accurate re-verification. This fix-before-ship discipline tracks before/after health scores and generates ship-readiness summaries without mixing unrelated changes.

Related Skills

Explore More Software Engineering Skills→
nocnocgroupnocnocgroup

qa

Automate structured QA testing of web applications with standardized reports.

Official
Advanced
henriquemeireles7henriquemeireles7

qa

Test web applications, fix bugs, and generate health scores with tiered QA.

Community
Advanced
Kevin-Liu-01Kevin-Liu-01
16

qa

Automate real-browser QA testing to discover bugs and generate regression tests.

Community
Advanced
pistosminpistosmin

qa

Identify and fix web application bugs with structured QA testing and atomic commits.

Community
Advanced