test-driven-development Skill
TDD: enforce RED-GREEN-REFACTOR, tests before code. Published by NousResearch in hermes-agent.
Decision snapshot
Is this a fit?
Testing, Writing, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
5 days ago · MIT license
No specific cautions were detected. Review the source and requested permissions before installing.
What is test-driven-development Skill?
TDD: enforce RED-GREEN-REFACTOR, tests before code. Published by NousResearch in hermes-agent. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Testing
- Writing
- Testing use cases
- Writing use cases
Declared skill metadata
- Declared author: Hermes Agent (adapted from obra/superpowers)
- Declared license: MIT
- Source file: skills/software-development/test-driven-development/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use test-driven-development Skill
- Use it for testing.
- Use it for writing.
Built with
Editorial notes
Source
- Creator: NousResearch
- Repository: NousResearch/hermes-agent
- Skill file: skills/software-development/test-driven-development/SKILL.md
What it does
TDD: enforce RED-GREEN-REFACTOR, tests before code.
Skill instructions
Test-Driven Development (TDD) Overview Write the test first. Watch it fail. Write minimal code to pass. Core principle: If you didn't watch the test fail, you don't know if it tests the right thing. Violating the letter of the rules is violating the spirit of the rules. When to Use Always: - New features - Bug fixes - Refactoring - Behavior changes Exceptions (ask the user first): - Throwaway prototypes - Generated code - Configuration files Thinking "skip TDD just this once"? Stop. That's rationalization. The Iron Law NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST Write code before the test? Delete it. Start over. No exceptions: - Don't keep it as "reference" - Don't "adapt" it while writing tests - Don't look at it - Delete means delete Implement fresh from tests. Period. Red-Green-Refactor Cycle RED — Write Failing Test Write one minimal test showing what should happen. Good test: python def testretriesfailedoperations3times(): attempts = 0 def operation(): nonlocal attempts attemp
Verified compatibility and discovery
Frequently asked questions
What is test-driven-development?
test-driven-development is a open-source AI agent skill with Copy skill directory. TDD: enforce RED-GREEN-REFACTOR, tests before code.
Who is test-driven-development best for?
test-driven-development is best for reusing agent instructions, scripts, and references, testing workflows, writing workflows.
How do I install test-driven-development?
Install or run test-driven-development using Copy skill directory. Check test-driven-development for the latest setup command.
Is test-driven-development actively maintained?
test-driven-development may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
