القائمة
Drives development with tests. Use when implementing logic, fixing bugs, or changing behavior. Define behavior first, prove with failing test, implement minimally, then refactor safely.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Ultra caveman communication mode. Maximum compression while preserving technical accuracy. Abbreviates prose aggressively; keeps code and technical identifiers exact. Use when user says "/caveman ultra" or explicitly asks for maximum token efficiency.
Optimizes agent context setup. Use when starting a new session, when agent output quality degrades, when switching between tasks, or when you need to configure rules files and context for a project.
Provides a guide for setting up Golang project layouts and workspaces. Use when starting a new Go project, organizing an existing codebase, setting up a monorepo with multiple packages, creating CLI tools with multiple main packages, deciding between cmd/internal/pkg directory conventions, or discussing package restructuring, package splits, or module splits.
Production-ready Golang tests — table-driven tests, testify suites and mocks, parallel tests, fuzzing, fixtures, goroutine leak detection with goleak, snapshot testing, code coverage, integration tests, idiomatic test naming. Use when writing or reviewing Go tests, choosing a testing approach, setting up Go test CI, or debugging flaky/slow tests. For testify-specific APIs see `samber/cc-skills-golang@golang-stretchr-testify`; for measurement methodology see `samber/cc-skills-golang@golang-benchmark`.
Delivers changes incrementally. Use when implementing any feature or change that touches more than one file. Use when you're about to write a large amount of code at once, or when a task feels too big to land in one step.
Extracts what the user actually wants instead of what they think they should want. Achieves this through one-question-at-a-time interview until ~95% confidence about the underlying intent. Use when an ask is underspecified ("build me X" without "for whom" or "why now"), when the user explicitly invokes ("interview me", "grill me", "are we sure?", "stress-test my thinking"), or when you catch yourself silently filling in ambiguous requirements before any plan, spec, or code exists.
| name | test-driven-development |
| description | Drives development with tests. Use when implementing logic, fixing bugs, or changing behavior. Define behavior first, prove with failing test, implement minimally, then refactor safely. |
Test-Driven Development (TDD) means behavior-first delivery:
TDD goal: reduce regression risk, improve design feedback, keep changes verifiable.
This skill describes TDD process only.
For Go testing examples, patterns, and tooling, use:
.agents/skills/golang-testing/SKILL.mdWhen not needed:
RED -> GREEN -> REFACTOR
After behavior change:
After applying this TDD workflow in Go projects, consult:
.agents/skills/golang-testing/SKILL.mdUse that skill for: