Skills tdd
๐Ÿ“ฆ

tdd

Content revision r1 Safe โš™๏ธ External commands๐ŸŒ Network access๐Ÿ”‘ Env variables

Build Software with Test-Driven Development

Feature work often produces fragile tests that mirror implementation details. This skill guides focused red-green-refactor cycles around observable behavior and public interfaces.

Supports: Claude Codex Code(CC)
๐Ÿฅ‰ 78 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 "tdd" from https://skillstore.io/skills/brianlovin-tdd.md and its manifest at https://skillstore.io/api/skills/brianlovin-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 coupon support to checkout using TDD.

Expected outcome:

  • Public behavior: a valid coupon reduces the checkout total.
  • First red step: add one checkout test for a valid fixed discount.
  • Green step: implement only the discount needed for that case.
  • Next cycle: cover invalid, expired, and percentage coupons separately.

Using "tdd". Fix duplicate welcome emails after user registration.

Expected outcome:

  • Reproduce the duplicate through the registration interface.
  • Assert one observable email delivery for one successful registration.
  • Apply the smallest correction, rerun tests, then inspect duplication.

Using "tdd". Review tests that mock every service method.

Expected outcome:

The suite is coupled to call structure. Keep mocks at external boundaries and verify results through the module's public interface.

Security Audit

Safe
v1 โ€ข 8/21/2026 Open versioned report

All 21 static alerts are false positives caused by inert Markdown examples, code fences, template literals, or unrelated prose. No executable scripts, malicious intent, credential exposure, prompt injection, or unauthorized network behavior were found.

6
Files scanned
307
Lines analyzed
0
Review items
0
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
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
Security Assessment

Copy report link

https://skillstore.io/skills/brianlovin-tdd/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/brianlovin-tdd/security.svg)](https://skillstore.io/skills/brianlovin-tdd?utm_source=security_passport_badge)

HTML badge

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

Embed card

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

brianlovin. (2026). tdd security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/brianlovin-tdd/audits/1

BibTeX citation

@techreport{brianlovin-brianlovin-tdd-2026, author = {brianlovin}, title = {tdd security audit report (audit version 1)}, institution = {Skillstore}, year = {2026}, number = {1}, url = {https://skillstore.io/skills/brianlovin-tdd/audits/1}, 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 1)" version: "unspecified" type: report authors: - name: "brianlovin" date-released: "2026-08-21" url: "https://skillstore.io/skills/brianlovin-tdd/audits/1" identifiers: - type: other value: "skillstore:brianlovin-tdd:audit:1" description: "Skillstore immutable audit report identifier"

Compare variants

3 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
mattpocock Recommended

mattpocock-tdd

Skillstore Score 80
Evidence Confidence High
Skillstore usage 13
Updated

2026-08-21

benny9193-tdd

Skillstore Score 79
Evidence Confidence High
Skillstore usage 10
Updated

2026-08-21

brianlovin Current

brianlovin-tdd

Skillstore Score 78
Evidence Confidence Medium
Skillstore usage Unknown
Updated

2026-08-21

Skillstore Score

Why this score Evidence Confidence: Medium
55
Architecture
85
Maintainability
87
Content
65
Community
91
Spec Compliance

What You Can Build

Develop a New Feature

Turn a requested capability into small behavior slices, then implement each slice through a red-green-refactor cycle.

Repair a Regression

Reproduce a reported defect with a failing public-interface test before applying the smallest effective correction.

Improve a Test Suite

Replace brittle implementation-detail tests with durable checks of observable behavior and system boundaries.

Try These Prompts

Start a TDD Feature
Use TDD to add [feature]. First identify the public interface and the single most important observable behavior.
Fix a Bug Test First
Fix [bug] with TDD. Reproduce it through the public interface, make the test fail, then implement the minimal correction.
Review Test Quality
Review tests for [module]. Identify implementation coupling, unnecessary internal mocks, and missing behavior coverage. Propose focused replacements in priority order.
Design a Testable Interface
Design a testable interface for [capability]. Minimize surface area, inject external dependencies, define behavior slices, and plan incremental red-green-refactor cycles.

Best Practices

  • Agree on the public interface and highest-priority behavior before writing code.
  • Complete one failing test and minimal implementation before starting another behavior.
  • Refactor only after tests pass, and rerun them after each structural change.

Avoid

  • Do not write the complete test suite before implementing any behavior.
  • Do not mock internal collaborators or assert private call sequences.
  • Do not add speculative production code beyond the current failing test.

Frequently Asked Questions

What development loop does this skill use?
It uses repeated red-green-refactor cycles, with one behavior test and one minimal implementation per cycle.
Does it prefer unit or integration tests?
It prefers integration-style tests through public interfaces while keeping each test focused on one logical behavior.
When should dependencies be mocked?
Mock external boundaries such as payment APIs, email services, time, or files when real dependencies are impractical.
Can it help fix existing bugs?
Yes. It first captures the defect with a failing behavior test, then guides the smallest correction.
When should refactoring begin?
Refactor after the relevant tests pass. Run the suite after each structural change.
Does it choose which behaviors matter most?
It helps identify behaviors, but the user must confirm priorities, interfaces, and acceptable coverage.

Developer Details

Author

brianlovin

License

MIT

Skillstore revision

r1

Version notice

The author did not declare a version.

Ref

6b4c2c37d714f625bf5f1482f739feeb23554773

Maintenance freshness

8/21/2026

Usage

0 downloads ยท 0 views

File structure

๐Ÿ“„ deep-modules.md

๐Ÿ“„ interface-design.md

๐Ÿ“„ mocking.md

๐Ÿ“„ refactoring.md

๐Ÿ“„ SKILL.md

๐Ÿ“„ tests.md

More from brianlovin

View all
View all