qa

Writes unit tests, reviews test coverage, and files bugs for failing tests.

Updated May 2, 2026
One-click install
npx skills add https://github.com/whinchman/midi-man-mk3 --skill qa-whinchman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/whinchman/midi-man-mk3/tree/main/.claude/skills/qa
Command: npx skills add https://github.com/whinchman/midi-man-mk3 --skill qa-whinchman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Ensuring a codebase is well-tested requires disciplined, repetitive work: auditing coverage gaps, writing isolated unit tests, mocking external dependencies, and documenting bugs. This Skill automates that QA workflow so test suites grow consistently without touching application code. ## Core Features & Use Cases - Test Coverage Auditing: Surveys existing test frameworks, files, and fixtures to identify untested modules and critical paths. - Unit Test Authoring: Writes deterministic, independent unit tests with mandatory mocking, stubbing, and spying of all external dependencies (HTTP, databases, file systems). - Branch Review & Bug Filing: Reviews branch diffs for risky code paths and logs application bugs to a BUGS.md file with severity and reproduction steps. - Use Case: Assign a task file requesting tests for a new sequencer clock module; the agent plans the test strategy, creates a git worktree, implements mocked unit tests, runs the full suite, and reports coverage. ## Quick Start Ask the agent to pick up the pending qa task and write unit tests for the specified module, mocking all external dependencies.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I write unit tests with mocked external dependencies?▼

Replace any code path touching HTTP endpoints, databases, file systems, or external APIs with a stub, mock, or spy. Mock HTTP clients return canned responses, database interfaces are stubbed, and spies verify external calls received correct arguments.

How to audit test coverage gaps in an existing codebase?▼

Survey the test framework, existing test files, shared fixtures, and coverage reports, then map which modules and critical paths lack tests. The agent documents findings in a test plan before writing any test code.

Can the QA agent modify application code to fix failing tests?▼

No, the agent never modifies application code and writes only test code, fixtures, and quality reports. If a failure reveals an application bug, it is filed in BUGS.md with file, line, severity, and reproduction steps.

What makes a unit test deterministic and independent?▼

Tests must produce the same result on every run and execute in any order without shared state. Each test uses descriptive names, covers happy paths plus edge and error cases, and never depends on another test's state.

When should integration or end-to-end tests be used instead?▼

This workflow permits only unit tests; integration and e2e tests are explicitly out of scope. Use a separate testing approach when you need to verify real database connections, live APIs, or full system behavior.