qa
QA skill uses real browser automation to test websites end-to-end, capturing visual evidence and validating user flows. It audits pages systematically, scores site health across console errors and interactivity, then fixes issues atomically with commit-per-fix discipline.
QA skill tests websites with real browser automation to find bugs, broken links, and visual issues.
AI-generated summary based on this skill's SKILL.md
Install
blueberrycongee/termcanvas/qa · repository language: TypeScript
git clone https://github.com/blueberrycongee/termcanvas
cp -r termcanvas/skills/skills/qa ~/.claude/skills/qanpx skillfed install blueberrycongee/termcanvas/qaFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
What can QA test this website for bugs?
QA uses real browser automation to systematically test websites for bugs, broken links, and visual issues. It validates end-to-end user flows like signup, login, and checkout, captures screenshots and console errors as evidence, and generates a health score report across console health, link integrity, interactivity, and layout quality.
How does QA check for visual bugs on my page?
QA captures screenshots during automated testing runs and logs visual anomalies alongside console errors. It audits pages for layout problems, broken UI elements, and rendering issues, then documents findings with visual evidence to help you understand exactly what went wrong and where.
Can QA verify user flows like signup and checkout?
Yes. QA automates real user flows end-to-end—signup, login, checkout, and custom workflows—using browser automation. It validates that each step completes successfully, captures interactions and errors, and reports whether critical paths work as expected after deployment or code changes.
Does QA find broken links and console errors?
QA systematically crawls your site to find broken links and monitors the browser console for errors and warnings. It compiles these findings into a health score report that shows console health, link status, interactivity success, and layout integrity across your entire page or flow.
How does QA validate UI changes after deploy?
QA uses browser automation to verify UI changes work as intended after deployment. It runs automated tests on your live site, captures visual evidence of the updated interface, checks that interactions still function, and confirms the deploy looks good before you declare it production-ready.
What does QA's health score report include?
QA's health score aggregates findings across four dimensions: console errors and warnings, link validity, user interaction success, and layout correctness. The report gives you a single score plus detailed breakdowns so you can prioritize fixes and track improvement over time.
SKILL.md
rendered from the published skill — quoted content, verbatim
QA
Browser-based QA testing with the browse CLI. Test real user flows, capture
visual evidence, and fix issues with atomic commits.
Phase 0: Setup
- Verify browse is available:
browse status - If not found, report error — browse binary must be installed
- Get the target URL from the task description or ask the user
Phase 1: Orient
- Navigate to the target:
browse goto <url> - Take a baseline snapshot:
browse snapshot -i - Check console for errors:
browse console - Extract navigation links:
browse links - Build a site map of pages to test (limit to 10 most important pages)
Phase 2: Page-by-Page Audit
For each page in the site map:
- Navigate:
browse goto <page-url> - Snapshot interactive elements:
browse snapshot -i - Check console for errors:
browse console - Screenshot for evidence:
browse screenshot <page-name>.png - Note issues found: broken links, console
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 1 file
skills/skills/qa/SKILL.md