qa

Automates web app testing, bug fixing, and git commit creation.

Updated Jul 3, 2025
One-click install
npx skills add https://github.com/andrew-t-james/dotfiles --skill qa-andrew-t-james
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/andrew-t-james/dotfiles/tree/main/dot_claude/skills/qa
Command: npx skills add https://github.com/andrew-t-james/dotfiles --skill qa-andrew-t-james

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA teams spend hours manually testing and patching web apps. This Skill automates the test-and-fix loop, surfacing bugs quickly and guiding atomic commits to verify fixes.

Core Features & Use Cases

  • End-to-end QA workflow: set up tests, run them against a web application, log failures, and create patches that fix defects.
  • Atomic verification: ensure each bug fix is committed in its own change with traceable history and re-verification.
  • Use cases: feature development regression, smoke testing after deployments, and quick sanity checks in sprint cycles.

Quick Start

Run the QA workflow against your target URL to begin the test, fix, and 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 web applications?

Automating QA testing for web applications involves running a workflow that executes tests, detects failures, generates patches, and commits atomic fixes to Git for traceable verification.

How does automated regression testing handle bug fixes and verification?

Automated regression testing locates defects during execution, creates a patch to fix the bug, commits the change atomically, and re-verifies the web app to ensure the fix is traceable and successful.

Can I use automated QA workflows for post-release sanity checks on web apps?

Yes, you can use automated QA workflows for post-release sanity checks. The process runs tests against your target web app, logs failures, and creates patches to quickly verify stability.

What is the best way to maintain traceable history when fixing web app bugs?

The best way to maintain traceable bug fix history is to enforce atomic commits. This ensures each defect patch is committed individually and re-verified before integration.

Does automated QA testing require Git integration for fixing web application defects?

Git integration is used to provide traceable fixes during automated QA testing. It logs test results and commits atomic patches, ensuring each web app defect fix has a verifiable history.