qa

Test web application user flows and generate QA reports with health scores.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/shaneholloman/ship --skill qa-shaneholloman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/shaneholloman/ship/tree/main/qa
Command: npx skills add https://github.com/shaneholloman/ship --skill qa-shaneholloman

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Systematically QA test a web application to identify bugs, verify fixes, and produce actionable evidence. It guides engineers through a structured workflow from setup to wrap-up, ensuring repeatable, atomic fixes and traceable reports.

Core Features & Use Cases

  • Structured QA workflow: prep, explore, document, and verify, with tiered testing scopes.
  • Automated health scoring and evidence collection to support ship-readiness decisions.
  • Diff-aware and full-scan modes to adapt testing to feature branches or production URLs.
  • Generate QA reports with before/after evidence and traceable commits.

Quick Start

Run /qa on your target URL to start a complete QA cycle.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I automate end-to-end testing to find bugs in web applications?

Run a complete QA cycle on your target URL to automate end-to-end testing for web applications, identifying bugs and verifying fixes while generating actionable evidence with ship-readiness scores.

What is the best way to structure QA reports for user flow testing?

Structure QA reports by capturing before and after evidence, applying tiered testing scopes, and generating health scores to support ship-readiness decisions for user flow testing.

Can I run diff-aware testing on feature branches instead of full production scans?

Yes, you can run diff-aware testing on feature branches instead of full production scans, adapting the scope to target only changed areas for faster bug verification.

How do I apply tiered testing scopes to determine which bugs to fix first?

Apply tiered testing scopes like Quick, Standard, and Exhaustive to determine which bugs to fix first by evaluating issue severity and verifying fixes thoroughly based on scope depth.

Does structured quality assurance testing support traceable commits for atomic fixes?

Structured quality assurance testing supports traceable commits by guiding engineers through a repeatable workflow that ensures atomic fixes and generates reports linking evidence to specific commits.