skills.rest
NaKMiers
NaKMiersCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

qa

Automates web application QA testing and bug fixing with before/after health scores.

1|2|Updated Jan 4, 2024
Search Tags:#automation#testing#e2e#qa#verification#bug-fix#web-app
One-click install
npx skills add https://github.com/NaKMiers/Port4lio --skill qa-nakmiers
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/NaKMiers/Port4lio/tree/main/.agents/skills/qa
Command: npx skills add https://github.com/NaKMiers/Port4lio --skill qa-nakmiers

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Systematically QA test a web application and fix bugs found. Runs QA testing, then iteratively fixes bugs in source code, committing each fix atomically and re-verifying. Use when asked to "qa", "QA", "test this site", "find bugs", "test and fix", or "fix what's broken".

Core Features & Use Cases

  • End-to-end QA passes that identify defects across UI, API, and data layers.
  • Automatic, atomic bug fixes with verifiable, before/after health checks and a ship-readiness summary.
  • Proactive guidance and modes (e.g., /qa-only) to run QA in report-only or active fix modes.

Quick Start

Run a full QA cycle on the current project, log failures, fix them atomically, and re-run until health is green.

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 a web application?▼

Automated QA testing for a web application is executed by running a full QA cycle that identifies defects across UI, API, and data layers, and then iteratively fixing them in source code with verifiable health checks.

What is the process for finding and fixing bugs before deploying to staging?▼

Finding and fixing bugs before staging involves running end-to-end QA passes, committing atomic bug fixes to source code, and re-verifying until you receive a ship-readiness summary with green health scores.

Can I run a QA test on my web app without automatically applying code fixes?▼

Yes, you can run a QA test without applying code fixes by using the optional /qa-only mode, which operates as a report-only pass to identify defects across your web application without modifying source code.

Does this QA testing approach work across both development and staging deployments?▼

This QA testing approach works across both development and staging deployments, allowing you to act on QA requests to find bugs or verify fixes regardless of which environment your web application is currently running in.

What's the best way to verify that my bug fixes actually resolve the original defects?▼

The best way to verify bug fixes is through automated before and after health checks, which re-run QA testing after each atomic source code commit to confirm the defect is resolved and generate a ship-readiness summary.

Why do I need to re-run QA testing after committing a bug fix?▼

You need to re-run QA testing after committing a bug fix to verify the fix resolved the original defect without introducing new issues, ensuring your web application maintains a green health score before shipping.

Related Skills

Explore More Software Engineering Skills→
nocnocgroupnocnocgroup

qa

Automate structured QA testing of web applications with standardized reports.

Official
Advanced
wodehwodeh

qa

Test web applications, report defects, and iteratively fix them with health scores.

Community
Advanced
benrapportbenrapport

qa

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

Community
Advanced
abhishekmmgnabhishekmmgn

qa

Automate web application QA testing with tiered test suites and health scoring.

Community
Advanced