Skills test-driven-development

📦

test-driven-development

Name: test-driven-development
Author: DMJGilbert

Content revision r1 Safe

Practice Test-Driven Development

AI coding agents often write implementation code before proving expected behavior with tests. This skill enforces a red, green, refactor workflow for safer feature work, bug fixes, and refactoring.

Supports: Claude Codex Code(CC)

🥉 79 Bronze

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/dmjgilbert-test-driven-development.md and its manifest at https://skillstore.io/api/skills/dmjgilbert-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/dmjgilbert-test-driven-development.md Signed manifest GET /api/skills/dmjgilbert-test-driven-development/manifest Signed lockfile GET /api/skills/dmjgilbert-test-driven-development/lockfile

Test it

Using "test-driven-development". Add validation that rejects empty project names.

Expected outcome:

The assistant first proposes a focused failing test for empty names, explains the expected failure, implements the smallest validation change, then reruns the test suite.

Using "test-driven-development". Fix a date parsing bug that accepts invalid months.

Expected outcome:

The assistant captures the invalid month case in a regression test, confirms the test fails, changes parsing logic, and checks that existing tests still pass.

Using "test-driven-development". Clean up duplicated payment formatting logic.

Expected outcome:

The assistant verifies existing behavior with tests, extracts shared formatting only after green tests, and keeps the refactor separate from new behavior.

Security Audit

Safe

v8 • 7/6/2026 Open versioned report

The static findings are false positives caused by benign development workflow language in SKILL.md. The skill provides test-driven development guidance and contains no prompt injection, data exfiltration intent, unsafe command instructions, or reconnaissance behavior.

Files scanned

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/dmjgilbert-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/dmjgilbert-test-driven-development/security.svg)](https://skillstore.io/skills/dmjgilbert-test-driven-development?utm_source=security_passport_badge)

HTML badge

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

Embed card

<iframe src="https://skillstore.io/embed/skills/dmjgilbert-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

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

BibTeX citation

@techreport{dmjgilbert-dmjgilbert-test-driven-development-2026,
  author = {DMJGilbert},
  title = {test-driven-development security audit report (audit version 8)},
  institution = {Skillstore},
  year = {2026},
  number = {8},
  url = {https://skillstore.io/skills/dmjgilbert-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: "DMJGilbert"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/dmjgilbert-test-driven-development/audits/8"
identifiers:
  - type: other
    value: "skillstore:dmjgilbert-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 Current

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

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

Add a Feature Safely

Write a failing test for the new behavior, implement the smallest change, then refactor after tests pass.

Fix a Reproducible Bug

Capture the bug with a failing regression test before changing production code.

Refactor Existing Code

Keep behavior protected by tests while improving names, removing duplication, and extracting helpers.

Try These Prompts

Start With TDD

Use the test-driven-development skill for this change. First write one minimal failing test for the requested behavior, show why it fails, then implement only enough code to pass it.

Create a Regression Test

Use TDD to fix this bug. Write a failing regression test that reproduces the problem, confirm the failure, then make the smallest production change that passes the test.

Refactor Under Test

Apply the red, green, refactor cycle to this refactor. Confirm current behavior is covered, keep all tests green, and stop if the refactor requires behavior changes.

Recover From Failed Attempts

Use the skill when repeated test fixes fail. After three unsuccessful fixes, stop implementation, analyze the architecture, and propose a new test-first plan before continuing.

Best Practices

State the expected failing behavior before editing production code.
Keep each test focused on one observable behavior.
Refactor only after all relevant tests are passing.

Avoid

Writing implementation code before a failing test exists.
Keeping a test that passes before the feature is implemented.
Adding extra features during the green phase.

Frequently Asked Questions

What does this skill do?

It instructs the assistant to follow a strict red, green, refactor workflow for production coding tasks.

Does it run tests automatically?

It tells the assistant to run or request tests, but actual execution depends on the available tool environment.

Can it be used for bug fixes?

Yes. It requires a failing regression test before changing production code.

Can it be used for refactoring?

Yes. It requires tests to remain green while duplication, naming, or structure is improved.

When should it not be used?

It allows exceptions for throwaway prototypes, generated code, and config files when the user permits them.

Which tools can use it?

The report lists support for Claude, Codex, and Claude Code.

Developer Details

Author

DMJGilbert

License

MIT

Skillstore revision

Version notice

The author did not declare a version.

Repository

https://github.com/DMJGilbert/.config/tree/main/users/darren/config/claude/skills/test-driven-development

Ref

72d5025b022c77f7a51bdf5c1637c689c80e89d1

Maintenance freshness

7/18/2026

Usage

4 downloads · 213 views

File structure

📄 SKILL.md