lemessdavi/test-driven-development
skills/test-driven-development/SKILL.md
Use before any feature, bugfix, or behavior change. Write failing tests first, then implement minimum code.
development
Updated Apr 16, 2026
$ install --global
skillsauthnpx skillsauth add lemessdavi/ia-prev test-driven-developmentInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 5:34 PM8.0s1 file scanned
SKILL.md
- name:
- test-driven-development
- description:
- Use before any feature, bugfix, or behavior change. Write failing tests first, then implement minimum code.
Test-Driven Development
Iron Rule
No production code without a failing test first.
Cycle
- Red: write one failing test for one behavior.
- Verify Red: run the test and confirm expected failure.
- Green: implement minimal code to pass.
- Verify Green: run targeted and related tests.
- Refactor: clean structure without changing behavior.
Constraints
- Do not bundle multiple behaviors in one test.
- Do not refactor while still red.
- Do not skip failure verification.
Done Criteria
- New/changed behavior is covered by tests.
- Regression risk is guarded by automated tests.
Related Skills
lemessdavi/xp-delivery-loop
testing
VerifiedTrustedCommunity
Use for every implementation task in this template. Enforces pair-programming with AI, small releases, and continuous integration discipline.
SKILL.mdUpdated Apr 16, 2026
lemessdavi/refactor-continuous
development
VerifiedTrustedCommunity
Use after green tests to keep codebase healthy through small and frequent refactors instead of large rescue rewrites.
SKILL.mdUpdated Apr 16, 2026
lemessdavi/linear-delivery-sync
tools
VerifiedTrustedCommunity
Use the Linear MCP from the scaffolded Linear link to align implementation with issues/projects, suggest card updates, and keep Linear documentation in sync.
SKILL.mdUpdated Apr 16, 2026
lemessdavi/docs-living-spec
testing
VerifiedTrustedCommunity
Keep CLAUDE.md and AGENTS.md aligned with reality. Use when new decisions, hurdles, or patterns emerge during implementation.
SKILL.mdUpdated Apr 16, 2026