skills.rest
steadyfall
steadyfallCOMMUNITY
Explore all skills by this author →
Website𝕏@steadyfall04GitHub

qa

Run QA testing and bug-fix workflows for web applications with atomic commits.

Updated Mar 28, 2026
Search Tags:#automation#testing#commit#qa#verification#web#bug-fix
One-click install
npx skills add https://github.com/steadyfall/fspeek --skill qa-steadyfall
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/steadyfall/fspeek/tree/main/.claude/skills/gstack/qa
Command: npx skills add https://github.com/steadyfall/fspeek --skill qa-steadyfall

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematically QA test a web application and fix bugs, then iteratively fix bugs in source code, committing each fix atomically and re-verifying. The workflow ensures regressions are caught early and fixes are traceable.

Core Features & Use Cases

  • Structured QA workflows across Quick, Standard, and Exhaustive tiers.
  • Evidence collection, bug triage, and re-verification to close feedback loops.
  • Proactive suggestions for next QA or fixes when guidance is requested.

Quick Start

Run a QA session on your web app and follow through with atomic commits and re-verification.

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 application?▼

Automated QA testing for web applications works through structured workflows that identify, triage, fix, and re-verify defects. It commits each bug-fix atomically to catch regressions early and ensure traceability across Quick, Standard, and Exhaustive testing tiers.

What is the best way to catch regressions when fixing bugs in source code?▼

The best way to catch regressions during bug-fix workflows is to commit fixes atomically and re-verify defects iteratively. This structured QA approach closes the feedback loop by collecting evidence and re-testing after each source code change.

Does structured QA testing support different levels of verification depth?▼

Structured QA testing supports different verification depths through Quick, Standard, and Exhaustive tiers. These tiers scale the bug triage and re-verification process, allowing you to apply the appropriate level of testing based on your web application needs.

How do I commit atomic fixes while re-verifying web application bugs?▼

Commit atomic fixes by applying source code changes for a single defect, then running re-verification to confirm the bug is resolved. This QA workflow uses Bash and editing tools to automate tests, ensuring each commit represents a traceable, verified bug-fix.

Can I use Bash and WebSearch to automate tests and collect evidence during QA?▼

You can use Bash, WebSearch, and file editing tools to automate tests and collect structured evidence during QA. These dependencies enable the workflow to run verification scripts, search for solutions, and communicate triage results effectively.

When should I use the Exhaustive tier over the Quick tier for bug-fix verification?▼

Use the Exhaustive tier over the Quick tier when you need comprehensive defect identification and deep re-verification across your web application. The Exhaustive tier provides maximum coverage for bug triage, while the Quick tier offers rapid verification for isolated fixes.

Related Skills

Explore More Software Engineering Skills→
al-steval-stev

atlassian-setup

Configure Atlassian API credentials for Jira and Confluence access.

Community
Intermediate
SakshamKandelSakshamKandel

qa

QA test web applications, reproduce bugs, and verify fixes iteratively.

Community
Advanced
puwenjunluck-pixelpuwenjunluck-pixel

fix

Automate bug fixing with root cause analysis and regression testing.

Community
Advanced
yocxy2yocxy2

qa-only

Test web applications and generate structured bug reports with health scores.

Community
Intermediate