AGENT SKILL

tdd

Apply test-driven development with small, behavior-focused feedback loops. Use when the user asks to build or fix something test-first, mentions red-green-refactor, or wants integration tests.

License 许可
MIT
所属仓库
stevesolun/ctx
最近更新
2026-10-15
Stars
★ 593
Forks
69

01 前言 Front Matter

name
tdd
description
Apply test-driven development with small, behavior-focused feedback loops. Use when the user asks to build or fix something test-first, mentions red-green-refactor, or wants integration tests.

02 资源文件 3

03 SKILL.md 正文

Test-Driven Development

Use small red → green → refactor cycles when a test-first feedback loop is practical. Treat repository conventions, existing tests, and the requested behavior as authoritative.

Loop

  1. Identify one observable behavior and the seam through which callers see it.
  2. Write the smallest meaningful test and confirm that it fails for the expected reason.
  3. Add only enough implementation to make the test pass.
  4. Refactor when doing so improves clarity or design; keep the suite green.
  5. Repeat with the next vertical slice.

Infer seams from public interfaces and nearby tests. Ask the user only when choosing a seam would materially change the product contract, cost, or scope.

Judgment

  • Prefer behavior-focused tests that survive internal refactors.
  • Derive expected results from a specification, worked example, or other independent source rather than duplicating the implementation.
  • Mock external or nondeterministic boundaries when useful; follow established repository patterns where they provide an adequate feedback loop.
  • Prefer vertical slices over a speculative batch of tests. Batch closely related mechanical cases when that is clearer and faster.
  • If a failing-first cycle is impractical—for example in legacy code with no usable seam—state the limitation and establish the nearest reliable characterization or integration test.

Read tests.md for examples and mocking.md when deciding whether and where to use test doubles.

04 同仓库更多 Skills

stevesolun
stevesolun/ctx

toolbox

Pre/post dev toolbox — named bundles of skills/agents loaded before development work and councils of experts invoked after. Run /toolbox or the toolbox.py CLI to list, activate, initialize, export, import, and validate toolboxes. Invoke at the start or end of a dev session, when setting up a new repo, or when sharing toolboxes with a team.

★ 593
stevesolun
stevesolun/ctx

skill-router

Alive skill router — reads the current project's stack and loads/unloads skills dynamically. Invoke at session start or when project context changes.

Skill与智能体开发
★ 593
stevesolun
stevesolun/ctx

repo-stats-autoupdate

Keeps README badge + inline counts in sync with the real number of skills, agents, graph nodes/edges, communities, converted pipelines, and test inventory. Runs automatically on every commit via a git pre-commit hook. Use when the README drifts from reality or before publishing a release.

Skill与智能体开发
★ 593
stevesolun
stevesolun/ctx

find-skills

Discover installable agent skills from ctx's shipped Skills.sh catalog, the Skills.sh search API, and the npx skills CLI. Use when a user asks whether a skill exists, wants to add/update a skill, or needs a repeatable procedure for finding candidate skills safely.

开发工程师Skill与智能体开发
★ 593
stevesolun
stevesolun/ctx

no-mistakes

Validate committed feature-branch changes through the no-mistakes pipeline: intent, rebase, review, test, docs, lint, push, PR, and CI. Use when the user asks to run no-mistakes, ship safely, validate before pushing, or gate a change before it reaches upstream.

★ 593
stevesolun
stevesolun/ctx

zoom-out

Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.

开发工程师Skill与智能体开发
★ 593