dharma-qa

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

1|3|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/AIKAGRYA/dharma_swarm --skill dharma-qa-aikagrya
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dharma-qa
Source: https://github.com/AIKAGRYA/dharma_swarm/tree/main/mode_pack/claude/qa
Command: npx skills add https://github.com/AIKAGRYA/dharma_swarm --skill dharma-qa-aikagrya

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 with real evidence, reproducible steps, and a clear health score. ## Core Features & Use Cases - Structured Verification: Tests flows like a real user and refuses to claim success without verification. - Evidence Collection: Gathers screenshots, console output, and precise reproduction steps for every issue. - Standardized Output: Produces a health score, prioritized issue list, evidence, and top fixes. - Use Case: After shipping a new checkout flow, run this Skill to validate the flow end to end, capture console errors, and receive a health score plus a ranked bug list ready for triage. ## Quick Start Ask the agent to QA-test the checkout flow and return a health score with 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 before release?▼

Run the QA mode against the flow and test it like a real user. The Skill requires verification before claiming success and returns a health score, issue list, evidence, and top fixes.

What evidence should a good bug report include?▼

A good bug report includes screenshots, console output, and precise reproduction steps. This Skill collects exactly those artifacts and attaches them to each reported issue.

What happens when the QA environment is blocked or unavailable?▼

The Skill states the block explicitly instead of guessing or fabricating results. Blocked environments are reported as-is so teams can resolve infrastructure issues first.

How are critical failures handled during QA testing?▼

Critical failures are routed to the dharma-incident-commander mode for escalation. Non-critical results hand off to dharma-retro for retrospective review.

What are the limitations of this QA mode?▼

It focuses on user-facing flow verification rather than unit or load testing. It depends on access to a runnable environment and cannot verify flows when that access is blocked.