go-testing

Agent Skills › Gentleman-Programming/gentle-ai › go-testing

go-testing

GitHub

用于编写和审查 Go 测试的规范，涵盖表驱动测试、Bubbletea TUI 流测试（teatest）、黄金文件管理及集成测试跳过策略，确保测试行为与状态转换的正确性。

internal/assets/skills/go-testing/SKILL.md Gentleman-Programming/gentle-ai

Trigger Scenarios

编写或审查 Go 单元测试增加 Go 测试覆盖率测试 Bubbletea/TUI 交互流程使用 teatest 进行终端测试更新或生成黄金文件

Install

npx skills add Gentleman-Programming/gentle-ai --skill go-testing -g -y

More Options

Non-standard path

npx skills add https://github.com/Gentleman-Programming/gentle-ai/tree/main/internal/assets/skills/go-testing -g -y

Use without installing

npx skills use Gentleman-Programming/gentle-ai@go-testing

指定 Agent (Claude Code)

npx skills add Gentleman-Programming/gentle-ai --skill go-testing -a claude-code -g -y

安装 repo 全部 skill

npx skills add Gentleman-Programming/gentle-ai --all -g -y

预览 repo 内 skill

npx skills add Gentleman-Programming/gentle-ai --list

SKILL.md

Frontmatter

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

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

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