Skip to content
Skill Authoring
Skill

/go-testing

Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.

BOOST
From plugin
gentle-ai
7.8k18 skills11 agents2 commands
Install
$ npx -y skills add Gentleman-Programming/gentle-ai --skill go-testing --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/go-testing

Context preview

The summary Claude sees to decide when to auto-load this skill.

Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.

SKILL.md

go-testing.SKILL.md
name: go-testing
description: "Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns."
license: Apache-2.0
metadata:
  author: gentleman-programming
  version: "1.0"

Activation Contract

Load this skill when writing or reviewing Go tests, adding coverage, testing Bubbletea/TUI flows, using `teatest`, or updating golden files.

Hard Rules

  • Prefer table-driven tests for multiple cases; use `t.Run(tt.name, ...)`.
  • Test behavior and state transitions, not implementation trivia.
  • Use `t.TempDir()` for filesystem tests; never rely on a real home directory.
  • Keep integration tests skippable with `testing.Short()` when they run external commands or slow flows.
  • For Bubbletea, test `Model.Update()` directly for state changes; use `teatest` only for interactive flows.
  • Golden files must be deterministic; update only through the repo's `-update` path and rerun tests without `-update`.
  • Use small mocks/interfaces around system or command execution boundaries.

Decision Gates

| Target | Test pattern | |---|---| | Pure function or parser | Table-driven unit test. | | Error behavior | Explicit success and failure cases. | | File operations | `t.TempDir()` plus focused assertions. | | TUI state transition | Direct `Model.Update()` call with `tea.Msg`. | | Full TUI interaction | `teatest.NewTestModel()`. | | Rendered output | Golden file test. | | Real external command | Integration test; skip in `-short`. |

Execution Steps

1. Identify behavior under test and the smallest public boundary that proves it. 2. Choose the test pattern from the decision gate. 3. Name cases by scenario, not input mechanics. 4. Assert outputs, errors, state, and side effects explicitly. 5. Run the narrow package test first, then the relevant broader suite. 6. For golden updates: run with `-update`, inspect diff, then rerun without `-update`.

Output Contract

Report test files changed, scenarios covered, commands executed, golden files updated, and any skipped integration scope.

References

  • [references/examples.md](references/examples.md) — compact table-driven, Bubbletea, teatest, golden, and command examples.
Read more
Ships withgentle-ai

Gentle-AI configures the AI coding agents you already use: Claude Code, Cursor, OpenCode, Codex, Pi, and more. Choose persistent memory, Organic-Driven Development, curated skills, MCP servers, personas, and optional bounded review. Open source, no agent lock-in.

Get the whole plugin

Other skills on gentle-ai.