agentsclimarketplace

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.

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, 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

  1. Pick one vertical behavior slice.
  2. Write or update a failing test first when practical.
  3. Run the targeted test and confirm red for the right reason.
  4. Implement the smallest code change to pass.
  5. Refactor while tests stay green.
  6. 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ụ.

Gives 2 of the 12 instructions most tdd skills give

Counted across 439 of the 443 authors here whose files we hold, read 2026-08-06

  • write minimal code to pass the testin 302 of 439, across 218 files
  • write a failing test firsthere, and in 176 of 439, across 112 files
  • refactor code only after tests passin 171 of 439, across 101 files
  • watch the test fail before writing codein 142 of 439, across 93 files
  • test one behavior per testin 106 of 439, across 44 files
  • refactor code while keeping tests greenhere, and in 99 of 439, across 86 files
  • delete code written before testsin 98 of 439, across 54 files
  • run tests after each refactor stepin 85 of 439, across 54 files
  • Use real code instead of mocks unless unavoidablein 64 of 439, across 21 files
  • confirm the test fails for the right reasonin 64 of 439, across 60 files
  • reproduce bugs with a test before fixingin 53 of 439, across 36 files
  • write tests before implementationin 48 of 439, across 39 files

Said here and by no other author read

  • Use a red-green-refactor loop for behavior changes and bug fixes
  • Repeat for the next slice and finish with broader validation
  • Record verification commands

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.