skills.rest
jeisenback
jeisenbackCOMMUNITY
Explore all skills by this author →
GitHub

qa

Automate QA testing and iterative bug fixing for web applications.

Updated Mar 22, 2026
Search Tags:#automation#testing#qa#verification#bug-fix#workload
One-click install
npx skills add https://github.com/jeisenback/original-curse-killer --skill qa-jeisenback
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/jeisenback/original-curse-killer/tree/main/.claude/skills/qa
Command: npx skills add https://github.com/jeisenback/original-curse-killer --skill qa-jeisenback

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematically QA test a web application and fix bugs found. Runs QA testing, then iteratively fixes bugs in source code, committing each fix atomically and re-verifying. Use when asked to "qa", "QA", "test this site", "find bugs", "test and fix", or "fix what's broken".

Core Features & Use Cases

  • Proactively suggest improvements when you describe a feature as ready for testing or ask "does this work?"
  • Three tiers: Quick (critical/high), Standard (+ medium), Exhaustive (+ cosmetic). Produces before/after health scores, fix evidence, and a ship-readiness summary.
  • Integrates with a disciplined commit-based workflow to ensure traceability and reproducibility of QA fixes.

Quick Start

Run the QA workflow against your project to start automated testing, bug fixing, and 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 systematically tests a web application, iteratively fixes bugs in source code, commits each fix atomically, and re-verifies the changes until the site is stable.

What is the difference between Quick, Standard, and Exhaustive QA testing tiers?▼

Quick QA testing targets critical and high-severity bugs, Standard adds medium-severity issues, and Exhaustive includes cosmetic defects to provide comprehensive coverage and a ship-readiness summary.

How does commit-based workflow integration improve bug fixing?▼

Commit-based workflow integration ensures traceability and reproducibility by committing each bug fix atomically, allowing developers to track specific changes and verify fixes individually.

What evidence does automated QA testing capture during the verification process?▼

Automated QA testing captures evidence including screenshots and logs, producing before and after health scores to demonstrate the effectiveness of applied bug fixes.

When should I run an exhaustive QA test instead of a quick scan?▼

Run an exhaustive QA test when preparing for final release to catch cosmetic defects alongside critical and medium issues, whereas a quick scan suits rapid checks for critical and high-severity bugs.

Can I use automated QA to fix bugs without manually writing test cases?▼

Yes, automated QA proactively suggests improvements and runs systematic testing when you describe a feature as ready, automatically finding and fixing bugs without requiring manually written test cases.

Related Skills

Explore More Software Engineering Skills→
rajyeole6rajyeole6

agency-jira-workflow-steward

Validate Git branches and commits against Jira-linked workflow policies.

Community
Advanced
soyasissoyasis

qa

Identify and validate web application bugs with tiered QA testing.

Community
Advanced
rnbenrnben

dogfood

Automate exploratory QA testing of web applications with screenshots and structured reports.

Community
Advanced
SakshamKandelSakshamKandel

qa

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

Community
Advanced