test-builder

Scaffold Go unit tests for services, models, and controllers using TDD.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/griffnb/claude-plugins --skill test-builder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-builder
Source: https://github.com/griffnb/claude-plugins/tree/main/plugins/backend/skills/testing
Command: npx skills add https://github.com/griffnb/claude-plugins --skill test-builder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Go projects often struggle to establish tests that drive design and ensure coverage. This Skill provides a structured approach to build proper unit tests for services, models, and controllers following TDD.

Core Features & Use Cases

  • Enforces a test-first workflow (RED/GREEN/REFACTOR) for Go services, models, and controllers.
  • Promotes table-driven tests, mocks, and isolation to improve reliability and readability.
  • Guides code authors toward achieving high test coverage and clean commit hygiene in Go projects.

Quick Start

Write a failing test first, then implement the minimal production code to pass, and refactor while preserving test success.

Frequently Asked Questions about test-builder

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

FAQPage Schema
How do I write table-driven unit tests in Go using TDD?

Table-driven unit tests in Go are scaffolded by enforcing a strict test-first workflow, where you write a failing test first, implement minimal production code to pass, and refactor while preserving test success.

What is the best way to achieve high code coverage for Go services and controllers?

Achieving high code coverage for Go services requires scaffolding comprehensive unit tests with mocks and table-driven patterns, enforcing a quality standard of at least 90% coverage and deterministic test execution.

Can I use this to scaffold mocks for Go controller handler coverage?

Yes, scaffolding mocks for Go controller handler coverage is supported, applying table-driven patterns and isolation to ensure reliable and readable tests across packages.

Does this TDD workflow enforce commit hygiene for Go projects?

Yes, the TDD workflow enforces strict commit hygiene for Go projects, guiding code authors through a clear development process while building proper unit tests for models and services.

What are the limitations of applying table-driven tests to Go models?

Table-driven tests for Go models require deterministic execution and isolation, meaning tests must be structured to avoid external dependencies and ensure reliable, repeatable results across packages.