dev-testing

Enforce 85% unit test coverage for Go, TypeScript, and Python.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/withmartian-sandbox-darkside/ghrc-y-3126672651424eddb640ecc81321a665 --skill dev-testing-withmartian-sandbox-darkside
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-testing
Source: https://github.com/withmartian-sandbox-darkside/ghrc-y-3126672651424eddb640ecc81321a665/tree/main/dev-team/skills/dev-testing
Command: npx skills add https://github.com/withmartian-sandbox-darkside/ghrc-y-3126672651424eddb640ecc81321a665 --skill dev-testing-withmartian-sandbox-darkside

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensure every acceptance criterion is verified with executable unit tests and that overall unit test coverage meets the minimum quality gate so unverified code cannot progress through the delivery pipeline.

Core Features & Use Cases

  • TDD orchestration: Guides RED→GREEN→REFACTOR cycles and dispatches a QA analyst agent to write and run tests.
  • Coverage enforcement: Validates language-specific coverage (Go, TypeScript, Python) against an 85% minimum threshold and loops with implementers until met or escalated.
  • Traceability & reporting: Produces a traceability matrix mapping acceptance criteria to tests, structured coverage reports, and handoff artifacts for the next gate.
  • Use case: After Gate 0 implementation, run this skill to verify unit tests cover all ACs, close coverage gaps, and prepare the unit for code review.

Quick Start

Run the dev-testing skill to verify unit tests achieve at least 85% coverage and produce a traceability matrix for the given task.

Frequently Asked Questions about dev-testing

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

FAQPage Schema
How do I enforce an 85% unit test coverage threshold for Go, TypeScript, and Python?

To enforce an 85% unit test coverage threshold, apply this skill to Gate 3 verification in TDD workflows to validate language-specific coverage commands and loop with implementers until the minimum threshold is met.

How do I map acceptance criteria to unit tests for traceability?

Map acceptance criteria to unit tests by generating a traceability matrix during post-implementation testing, ensuring every criterion is verified with executable tests and producing structured coverage reports for review.

Can I use this skill to orchestrate TDD workflows for Python and TypeScript?

Yes, you can use this skill to orchestrate TDD workflows for Python and TypeScript by guiding RED→GREEN→REFACTOR cycles and dispatching a QA analyst agent to write and run tests before code review.

What is the best way to verify acceptance criteria with executable unit tests in a delivery pipeline?

The best way to verify acceptance criteria with executable unit tests is running post-implementation verification to close coverage gaps, block unverified code from progressing, and prepare handoff artifacts for the next gate.

Why does my unit test coverage verification fail during the Gate 3 pre-review testing phase?

Unit test coverage verification fails during Gate 3 when overall coverage drops below the 85% minimum threshold or acceptance criteria lack mapped executable tests, requiring implementers to loop and close gaps before escalation.