Run end-to-end QA tests on web applications and document fixes.
npx skills add https://github.com/sanskarbasnet/fstack --skill qa-sanskarbasnet
Please help me install this Agent Skill. Skill: qa Source: https://github.com/sanskarbasnet/fstack/tree/main/qa Command: npx skills add https://github.com/sanskarbasnet/fstack --skill qa-sanskarbasnet
QA testing often requires repeated manual cycles to identify defects, verify fixes, and ensure ship-readiness. This Skill automates end-to-end QA workflows within Claude Code, coordinating testing, bug fixes, and evidence generation so teams can iterate quickly and confidently.
Run the QA skill on your web project to start automated testing, bug isolation, and verification.
High-intent search queries and answers about installing and using this skill.
End-to-end QA testing for a web application executes automated workflows to capture failures, validate fixes, and generate ship-readiness summaries. It coordinates tiered testing levels—Quick, Standard, and Exhaustive—to isolate defects and verify corrections.
A ship-readiness assessment evaluates release readiness by producing before and after health scores alongside a concise QA summary. It applies to development cycles requiring QA coverage, ensuring applications meet quality standards before deployment.
Yes, you can execute QA workflows in a report-only mode to identify defects and document issues without applying automatic fixes. This mode supports telemetry collection and evidence generation while leaving code modifications entirely manual.
Automating bug fixes during quality assurance testing requires a workflow that identifies defects, documents corrections, and validates the applied fixes. This Skill runs end-to-end tests, isolates failures, and verifies resolutions to ensure web app stability.
Yes, the QA testing approach supports tiered testing levels including Quick, Standard, and Exhaustive coverage. This allows teams to select the appropriate depth of automated testing based on specific development cycle requirements and ship-readiness goals.
Automated end-to-end QA testing may be unnecessary for trivial changes or when rapid manual verification suffices. It is best applied to development cycles requiring comprehensive QA coverage, bug hunts, and formal ship-readiness assessments.
solace-illRun automated test suites and produce PASS/FAIL reports for QA hand-off.
cattboyTest web applications, fix bugs iteratively, and commit changes atomically.
zangxin75Create test strategies and write unit, integration, and end-to-end tests.
tyhuffman7Execute QA tests on web apps and log failures with health scores.
