test-driven-development

What This Skill Does

The test-driven-development skill is a unified framework designed to enforce rigorous software engineering practices within the OpenClaw ecosystem. By mandating a Red-Green-Refactor workflow, it ensures that your codebase grows intentionally and defect-free. The skill intelligently detects your entry point—whether it is a formal .spec.md file, a specific .code-task.md document, or a simple ad-hoc feature description—and adapts its strategy accordingly. It emphasizes pattern discovery by analyzing existing repository conventions before writing a single line of test code, ensuring that new tests feel like native components of your project.

Installation

To integrate this skill into your OpenClaw environment, execute the following command in your terminal: clawhub install openclaw/skills/skills/imbeasting/imbeasting-test-driven-development Ensure your local environment is configured to access the openclaw/skills repository.

Use Cases

• Formal Specification Fulfillment: Ideal for projects following strict TDD where acceptance criteria are predefined in Markdown documentation.
• Refactoring Legacy Code: Use the test-first approach to lock down current behavior with safety nets before modifying or optimizing existing modules.
• Rapid Feature Development: Perfect for developers who need to implement new logic while maintaining high coverage, ensuring that edge cases are accounted for through systematic test generation.
• Proptest Implementation: Automatically identify functions suitable for property-based testing to verify complex input spaces that unit tests might miss.

Example Prompts

1. "Apply TDD to the authentication module using the requirements defined in ./specs/auth.spec.md."
2. "Implement a new rate-limiting feature based on the task description in ./tasks/rate-limit.code-task.md; follow the project's existing test patterns."
3. "Refactor the currency converter logic. I've described the goal here: [insert description]; please generate the failing tests first."

Tips & Limitations

• Pattern Discovery: Always allow the skill to search your repository for existing test helpers. Matching the local style leads to better PR reviews and easier maintenance.
• Proptest Constraints: Only enable proptest for pure, deterministic functions. Attempting to use property-based testing on I/O-bound code will result in test flakiness.
• Red-Green-Refactor: Never skip the RED phase. If your test passes before you have written the implementation code, verify your test logic; it is likely incorrectly asserting behavior.