Test driven development

Skill roronoazoroshao369/vibe-coding-os/skills/core/test-driven-development

Vibe Coding OS — Claude/Codex/Cursor skill framework with 139 skills, 111 commands, 95 templates, 22 tracked sources, 28/28 validation gates PASS. Quality Shield, Engineering Discipline Pack, plugin marketplace.From the repository description

Install

npx -y skills add roronoazoroshao369/vibe-coding-os --skill test-driven-development

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

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.5 KB, 306 tokens by cl100k_base, as published. Nobody here has run it

Skill: Test Driven Development

Purpose

Use a red-green-refactor loop for behavior changes and bug fixes.

When to use

Use when behavior can be specified with tests, especially new features, regressions, and risky refactors.

Inputs

Expected behavior, acceptance criteria, existing test framework, target slice, and validation commands.

Workflow

Pick one vertical behavior slice.
Write or update a failing test first when practical.
Run the targeted test and confirm red for the right reason.
Implement the smallest code change to pass.
Refactor while tests stay green.
Repeat for the next slice and finish with broader validation.

Outputs

Failing test evidence, passing test evidence, implementation notes, refactor notes, and remaining gaps.

Failure modes

Writing tests after broad implementation, testing implementation details, skipping the red state, or expanding scope mid-loop.

Verification checklist

Red state observed or justified; green state observed; refactor kept behavior; verification commands are recorded.

Ghi chú tiếng Việt

TDD ở đây là red-green-refactor theo lát nhỏ. Dùng cho thay đổi hành vi và bug. File liên quan: commands/vibe-tdd.md, references/features/diagnosis-loop.md. Khi upstream update TDD, so sánh nguyên tắc, không sao chép ví dụ.

What ships with it

Read from the repository

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

Gives 2 of the 12 instructions most tdd skills give in 306 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 codehere, and in 240 of 594, across 221 files
Refactor code only after tests passin 184 of 594, across 169 files
Refactor code while keeping tests greenhere, and in 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

Said here and by no other author read

Pick one vertical behavior slice
Repeat for next behavior slice

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.