Loading...
Loading...
Found 147 Skills
Test-driven development using Red-Green-Refactor for bug fixes, new features, and regression prevention. Writes a failing test first to prove a defect or define behavior, then implements minimal code to pass, then refactors. Use when fixing bugs, encountering failing behavior, adding new features, writing tests, or when the user mentions TDD, red-green-refactor, regression test, failing test, test first, or test-driven.
ping-pong TDD 세션의 마지막 단계입니다. .tdd-sessions/에서 활성 세션 파일을 읽어 완료된 태스크를 요약하고, Conventional Commits 메시지를 제안하며, 커밋을 실행하고 세션 파일을 정리합니다. 모든 /tdd-task 호출이 완료된 후 실행합니다.
Use when debugging bugs, test failures, build failures, performance regressions, or unexpected behavior and you need root-cause investigation before proposing fixes. Trigger on requests to debug, investigate why something broke, or find the source of a technical issue.
Guide for creating effective skills. This command should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations. Use when creating new skills, editing existing skills, or verifying skills work before deployment - applies TDD to process documentation by testing with subagents before writing, iterating until bulletproof against rationalization
Android Test-Driven Development standards. Enforces Red-Green-Refactor cycle, test pyramid (70/20/10), layer-specific testing strategies, and CI integration. Use when building or reviewing Android apps with TDD methodology.
Test-driven development methodology — red-green-refactor cycle, writing failing tests first, minimal implementation, and iterative refinement. Use when implementing features test-first, when the user asks for TDD, or when writing tests before code.
Strict Red-Green-Refactor workflow for robust, self-documenting code. Discovers project test setup via codebase exploration before assuming frameworks. Use when: (1) Implementing new features with test-first approach, (2) Fixing bugs with reproduction tests, (3) Refactoring existing code with test safety net, (4) Adding tests to legacy code, (5) Ensuring code quality before committing, (6) When tests exist but workflow unclear, or (7) When establishing testing practices in a new project. Triggers: test, tdd, red-green-refactor, failing test, test first, test-driven, write tests, add tests, run tests.
단일 태스크의 RED-GREEN-REFACTOR TDD 루프를 ping-pong 방식으로 실행합니다. .tdd-sessions/에서 활성 세션 파일을 읽어 현재 태스크를 찾고, 개발자와 함께 전체 사이클을 진행하며 (테스트 작성과 구현을 번갈아가며), 완료 시 세션 파일을 업데이트합니다. 세션 파일을 생성하려면 먼저 /tdd-plan을 실행하세요.
Use when implementing a Beat change — requires gherkin or proposal artifact to be done first
Structured TDD workflow that decomposes features into small specs and implements them one at a time through the strict red/green/refactor cycle. Use this skill whenever the user wants to build, implement, or fix something using TDD, test-driven development, or a test-first approach. Also trigger when the user says "red green refactor", "write tests first", "one test at a time", "failing test first", or asks to develop something incrementally with tests driving the design. Even if the user just says "use TDD" or "do it test-driven" alongside a feature request, this skill applies. Do NOT trigger for: running existing tests, adding tests after the fact to untested code, fixing a single failing test, or test infrastructure setup.
Test-driven development workflow — write failing tests first, implement minimum code, run full suite, commit. Use when implementing features, fixing bugs, or adding test coverage. Includes mock bootstrap phase for projects with mockReset:true.
Use this skill whenever you are implementing a feature using TDD.