skills.rest
ingoatl
ingoatlCOMMUNITY
Explore all skills by this author →
GitHub

qa

Run QA tests on a web application and fix bugs with atomic commits.

Updated Aug 23, 2026
Search Tags:#automation#testing#qa#atomic-commits#bug-fix#web-app
One-click install
npx skills add https://github.com/ingoatl/propertycentral --skill qa-ingoatl
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/ingoatl/propertycentral/tree/main/.claude/skills/gstack/qa
Command: npx skills add https://github.com/ingoatl/propertycentral --skill qa-ingoatl

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

QA work often stalls projects when bugs slip through and fixes are inconsistently verified. This Skill provides a disciplined, repeatable QA workflow that surfaces issues, captures before/after evidence, and coordinates atomic fixes with re-verification.

Core Features & Use Cases

  • Structured test execution: run tests against the web app, collect evidence, and log failures.
  • Atomic bug fixes: commit each fix separately and re-run verification to confirm impact.
  • Real-world scenarios: validate forms, navigation, error states, and performance under typical user flows.

Quick Start

Run a complete QA pass on the target web app, then iteratively fix each bug and re-verify.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I run automated QA testing and fix bugs in a web application?▼

Automated QA testing and bug fixing for a web application is executed by running structured test scenarios, iteratively fixing source code with atomic commits, and re-verifying to confirm impact. It outputs before/after health scores and ship-readiness reports.

What's the best way to structure web app QA testing across different levels of coverage?▼

Structuring web app QA testing across coverage levels is done by selecting Quick, Standard, or Exhaustive test tiers. Each tier identifies real-world scenarios like form validation, navigation, error states, and performance to validate typical user flows.

Can I use atomic commits to track bug fixes during QA testing?▼

Atomic commits are used to track bug fixes during QA testing by committing each source code fix separately. After committing, re-run verification to confirm the specific impact of the isolated fix on the web application.

Does this QA workflow generate evidence and ship-readiness reports?▼

This QA workflow generates ship-readiness reports by collecting evidence and logging failures during initial test execution, then capturing before and after health scores once iterative bug fixes are applied and re-verified.

What types of real-world scenarios are covered in web app QA testing?▼

Real-world scenarios covered in web app QA testing include validating forms, testing navigation, checking error states, and evaluating performance under typical user flows to ensure comprehensive application health.

Why do I need to re-verify after applying a bug fix?▼

Re-verifying after applying a bug fix is needed to confirm that the atomic source code change actually resolved the issue without introducing regressions, ensuring the web application maintains its improved health score.

Related Skills

Explore More Software Engineering Skills→
benrapportbenrapport

qa

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

Community
Advanced
timurgaleevtimurgaleev
5

canary

Monitor post-deploy web apps for defects and performance regressions.

Community
Advanced
x-meshx-mesh
1

build

Automate build script execution for software development workflows.

Official
Intermediate
JuanMS20JuanMS20
1

e2e-testing

Automate end-to-end tests with Playwright, Cypress, or Selenium.

Community
Advanced