6bnbn/test-driven-development
兼容codex@cursor一键安装技能/cursor一键安装技能/-Force/skills/test-driven-development/SKILL.md
Use when implementing a feature, fixing a bug, or changing behavior in Cursor and you want a disciplined red-green-refactor workflow.
$ install --global
skillsauthnpx skillsauth add 6bnbn/flowpilot 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%
Error
VirusTotalMulti-engine malware detection
70%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Mar 25, 2026, 7:14 PM44.1s2 files scanned
SKILL.md
- name:
- test-driven-development
- description:
- Use when implementing a feature, fixing a bug, or changing behavior in Cursor and you want a disciplined red-green-refactor workflow.
Test-Driven Development
Goal
Write the failing test first, then the smallest implementation that makes it pass.
Workflow
- Write one failing test for one behavior.
- Run it and confirm it fails for the right reason.
- Implement the minimal code needed to pass.
- Re-run the test and nearby checks.
- Refactor while keeping everything green.
- Repeat for the next behavior.
Rules
- No production code before a failing test unless the user explicitly asks to skip TDD.
- Keep tests focused on behavior, not incidental implementation details.
- Prefer real code paths over heavy mocking.
- If the test passes immediately, you are probably testing existing behavior or the wrong thing.
- Use
verification-before-completionbefore claiming the bug or feature is finished.
Good Test Qualities
- one behavior
- clear name
- obvious expected outcome
- minimal setup
- catches the intended regression
Related Skills
6bnbn/writing-skills
testing
VerifiedTrustedCommunity
Use when creating, editing, or validating Cursor custom skills, especially when deciding where they should live, how they should be named, and how to describe when they apply.
128SKILL.mdUpdated May 2, 2026
6bnbn/writing-plans
development
VerifiedTrustedCommunity
Use when the user wants a written implementation plan in Cursor before editing code, especially for multi-step tasks or changes touching several files.
128SKILL.mdUpdated May 2, 2026
6bnbn/verification-before-completion
development
VerifiedTrustedCommunity
Use before claiming work is complete, fixed, or passing in Cursor. Requires fresh verification evidence such as tests, builds, lint output, or direct reproduction checks.
128SKILL.mdUpdated May 2, 2026
6bnbn/using-superpowers
testing
VerifiedTrustedCommunity
Use when starting a task in Cursor and deciding whether to apply one of the companion skills in this pack before exploring, planning, editing, or reviewing.
128SKILL.mdUpdated May 2, 2026