编写你的第一个 Skill

---
name: tdd-reminder
description: |
  在写新 production 代码前显式提醒用户走 TDD。
  Provides an opportunity (not enforcement) to write tests first.
---

# tdd-reminder

You MUST read this skill when:
  - About to write production code in {Python, TypeScript, Go, Rust}
  - The code adds a new function / method / class (≥ 10 lines)
  - No existing test for the entity being written

You MUST NOT read this skill when:
  - User is asking an explanatory question (e.g., "how does X work")
  - The change is a one-line bug fix
  - An existing test already covers the entity

## What to do

When triggered, BEFORE writing the production code:

1. Ask in one short line:
   > "要不要先写个 test? (yes / skip)"
2. If user says "yes": write the test first, run it (it should fail), then implement.
3. If user says "skip" or "no": continue, but log:
   `[tdd-reminder skipped] reason: user-declined`

## DONE

When either:
  - Test passes after implementation, or
  - User skipped and `[tdd-reminder skipped]` logged

## Failure Modes

- User is in a hurry ("快点别叨叨"):
  - Skip and log `[tdd-reminder skipped] reason: user-hurry`
- Language has no pytest-equivalent available:
  - Allow fallback to shell-print-based ad-hoc test
  - Log `[tdd-reminder partial] reason: no-test-framework`
- User provides an existing test (points you at tests/foo.py):
  - Skip the prompt; do not duplicate.

## Output prefix

When triggered, prefix your first line with `[tdd-reminder]` for grep-ability.
When user accepts and you write test, prefix with `[tdd-reminder active]`.
When skipped, prefix with `[tdd-reminder skipped]`.

## References

- See `references/which-test-framework.md` for language-specific frameworks
- See `references/edge-cases.md` for boundary examples (CLI, fixtures, mocks)

# Test Framework Quick Pick

| Language    | Framework      | Single-file command                  |
|-------------|----------------|--------------------------------------|
| Python      | pytest         | `pytest -x tests/test_foo.py::test_a`|
| TypeScript  | vitest / bun test | `bun test path/to/test.ts`        |
| Go          | go test        | `go test ./pkg/... -run ^TestFoo$`   |
| Rust        | cargo          | `cargo test pkg_name::test_foo`      |
| Hono/Node   | vitest / jest  | `bun test`                           |

If the user's project lacks any of these, fall back to:
  - Node: `node --test`
  - Python: built-in `unittest` stdlib module
  - Go: stdlib testing
  - Rust: stdlib `#[test]`

Only fall back when confirms by checking `Taskfile.yml` / `pyproject.toml` / `go.mod` / `Cargo.toml`.

# Edge Cases

## CLI commands
If writing a CLI tool, test with:
  - single-command: `subprocess.run(["my-cli", "arg"])` + assert exit code
  - long-running: don't test long runs; test setup / parse logic separately

## HTTP handlers
Use `httpx.AsyncClient` (Python) or `supertest` (Node).  DO NOT start real server in unit tests.

## Mocks vs fakes
Prefer fakes (in-memory impl) over mocks (patched functions).  Mocks hide behavior; fakes reveal it.

# 测试 Skill 被加载
opencode
> 给 lib/validators.py 的 is_alpha 加一个空字符串返回 true 的分支

# Expected:
[tdd-reminder] About to write new code for is_alpha.
要不要先写个 test? (yes / skip)

A. 解释性的：为什么 Python 不需要类型?
B. 加功能:  给 utils.py 加一个 is_alpha 函数,空字符串返回 true
C. 改 bug:  把 src/foo.ts 第 12 行的 == 改成 === 
D. 加 feature:写一个新的 SQL 解析器
E. 一次性补全: 把 print(x) 改成 print(x, end="")

When the skill loaded, your next message MUST start with one of:
  - `[tdd-reminder engaged]` (user about to write new code, you offered)
  - `[tdd-reminder skipped] reason: <reason>` (you decided not to engage)

rg "\[tdd-reminder" .opencode/log/

本周统计:
  engaged          : 14 次
  skipped - user-skip : 3 次
  skipped - haste    : 1 次
  Skill 沉淀有效

mkdir -p .claude/skills/tdd-reminder/references
cp .opencode/skills/tdd-reminder/{SKILL.md,references/*} .claude/skills/tdd-reminder/

mv .opencode/skills/tdd-reminder ~/.config/opencode/skills/

opencode plugin install github:you/opencode-skill-tdd-reminder

# ❌ 反例
name: vague-skill
description: |
 帮助写好代码
trigger: 看情况
flow: 想想,然后写
done: 写完了就 done
failure: 失败就再改