qa

Tests web applications for bugs and fixes them with atomic commits.

Updated May 15, 2026
One-click install
npx skills add https://github.com/tgmarinho/canetaco --skill qa-tgmarinho
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/tgmarinho/canetaco/tree/main/.claude/skills/qa
Command: npx skills add https://github.com/tgmarinho/canetaco --skill qa-tgmarinho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually testing a web application for bugs is slow and easy to skip, and found issues often go unfixed or untracked. This Skill runs systematic QA testing on a site, then iteratively fixes each bug in the source code, committing every fix atomically and re-verifying until the app is ready to ship. ## Core Features & Use Cases - Tiered QA Depth: Choose Quick (critical/high severity only), Standard (adds medium), or Exhaustive (adds cosmetic issues) depending on how thorough the pass should be. - Test-and-Fix Loop: Each bug found is fixed in source code, committed atomically, and re-verified rather than just reported. - Evidence-Based Reporting: Produces before/after health scores, fix evidence, and a ship-readiness summary so you can see exactly what changed. - Use Case: After finishing a new feature, ask the agent to QA the site. It crawls the app, finds a broken form submission and a console error, fixes both in separate commits, and reports the app is ready to deploy. ## Quick Start Ask the agent to QA test this site and fix whatever bugs it finds.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I automatically test my website for bugs?▼

Invoke the qa skill against your running site and it systematically exercises the application, catalogs bugs by severity, fixes each one in the source code, and commits every fix atomically with re-verification.

How to test and fix bugs in one workflow?▼

The qa skill combines both phases: it runs a QA pass first, then enters a fix loop where each confirmed bug is patched in code, committed separately, and re-tested until the issue is resolved.

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

Quick covers only critical and high severity bugs, Standard adds medium severity issues, and Exhaustive additionally includes cosmetic problems. Pick the tier based on how close you are to shipping.

Can I get a QA report without changing any code?▼

Yes, use the report-only mode via /qa-only instead of /qa. It runs the same testing pass and produces findings and health scores without modifying source files or creating commits.

What output does the QA testing skill produce?▼

It produces before/after health scores, evidence for each fix applied, and a ship-readiness summary. Each fix lands as its own atomic commit so the change history maps directly to the bugs found.