Superpowers Tdd
v1.0.0Enforces strict RED-GREEN-REFACTOR TDD cycle by writing failing real-code tests before implementation, verifying failures, coding minimally, then refactoring...
⭐ 0· 154·1 current·1 all-time
by@axelhu
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description promise (enforce RED-GREEN-REFACTOR TDD) directly matches the SKILL.md instructions, which are focused on writing tests, running pytest, implementing minimal code, and refactoring. No unrelated credentials, binaries, or installs are requested.
Instruction Scope
Instructions stay within TDD workflow (writing tests, running pytest, editing code). However the guidance is prescriptive about deleting existing code if tests were written after implementation — this is potentially destructive for a user's repository if followed blindly. The skill tells the agent to run pytest and modify/delete code, which is expected for a TDD tutor but has real-world side effects.
Install Mechanism
No install spec and no code files — lowest-risk instruction-only skill. There is nothing downloaded or written to disk by the skill itself.
Credentials
The skill declares no environment variables, no credentials, and no config paths. The runtime instructions reference only typical developer tools (pytest) and project files; nothing asks for unrelated secrets or access.
Persistence & Privilege
always:false (no forced presence). The skill can be invoked autonomously by the agent (platform default). Because the instructions include modifying/deleting project code, granting the agent file-system or repo write access could be risky — exercise the usual caution when allowing autonomous actions.
Assessment
This skill is coherent for a strict TDD coach — it tells an agent to write failing tests, run pytest, implement minimal code, and refactor. Before you use or let an agent run this skill: (1) ensure your project is under version control and committed (or work in a disposable branch) so 'delete code' guidance can't cause data loss; (2) confirm the correct test command (pytest or project-specific) and that the runtime environment has necessary tooling; (3) if you allow autonomous agent actions, restrict write permissions or require manual approval for file modifications; (4) be aware the skill is dogmatic — it may insist on deleting code or restarting work if its TDD rules detect violations. If these precautions are acceptable, the skill is internally consistent with its stated purpose.Like a lobster shell, security has layers — review code before you run it.
latestvk971ay9qscehc4r664mtan4s2x83mmd8
License
MIT-0
Free to use, modify, and redistribute. No attribution required.