qa-engineer

Tests running applications end-to-end and fixes bugs with atomic commits and automated regression coverage.

2|1|Updated Jul 25, 2026
One-click install
npx skills add https://github.com/CODE-SAURABH/OpenSkills --skill qa-engineer-code-saurabh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-engineer
Source: https://github.com/CODE-SAURABH/OpenSkills/tree/main/qa-engineer
Command: npx skills add https://github.com/CODE-SAURABH/OpenSkills --skill qa-engineer-code-saurabh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents user-facing regressions by systematically testing applications from a real user's perspective, identifying bugs across critical workflows, fixing them with minimal atomic changes, and verifying that the fixes hold.

Core Features & Use Cases

  • End-to-End QA Testing: Test authentication, forms, navigation, APIs, responsive layouts, performance, accessibility, and error states in running applications.
  • Bug Fixing and Verification: Classify issues by severity, diagnose root causes, apply focused fixes, and re-test each issue before proceeding.
  • Regression Prevention: Add automated tests for every manually discovered bug and produce a clear ship-or-hold QA summary with evidence, health scores, and commit details.
  • Use Case: Before releasing a new feature, use this Skill to exercise its happy and sad paths in a browser, validate mobile behavior and network failures, fix blocking defects, and leave regression coverage behind.

Quick Start

Use the qa-engineer skill to run a Standard QA pass against the application's local development server, fix discovered bugs, add regression tests, and provide a ship-or-hold summary.

Frequently Asked Questions about qa-engineer

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

FAQPage Schema
How do I run end-to-end QA testing on a running application before release?

End-to-end QA testing exercises authentication, forms, navigation, APIs, responsive layouts, and error states from a real user's perspective. It finds bugs across critical workflows, fixes them with atomic changes, and verifies the fixes hold before release.

What's the best way to prevent regressions after manually fixing application bugs?

Regression prevention adds automated tests for every manually discovered bug during QA passes. This ensures fixed defects stay fixed and produces a ship-or-hold summary with evidence, health scores, and commit details.

Does browser-based QA testing cover responsive layouts and accessibility checks?

Browser-based QA testing covers responsive layouts, accessibility checks, performance, and network failure handling. It validates mobile behavior and exercises both happy and sad paths to ensure comprehensive pre-release validation.

How do I assess ship readiness for a new feature before deploying?

Ship readiness assessment runs a Standard QA pass against the local development server, classifies issues by severity, diagnoses root causes, applies focused fixes, and produces a clear ship-or-hold summary with health scores.

What do I need to set up before running automated regression testing on my app?

Automated regression testing requires access to a running application, relevant source code, test tooling, browser or end-to-end testing capabilities, and version control for atomic commits to verify fixes and prevent regressions.