What problem does it solve? Writing consistent, maintainable Go tests requires choosing the right pattern for each scenario—unit tests, TUI state transitions, interactive flows, or golden files—and this Skill provides decision gates and proven patterns so tests cover behavior rather than implementation trivia. ## Core Features & Use Cases - Pattern Selection via Decision Gates: Maps each test target (pure functions, file operations, TUI state, rendered output, external commands) to the correct Go testing pattern. - Bubbletea and teatest Coverage: Distinguishes direct Model.Update() state testing from full interactive flows using teatest.NewTestModel(). - Golden File Discipline: Enforces deterministic golden files updated only through the -update flag, with verification runs afterward. - Use Case: When adding tests to a Go CLI with a Bubbletea TUI, use this Skill to write table-driven unit tests for parsers, direct Update tests for screen transitions, and golden file tests for rendered output. ## Quick Start Ask the AI to write tests for a specific Go package or Bubbletea model following the go-testing patterns, for example: write table-driven tests for my parser package and a teatest flow for the main menu navigation.
