skills.rest
AmitabhainArunachala
AmitabhainArunachalaCOMMUNITY
Explore all skills by this author →
GitHub

dharma-qa

Tests user-facing flows and produces health scores with evidence-backed issue reports.

Updated Aug 5, 2026
Search Tags:#testing#screenshots#qa#verification#issue tracking#bug report#health score
One-click install
npx skills add https://github.com/AmitabhainArunachala/dharma_swarmv.01 --skill dharma-qa-amitabhainarunachala
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dharma-qa
Source: https://github.com/AmitabhainArunachala/dharma_swarmv.01/tree/main/mode_pack/claude/qa
Command: npx skills add https://github.com/AmitabhainArunachala/dharma_swarmv.01 --skill dharma-qa-amitabhainarunachala

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Verifying that a user-facing flow actually works often devolves into unverified claims and vague bug reports. This Skill enforces structured QA testing that gathers real evidence, produces a health score, and delivers reproducible issue reports instead of guesses. ## Core Features & Use Cases - Evidence-Based Verification: Captures screenshots, console output, and precise reproduction steps rather than relying on assumptions. - Health Scoring: Produces a health score plus a short prioritized bug list for every tested flow. - Structured Handoff: Routes critical failures to an incident commander mode and standard results to a retro mode. - Use Case: After shipping a new checkout flow, run this mode to click through it like a real user, capture console errors and screenshots, and receive a health score with the top fixes to prioritize. ## Quick Start Ask the assistant to QA the current user-facing flow and return a health score, evidence, and a prioritized issue list.

Frequently Asked Questions about dharma-qa

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

FAQPage Schema
How do I verify a user-facing flow actually works?▼

Test the flow like a real user and gather evidence such as screenshots, console output, and exact reproduction steps. This Skill produces a health score and prioritized issue list so verification is based on observed behavior, not assumptions.

What should a good QA bug report include?▼

A good QA report includes a health score, a prioritized issue list, supporting evidence like screenshots and console logs, and the top recommended fixes. Precise reproduction steps make each issue actionable for developers.

What happens when a critical failure is found during QA?▼

Critical failures are routed to the dharma-incident-commander mode for escalation. Non-critical results are handed off to the dharma-retro mode for review and follow-up.

What if the test environment is blocked or unavailable?▼

The Skill requires stating the block explicitly instead of guessing or claiming success. This keeps reports honest and prevents false positives when verification cannot be completed.

When should I not rely on this QA mode?▼

This mode focuses on user-facing flow verification with evidence, not deep load testing, security penetration testing, or automated unit test generation. Use dedicated tools for those specialized testing needs.

Related Skills

Explore More Software Engineering Skills→
LennyDevXLennyDevX

nuxchain-deploy

Build and deploy NuxChain production assets to Vercel with environment synchronization.

Community
Advanced
BrunoAMSilvaBrunoAMSilva

my-issues

List issues assigned to the current user in the current GitHub repository.

Community
Basic
LordjiggyLordjiggy

qa-engineer

Generate test plans, reproduce bugs, and design regression suites.

Community
Intermediate
VYRE-StudiosVYRE-Studios

webapp-testing

Automate end-to-end web testing across browsers and APIs with Playwright or Cypress.

Official
Intermediate