Run tiered web application QA tests and fix bugs with atomic commits.
npx skills add https://github.com/deveshkumars/Intentra --skill qa-deveshkumars
Please help me install this Agent Skill. Skill: qa Source: https://github.com/deveshkumars/Intentra/tree/main/qa Command: npx skills add https://github.com/deveshkumars/Intentra --skill qa-deveshkumars
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". Proactively suggest when the user says a feature is ready for testing or asks "does this work?". Three tiers: Quick (critical/high only), Standard (+ medium), Exhaustive (+ cosmetic). Produces before/after health scores, fix evidence, and a ship-readiness summary. For report-only mode, use /qa-only.
Ask the QA assistant to start a regression plan on the current build and generate a full QA report.
High-intent search queries and answers about installing and using this skill.
You can automate web application testing and bug fixing by running systematic QA cycles that record failures, guide iterative source code fixes with atomic commits, and re-verify until passing. It outputs health scores and ship-readiness summaries.
Systematic QA testing for feature readiness automates test execution across web applications, records failures, and generates before/after health scores to objectively determine if a feature is ready to ship.
Yes, you can run regression tests on your current build. The QA process automates testing, iteratively fixes discovered bugs, and generates a full report including health scores, fix evidence, and a ship-readiness summary.
The QA testing process supports three coverage tiers: Quick for critical and high issues only, Standard adding medium issues, and Exhaustive adding cosmetic issues, allowing you to balance testing speed and quality.
To assess web application bugs without automatic source code modifications, use the report-only mode. This mode runs systematic QA testing and generates health scores and ship-readiness summaries without applying iterative fixes.
Atomic commits during web application bug fixing should be used when iteratively correcting source code identified by systematic QA testing. Each fix is committed atomically and re-verified to ensure the regression is resolved without introducing new failures.
reomgitAutomate QA testing and bug fixing for web applications with Bash scripts.
concept2cureTest web applications, identify defects, and document fixes with health scores.
myrealtripGuide creation and orchestration of custom Claude Code Skills.
Marshall-HallenbeckDiagnose and repair failing test suites across multiple language ecosystems.
