Hyper Tdd
Use when about to write or modify behavior-bearing code — functions, business logic, bug fixes — before writing any production code. Also when the user invokes /hyperclaude:hyper-tdd. Forces a failing test first so you watch it fail for the right reason.
Install
$ agentstack add skill-zeikar-hyperclaude-hyper-tdd ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
hyper-tdd
Test-driven discipline tailored to this author's preferences.
The loop
- Write the failing test first. Name the behavior, not the implementation. The test should compile/import but fail because the behavior doesn't exist yet.
- Run it. Confirm it fails for the right reason. "Cannot find function" is fine. "ReferenceError because of typo in test" is not — fix the test.
- Write the minimum code to make it pass. Resist scope creep. No "while I'm here" edits.
- Run it. Confirm it passes.
- Commit. One behavior, one commit. Commit messages describe the behavior, not the code.
- Refactor if there's a clear smell. Tests must still pass after.
Skip TDD when
- Touching only documentation, comments, or formatting.
- Renaming a symbol (an LSP/grep operation, not a behavior change).
- One-shot migration scripts that run once and get deleted.
- Config-only changes (e.g., updating a
.gitignore).
What "minimum" means here
Implement only what the current test requires. If you need a helper, add the simplest version. Do not pre-build for tests you might write later — write that test first, then the helper.
What good test names look like
- ✅
slugify drops non-ASCII characters - ✅
cli --dry-run prints JSON without spawning codex - ❌
test_slugify(says nothing) - ❌
slugify works correctly(vague)
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: zeikar
- Source: zeikar/hyperclaude
- License: MIT
- Homepage: http://zeikar.dev/hyperclaude/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.