tdd
Apply Test-Driven Development to Every Change
Software changes often grow before their expected behavior is verified. This skill guides Claude, Codex, and Claude Code through focused Red-Green-Refactor cycles.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "tdd" from https://skillstore.io/skills/benny9193-tdd.md and its manifest at https://skillstore.io/api/skills/benny9193-tdd/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.
Test it
Using "tdd". Add support for an empty shopping cart total.
Expected outcome:
- Red: Add one test expecting an empty cart total of zero.
- Green: Return zero for the empty-cart case.
- Refactor: Remove duplication only after the test passes.
Using "tdd". Fix duplicate email registration.
Expected outcome:
First add a regression test proving that an existing email is rejected. Then make the smallest validation change and rerun all tests.
Using "tdd". Plan TDD for a username formatter.
Expected outcome:
- Start with lowercasing one simple username.
- Add whitespace handling only after the first test passes.
- Add punctuation and empty-input cases in later cycles.
Security Audit
SafeAll 18 static findings are false positives caused by Markdown code formatting or ordinary TDD guidance. The skill contains no shell execution, network reconnaissance, data exfiltration, or prompt injection instructions.
Risk Factors
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.
Copy report link
https://skillstore.io/skills/benny9193-tdd/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/benny9193-tdd?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/benny9193-tdd?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/benny9193-tdd/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/benny9193-tdd.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
Benny9193. (2026). tdd security audit report (audit version 9) [Author version unspecified]. Skillstore. https://skillstore.io/skills/benny9193-tdd/audits/9BibTeX citation
@techreport{benny9193-benny9193-tdd-2026,
author = {Benny9193},
title = {tdd security audit report (audit version 9)},
institution = {Skillstore},
year = {2026},
number = {9},
url = {https://skillstore.io/skills/benny9193-tdd/audits/9},
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: "tdd security audit report (audit version 9)"
version: "unspecified"
type: report
authors:
- name: "Benny9193"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/benny9193-tdd/audits/9"
identifiers:
- type: other
value: "skillstore:benny9193-tdd:audit:9"
description: "Skillstore immutable audit report identifier"
Compare variants
3 installable variantsEach author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
mattpocock-tdd
2026-09-09
benny9193-tdd
2026-09-09
brianlovin-tdd
2026-09-09
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Build a Small Feature
Turn one behavior into a failing test, minimal implementation, and focused refactoring.
Fix a Reproducible Defect
Capture a defect with a failing regression test before changing production behavior.
Teach Incremental Design
Demonstrate how successive tests drive a general solution from a simple starting point.
Try These Prompts
Use TDD to add [behavior]. First write one focused test, explain the expected failure, then implement only enough to pass.
Reproduce [bug] with one failing regression test. Confirm why it fails, apply the smallest fix, then suggest a focused refactor.
List the behaviors for [feature] from simplest to most complex. Begin the first Red-Green-Refactor cycle and stop after one passing test.
Review [module] and its tests. Identify observable behavior, add characterization tests incrementally, and refactor only while all tests remain green.
Best Practices
- Confirm each new test fails for the expected reason.
- Change one behavior at a time and keep feedback cycles short.
- Refactor only with a passing test suite.
Avoid
- Do not write production behavior before observing a failing test.
- Do not add many tests before making the first test pass.
- Do not assert private implementation details when public behavior is available.