dmitryprg-ai/tdd-workflow
.claude/skills/tdd-workflow/SKILL.md
Test-Driven Development with strict Red-Green-Refactor cycle. Use when developing with TDD, writing tests before code, adding test coverage, or when user mentions test-first, red-green-refactor, or wants reliable test suites.
$ install --global
skillsauthnpx skillsauth add dmitryprg-ai/cursor-develop-autorules tdd-workflowInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 17, 2026, 2:10 AM8.9s2 files scanned
SKILL.md
- name:
- tdd-workflow
- description:
- Test-Driven Development with strict Red-Green-Refactor cycle. Use when developing with TDD, writing tests before code, adding test coverage, or when user mentions test-first, red-green-refactor, or wants reliable test suites.
- allowed-tools:
- Read, Write, Bash, Grep, Glob
- model:
- sonnet
- user-invocable:
- true
TDD Workflow
Principle: Red -> Green -> Refactor (strict order)
Writing tests first catches design issues early — if the API is awkward to test, it's awkward to use. Tests also serve as living documentation that stays current because it breaks when behavior changes.
Phase 0: Test Planning (before any code)
Fill the test cases table first because it forces you to think about behavior before implementation. Without this step, tests end up only covering the happy path.
| # | Scenario | Input | Expected Output | Type |
|---|----------|-------|-----------------|------|
| 1 | Happy path | ... | ... | Unit |
| 2 | Edge: empty | [] | ... | Unit |
| 3 | Edge: null | null | Error | Unit |
| 4 | Integration | ... | ... | Integration |
Coverage categories:
- Happy path (main scenario)
- Edge cases (empty, null, boundaries)
- Error cases (invalid input, exceptions)
- Integration points (if dependencies exist)
Do NOT proceed until the table is filled — skipping this step leads to incomplete test coverage that gives false confidence.
Phase 1: RED — Write Failing Tests
- Create test file (
feature.test.ts) - Write tests for ALL cases from Phase 0
- Run tests — they must fail
npm test -- --grep "feature"
# Expected: FAIL
Tests must fail first because a test that passes without implementation might be testing the wrong thing.
Phase 2: GREEN — Minimal Code
- Write the minimum code to make tests pass
- Resist the urge to optimize or add "for later" — that's Phase 3
- Run tests — they must pass
npm test -- --grep "feature"
# Expected: PASS
Phase 3: REFACTOR
- All tests green? Now refactor
- After each change: run tests (must stay green)
Refactoring with a green test suite is safe. Refactoring without tests is gambling.
Phase 4: Verify
| Category | Written | Passing | Skipped |
|----------|---------|---------|---------|
| Happy path | X | X | 0 |
| Edge cases | X | X | 0 |
| Error cases | X | X | 0 |
| Integration | X | X | 0 |
What to avoid
- Code before test table — leads to incomplete coverage
- Code before failing tests — the test might be wrong
- Refactoring while tests are red — you don't know if refactoring broke something or if it was already broken
- "I'll write tests later" — later never comes, and by then you've forgotten the edge cases
Related Skills
dmitryprg-ai/techdebt-scan
development
VerifiedTrustedCommunity
Scan codebase for technical debt and fix safely with TDD. Use to find oversized files, duplicated code, code smells, and refactor safely. Workflow - SCAN, TEST CASES, REFACTOR, VERIFY. Keywords - techdebt, tech debt, duplicates, code quality audit.
8SKILL.mdUpdated Apr 17, 2026
dmitryprg-ai/tdd-workflow
development
VerifiedTrustedCommunity
Test-Driven Development workflow with strict Red-Green-Refactor cycle. Use when developing features with TDD, writing tests before code, or when test-driven approach is needed. MANDATORY order - test cases table BEFORE code, failing tests BEFORE implementation.
8SKILL.mdUpdated Apr 17, 2026
dmitryprg-ai/session-review
testing
VerifiedTrustedCommunity
Review work session quality and capture improvements. Use at end of session, after large tasks, after series of errors, or when user asks for session review, retrospective, lessons learned. Records improvements to backlog.
8SKILL.mdUpdated Apr 17, 2026
dmitryprg-ai/research
data-ai
VerifiedTrustedCommunity
Analyze data, investigate datasets, work with CSV/parquet/pandas/dataframes. Use when analyzing data, exploring datasets, running experiments, or when user mentions data, analysis, parquet, csv, pandas, dataframe, statistics, investigation.
8SKILL.mdUpdated Apr 17, 2026