Skills test-driven-development

📦

test-driven-development

Name: test-driven-development
Author: CodingCossack

Content revision r1 Safe ⚙️ External commands

Apply Test-Driven Development

Teams often add tests after code and miss broken behavior. This skill enforces test-first work with red, green, and refactor checkpoints.

Supports: Claude Codex Code(CC)

📊 74 Adequate

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "test-driven-development" from https://skillstore.io/skills/codingcossack-test-driven-development.md and its manifest at https://skillstore.io/api/skills/codingcossack-test-driven-development/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/codingcossack-test-driven-development.md Signed manifest GET /api/skills/codingcossack-test-driven-development/manifest Signed lockfile GET /api/skills/codingcossack-test-driven-development/lockfile

Test it

Using "test-driven-development". Add retry behavior to a network client.

Expected outcome:

A first failing test that describes retry count and final success.
A minimal implementation plan that only satisfies that test.
A refactor checkpoint after the test passes.

Using "test-driven-development". Fix empty email addresses being accepted.

Expected outcome:

A regression test that fails when empty email is accepted.
A small validation change that makes the test pass.
A recommendation to keep the test as permanent coverage.

Using "test-driven-development". Clean up a legacy service without tests.

Expected outcome:

A characterization test list for current behavior.
A safe refactoring order with tests kept green.
A boundary for new behavior that must use failing tests first.

Security Audit

Safe

v8 • 7/6/2026 Open versioned report

All 29 static findings were adjudicated as false positives. The detections are Markdown fences, TypeScript snippets, local npm test examples, inline test API names, and a retry test-list bullet, with no malicious execution or network reconnaissance. No prompt injection or semantic security issue was found.

Files scanned

553

Lines analyzed

Review items

False positives ignored

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/codingcossack-test-driven-development/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/codingcossack-test-driven-development/security.svg)](https://skillstore.io/skills/codingcossack-test-driven-development?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/codingcossack-test-driven-development?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/codingcossack-test-driven-development/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/codingcossack-test-driven-development.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

CodingCossack. (2026). test-driven-development security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/codingcossack-test-driven-development/audits/8

BibTeX citation

@techreport{codingcossack-codingcossack-test-driven-development-2026,
  author = {CodingCossack},
  title = {test-driven-development security audit report (audit version 8)},
  institution = {Skillstore},
  year = {2026},
  number = {8},
  url = {https://skillstore.io/skills/codingcossack-test-driven-development/audits/8},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "test-driven-development security audit report (audit version 8)"
version: "unspecified"
type: report
authors:
  - name: "CodingCossack"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/codingcossack-test-driven-development/audits/8"
identifiers:
  - type: other
    value: "skillstore:codingcossack-test-driven-development:audit:8"
    description: "Skillstore immutable audit report identifier"

Compare variants

9 installable variants

Each author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.

Why this variant is first

Highest Skillstore Score

Author / source Skillstore Score Evidence Confidence Skillstore usage Updated

DMJGilbert Recommended

dmjgilbert-test-driven-development

Skillstore Score 79

Evidence Confidence High

Skillstore usage 10

Updated

2026-08-21

obra

obra-test-driven-development

Skillstore Score 78

Evidence Confidence High

Skillstore usage 11

Updated

2026-08-21

Cycleaddict

cycleaddict-test-driven-development

Skillstore Score 78

Evidence Confidence High

Skillstore usage 8

Updated

2026-08-21

Cygnusfear

cygnusfear-test-driven-development

Skillstore Score 78

Evidence Confidence High

Skillstore usage 7

Updated

2026-08-21

DYAI2025

dyai2025-test-driven-development

Skillstore Score 75

Evidence Confidence Medium

Skillstore usage 8

Updated

2026-08-21

CodingCossack Current

codingcossack-test-driven-development

Skillstore Score 74

Evidence Confidence High

Skillstore usage 13

Updated

2026-08-21

ZhanlinCui

zhanlincui-test-driven-development

Skillstore Score 69

Evidence Confidence High

Skillstore usage 99

Updated

2026-08-21

sickn33

sickn33-test-driven-development

Skillstore Score 38

Evidence Confidence Medium

Skillstore usage 9

Updated

2026-08-21

davila7

davila7-test-driven-development

Skillstore Score 38

Evidence Confidence Medium

Skillstore usage 7

Updated

2026-08-21

Skillstore Score

Why this score Evidence Confidence: High

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Implement a Feature Safely

Create one failing test, add the smallest passing code, then refactor while tests stay green.

Fix a Regression

Reproduce the bug with a failing test before changing production code, then keep the test as coverage.

Improve Legacy Code

Add characterization tests to capture current behavior before refactoring or adding new behavior.

Try These Prompts

Start a Small Feature

Use test-driven development for this feature: [describe feature]. Start with one failing test and wait for verification before implementation.

Fix a Bug with Proof

Apply TDD to fix this bug: [describe bug]. First write a test that fails for the current behavior and explains the regression.

Refactor Behind Tests

Help me refactor [component or module]. Identify existing behavior tests first, add characterization tests if needed, then keep behavior unchanged.

Review Test Quality

Review these tests for TDD quality, mock overuse, brittle assertions, and missing behavior coverage. Recommend concrete changes before implementation continues.

Best Practices

Run the new test and confirm it fails before writing production code.
Assert observable behavior instead of internal implementation details.
Refactor only after tests pass, and keep the full suite green.

Avoid

Writing production behavior first and adding tests afterward.
Testing mock existence instead of real user-visible behavior.
Adding test-only methods to production classes for convenience.

Frequently Asked Questions

Does this skill write tests for me?

It guides the workflow and test design. The assistant still needs project context and a working test runner.

Can I use it on legacy code?

Yes. It recommends characterization tests first, then TDD for new behavior changes.

Does every refactor need a new failing test?

No. Pure refactoring keeps behavior unchanged, so existing tests should stay green throughout.

What if the test passes immediately?

The test may cover existing behavior or the wrong requirement. Revise it until it fails for the intended reason.

Does it require a specific test framework?

No. The guidance works with common test runners, but examples use JavaScript and TypeScript style tests.

Is this safe for publication?

The adjudication found no malicious behavior, prompt injection, or unsafe executable code in the reviewed skill text.

Developer Details

Author

CodingCossack

License

MIT

Skillstore revision

Version notice

The author did not declare a version.

Repository

https://github.com/CodingCossack/agent-skills-library/tree/main/skills/test-driven-development

Ref

d11af420e07cd866fe39cfa937efef3223896c06

Maintenance freshness

7/18/2026

Usage

9 downloads · 297 views

File structure

📁 references/

📄 tdd-philosophy.md

📄 testing-anti-patterns.md

📄 SKILL.md

test-driven-development

Install with my Agent

Agent-readable resources

Test it

Security Audit

Risk Factors

Copy report link

Markdown badge

HTML badge

Embed card

APA citation

BibTeX citation

CITATION.cff

Compare variants

Skillstore Score

What You Can Build

Implement a Feature Safely

Fix a Regression

Improve Legacy Code

Try These Prompts

Best Practices

Avoid

Frequently Asked Questions

Developer Details