Is test-driven-development safe?
Grade A, 100/100. No meaningful risk found.
Use when implementing any feature or bugfix, before writing implementation code
Atest-driven-development
skills/test-driven-development100/100 · No meaningful risk foundNo security findings
test-driven-development
skills/test-driven-developmentUse when implementing any feature or bugfix, before writing implementation code
- Content hash
- sha256:acf361b1743f444028ed8123f1ccf2df6e1d4dcca65b3f982aedb42f4f68ec44
- Files
- 2
- Quality
- 100/100
Security findings
None of the 30 rules matched.
Files in this skill
- SKILL.md9.4 KB
- writing-good-tests.md8.1 KB
Questions about test-driven-development
- Is test-driven-development safe to install?
- Our scanner gave test-driven-development grade A (100/100): no meaningful risk found. None of the 30 security rules matched. Static analysis cannot prove safety, so pin the reviewed revision with a lockfile.
- How do I install test-driven-development in Claude Code or Codex?
- Run skillhash add github:obra/superpowers/skills/test-driven-development. It downloads the exact commit, checks the grade against your policy, writes skills.lock and installs it into .claude/skills and .agents/skills.
- What happens if test-driven-development changes upstream?
- Its content hash changes. skillhash verify fails in CI until you review the new version and update the lock. With a watch, you also get an alert.
More from obra/superpowers
- A
writing-skills
302kobra/superpowers
Use when creating new skills, editing existing skills, or verifying skills work before deployment
No security findings - A
writing-plans
302kobra/superpowers
Use when you have a spec or requirements for a multi-step task, before touching code
No security findings - A
requesting-code-review
302kobra/superpowers
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
No security findings - A
diagnosing-superpowers
302kobra/superpowers
Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.
No security findings - A
dispatching-parallel-agents
302kobra/superpowers
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
No security findings - A
executing-plans
302kobra/superpowers
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
No security findings - A
finishing-a-development-branch
302kobra/superpowers
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work
No security findings - A
receiving-code-review
302kobra/superpowers
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
No security findings