smithery/mizkun

vibeflow-tdd

Execute TDD Red-Green-Refactor cycle. Use when implementing features with test-driven development.

Installation

$ npx skills add smithery/mizkun --skill vibeflow-tdd

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,369 B
  • docs SUMMARY.md 118 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

VibeFlow TDD Cycle

When to Use

  • When implementing new features
  • When fixing bugs with regression tests
  • When refactoring with test coverage

The Red-Green-Refactor Cycle

Phase 1: Red (Write Failing Tests)

Goal: Define expected behavior through tests that don't pass yet.

  1. Read the issue file and acceptance criteria
  2. Create test files:

- Unit tests: tests/ or src/**/tests/ - Integration tests: tests/integration/ - E2E tests: e2e/ or tests/e2e/

  1. Write tests that define expected behavior
  2. Run tests and confirm they fail (RED)
  3. Commit: test: Add failing tests for <feature>

Checklist:

  • Tests cover all acceptance criteria
  • Tests cover edge cases
  • Tests are independent (no shared state)
  • Test names are descriptive

Phase 2: Green (Make Tests Pass)

Goal: Write minimal code to pass all tests.

  1. Write the simplest code that makes tests pass
  2. Run tests after each small change
  3. Do NOT over-engineer at this stage
  4. Do NOT add features not covered by tests
  5. Commit: feat: Implement <feature>

Checklist:

  • All tests pass (GREEN)
  • No new tests added in this phase
  • Implementation is minimal

Phase 3: Refactor (Improve Code Quality)

Goal: Improve code structure while keeping tests green.

  1. Identify code smells:

- Duplication - Long functions - Poor naming - Missing abstractions

  1. Make one refactoring change at a time
  2. Run tests after EVERY change
  3. Keep tests GREEN throughout
  4. Commit: refactor: Improve <feature> code structure

Checklist:

  • All tests still pass
  • Code is DRY (Don't Repeat Yourself)
  • Functions are small and focused
  • Names are clear and descriptive
  • No dead code

Common Test Patterns

Unit Test Pattern

describe('<Component/Function>', () => {
  it('should <expected behavior> when <condition>', () => {
    // Arrange
    // Act
    // Assert
  });
});

Edge Cases to Consider

  • Empty inputs
  • Null/undefined values
  • Boundary values
  • Error conditions
  • Concurrent operations

Examples

  • "Implement user login with TDD"
  • "Add validation with TDD cycle"
  • "Refactor payment module keeping tests green"