Tdd workflows

Skill lingxling/awesome-skills-cn/antigravity-awesome-skills/plugins/agentic-awesome-skills/skills/tdd-workflows

Use when working with tdd workflows tdd cycle (Alias for tdd-workflows-tdd-cycle)From its SKILL.md

Install

npx -y skills add lingxling/awesome-skills-cn --skill tdd-workflows

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

1.3 KB, 262 tokens by cl100k_base, as published. Nobody here has run it

Tdd Workflows

This is an alias. The canonical skill is tdd-workflows-tdd-cycle.

This skill redirects to tdd-workflows-tdd-cycle. Load it from the vault:

skill-libraries/testing/tdd-workflows-tdd-cycle/SKILL.md

When to Use

Use this skill when working with tdd workflows tdd cycle (Alias for tdd-workflows-tdd-cycle)

Why this alias exists

Users commonly search for tdd-workflows but the full skill name in this collection is tdd-workflows-tdd-cycle. This alias ensures discoverability.

Limitations

Use this skill only when the task clearly matches the scope described above.
Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Examples

Use @tdd-workflows for this task: Use when working with tdd workflows tdd cycle (Alias for tdd-workflows-tdd-cycle).

Apply the skill to my current work and walk me through the safest next steps,
key checks, and the concrete output I should produce.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most tdd skills give in 262 tokens

Counted across 594 of the 695 authors here whose files we hold, read 2026-09-06

Write minimal code to pass the testin 356 of 594, across 332 files
Write a failing test before writing production codein 240 of 594, across 221 files
Refactor code only after tests passin 184 of 594, across 169 files
Refactor code while keeping tests greenin 140 of 594, across 133 files
Verify the test fails for the expected reasonin 133 of 594, across 121 files
Run tests after each refactor stepin 108 of 594, across 102 files
Use real code instead of mocks whenever possiblein 97 of 594, across 85 files
Reproduce bugs with a failing test before fixingin 90 of 594, across 81 files
Write tests before implementing codein 88 of 594, across 70 files
Verify the test passes after writing codein 71 of 594, across 61 files
Write one test for one behaviorin 71 of 594, across 63 files
Run the full test suitein 63 of 594, across 56 files

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.