dralgorhythm/claude-agentic-framework64 installs
test-driven-development
Write tests before implementation code. Use when starting new features or fixing bugs. Covers Red-Green-Refactor cycle and TDD best practices.
How do I install this agent skill?
npx skills add https://github.com/dralgorhythm/claude-agentic-framework --skill test-driven-developmentIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The skill provides educational guidelines for Test-Driven Development (TDD) and does not contain any malicious patterns or security risks.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
- Runlayerpass
1 file scanned · No issues
What does this agent skill do?
Test-Driven Development
The TDD Cycle
- Red: Write a failing test
- Green: Write minimal code to pass
- Refactor: Improve code while keeping tests green
Workflows
- Write Test: Write a test that describes desired behavior
- Run Test: Verify it fails (Red)
- Implement: Write minimal code to pass
- Run Test: Verify it passes (Green)
- Refactor: Clean up while tests stay green
- Repeat: Next test case
TDD Example
Step 1: Red - Write Failing Test
describe("Calculator", () => {
test("adds two numbers", () => {
const calc = new Calculator();
expect(calc.add(2, 3)).toBe(5);
});
});
// Run: FAIL - Calculator is not defined
Step 2: Green - Minimal Implementation
class Calculator {
add(a: number, b: number): number {
return a + b;
}
}
// Run: PASS
Step 3: Refactor (if needed)
Code is already clean, move to next test.
Step 4: Next Test
test("subtracts two numbers", () => {
const calc = new Calculator();
expect(calc.subtract(5, 3)).toBe(2);
});
// Run: FAIL - subtract is not defined
TDD Benefits
- Design Feedback: Tests reveal design issues early
- Documentation: Tests document expected behavior
- Confidence: Refactor fearlessly with test safety net
- Focus: One behavior at a time
TDD Tips
- Start Simple: Begin with the simplest test case
- One Assert: Each test should verify one behavior
- Descriptive Names: Test names are documentation
- No Logic in Tests: Tests should be obvious
- Fast Feedback: Tests should run in milliseconds
When to Use TDD
- New features with clear requirements
- Bug fixes (write failing test first)
- Complex business logic
- API contract development
When TDD is Less Useful
- Exploratory/prototype code
- UI layout changes
- Simple CRUD operations
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/dralgorhythm/claude-agentic-framework/test-driven-development">View test-driven-development on skillZs</a>