qa

Automate end-to-end QA testing and atomic bug fixes for web applications.

4|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/lendtrain/complete-pipeline --skill qa-lendtrain
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/lendtrain/complete-pipeline/tree/main/skills/qa
Command: npx skills add https://github.com/lendtrain/complete-pipeline --skill qa-lendtrain

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

QA teams spend significant time manually testing web applications, reproducing issues, and tracking fixes. This Skill automates the QA workflow, runs tests, and guides atomic bug fixes with verifiable evidence and health scores.

Core Features & Use Cases

  • Automated end-to-end QA testing across common user flows, with test orchestration and result validation.
  • Iterative bug fixing with atomic commits and re-verification to ensure stable progress.
  • Ship-readiness reporting that includes before/after health scores, evidence, and a clear go/no-go summary.
  • Tiered testing levels: Quick (critical/high), Standard (plus medium), Exhaustive (plus cosmetic), to fit time and risk budgets.

Quick Start

Provide the target URL and run the /qa command to begin automated testing and fixes.

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 QA testing for web apps?

Automated end-to-end QA testing for web apps orchestrates browser automation across common user flows, validates results, and generates before/after health scores with verifiable evidence to confirm ship-readiness.

Can I automate bug fixes and re-verify them during development?

Yes, automated bug fixes apply atomic commits and iteratively re-verify changes to ensure stable progress. This generates verifiable evidence confirming the fix resolved the issue across test environments.

What do I need to set up automated QA testing and ship-readiness reporting?

Automated QA testing and ship-readiness reporting require a test harness, browser automation, and logging. These produce repeatable tests and verifiable fixes before generating the go/no-go summary.

Does automated QA testing support different test levels based on risk?

Yes, automated QA testing supports tiered testing levels: Quick for critical and high severity, Standard for medium, and Exhaustive for cosmetic issues. This fits testing within specific time and risk budgets.

What is the best way to verify feature-branch changes across environments in CI?

Verifying feature-branch changes across environments in CI applies automated QA testing during development to run repeatable tests, generate health scores, and produce a ship-readiness summary with evidence.

Why do I need a test harness and logging for automated bug fixes?

Automated bug fixes require a test harness and logging to produce repeatable tests and verifiable fixes. Without these, the system cannot generate the before/after health scores and evidence needed for ship-readiness.