tdd-enforcer
Enforce Test-Driven Development Workflows
Teams often skip tests or write them after implementation. This skill guides Claude, Codex, and Claude Code through test-first delivery.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "tdd-enforcer" from https://skillstore.io/skills/barnhardt-enterprises-inc-tdd-enforcer.md and its manifest at https://skillstore.io/api/skills/barnhardt-enterprises-inc-tdd-enforcer/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-enforcer". Add password reset support to an authentication service.
Expected outcome:
- A failing service test defines token creation and password update behavior.
- An API route test checks success and invalid token responses.
- Implementation is limited to code required for those tests.
Using "tdd-enforcer". Review tests for a login form before implementation.
Expected outcome:
- The review flags vague test names and missing loading state coverage.
- It recommends user-visible assertions instead of internal state checks.
Using "tdd-enforcer". Refactor a utility without changing behavior.
Expected outcome:
- The workflow keeps the existing tests as the safety net.
- New edge case tests are added before simplifying the utility.
Security Audit
SafeAll static findings are false positives caused by markdown code fences, local test commands, localhost test URLs, and sample test text. No prompt injection, data exfiltration, arbitrary command construction, or malicious intent was found in SKILL.md.
Risk Factors
โ๏ธ External commands (34)
๐ Network access (2)
๐ Filesystem access (1)
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/barnhardt-enterprises-inc-tdd-enforcer/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/barnhardt-enterprises-inc-tdd-enforcer?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/barnhardt-enterprises-inc-tdd-enforcer?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/barnhardt-enterprises-inc-tdd-enforcer/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/barnhardt-enterprises-inc-tdd-enforcer.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
Barnhardt-Enterprises-Inc. (2026). tdd-enforcer security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/barnhardt-enterprises-inc-tdd-enforcer/audits/8BibTeX citation
@techreport{barnhardt-enterprises-inc-barnhardt-enterprises-inc-tdd-enforcer-2026,
author = {Barnhardt-Enterprises-Inc},
title = {tdd-enforcer security audit report (audit version 8)},
institution = {Skillstore},
year = {2026},
number = {8},
url = {https://skillstore.io/skills/barnhardt-enterprises-inc-tdd-enforcer/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: "tdd-enforcer security audit report (audit version 8)"
version: "unspecified"
type: report
authors:
- name: "Barnhardt-Enterprises-Inc"
date-released: "2026-07-05"
url: "https://skillstore.io/skills/barnhardt-enterprises-inc-tdd-enforcer/audits/8"
identifiers:
- type: other
value: "skillstore:barnhardt-enterprises-inc-tdd-enforcer:audit:8"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Build A New Feature
Create failing tests that define expected behavior before implementation starts.
Improve Test Quality
Review tests for clear names, AAA structure, edge cases, and behavior-focused assertions.
Refactor With Confidence
Keep tests green while simplifying code and preserving existing behavior.
Try These Prompts
Use the tdd-enforcer workflow for this feature: [feature]. First write failing tests with AAA. Then implement only enough code to pass.
Use tdd-enforcer for this bug: [bug]. Write a failing regression test first. Then fix the issue and keep existing tests green.
Review my planned tests for [change]. Check AAA structure, behavior focus, edge cases, and expected initial failures before implementation.
Create a TDD plan for [feature]. Cover unit, integration, component, and E2E tests. Include coverage targets and the red-green-refactor sequence.
Best Practices
- Write the failing test before changing production code.
- Use clear Arrange, Act, Assert sections in each test.
- Run the full relevant test suite after refactoring.
Avoid
- Do not write implementation first and backfill tests later.
- Do not test private implementation details when behavior is observable.
- Do not combine many unrelated behaviors into one large test.
Frequently Asked Questions
What does this skill enforce?
Does it work with Claude, Codex, and Claude Code?
Can it run tests for me?
Does it require TypeScript?
What test styles does it cover?
Does it guarantee high coverage?
Developer Details
Author
Barnhardt-Enterprises-IncLicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Repository
https://github.com/Barnhardt-Enterprises-Inc/quetrex-plugin/tree/main/templates/skills/tdd-enforcerRef
5ab1d37e83436c6eef84de88573e142b94f2a4ad
Maintenance freshness
7/18/2026
Usage
7 downloads ยท 257 views
File structure
๐ SKILL.md