agent-qa-debug-fix
Use after an agent-qa run has failed and you need to debug, patch, and verify the issue using MCP evidence, logs, artifacts, and local code changes instead of…
Use when creating, editing, validating, or running agent-qa tests, suites, or hooks. Prefer agent-qa MCP tools, enforce canonical agent-qa IDs, and use the bundled schema reference to avoid hallucinated config keys or YAML fields.
$ npx -y skills add vostride/agent-qa --skill agent-qa-authoring --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/agent-qa-authoringContext preview
The summary Claude sees to decide when to auto-load this skill.
Use when creating, editing, validating, or running agent-qa tests, suites, or hooks. Prefer agent-qa MCP tools, enforce canonical agent-qa IDs, and use the bundled schema reference to avoid hallucinated config keys or YAML fields.
name: agent-qa-authoring description: Use when creating, editing, validating, or running agent-qa tests, suites, or hooks. Prefer agent-qa MCP tools, enforce canonical agent-qa IDs, and use the bundled schema reference to avoid hallucinated config keys or YAML fields. metadata: short-description: Author agent-qa tests safely
1. Discover the local surface with `agent_qa_discover`. 2. Inspect active config with `agent_qa_get_config`, especially targets, devices, providers, and `services.mcp`. 3. Load `references/agent-qa-contracts.json` when you need exact schema fields or ID contracts. 4. Generate every new ID with agent-qa tooling:
5. Never hand-write IDs. Validate existing IDs with `agent_qa_validate_id` or `agent-qa ids validate <type> <id> --json`. 6. Validate definitions before saving:
7. Prefer MCP authoring mutations:
8. Use CLI/YAML fallback only when MCP is unavailable. Keep file paths matched by `workspace.testMatch` or `workspace.suiteMatch`.
Open-source self-improving QA agent for software teams. A test harness with memory. Write tests in natural language for web and mobile. agent-qa learns from every run, adapts to UI changes, and catches regressions before you ship.
Repo: vostride/agent-qa
Use after an agent-qa run has failed and you need to debug, patch, and verify the issue using MCP evidence, logs, artifacts, and local code changes instead of…
Use when investigating failed agent-qa runs, inspecting artifacts, classifying failures, or comparing recent runs. Prefer agent-qa MCP run/artifact tools and…