Results for “tdd”

Master TDD orchestrator specializing in red-green-refactor discipline, multi-agent workflow coordination, and comprehensive test-driven development practices. Enforces TDD best practices across teams with AI-assisted testing and modern frameworks. Use PROACTIVELY for TDD implementation and governance.

The English summary is being prepared. Showing the original description.

Test-driven development for substantive feature, bug-fix, and behavior-changing work. Use automatically when implementing features, fixing bugs, or changing behavior (red → green → refactor). Also use when the user mentions TDD, /tdd, /TDD, or red-green-refactor. Do not use for documentation-only, formatting-only, exact generated-mirror, or provenance-only changes.

The English summary is being prepared. Showing the original description.

Use when implementing features or writing code. TDD enforcement is opt-in via --tdd / MEOWKIT_TDD=1. Provides code patterns, skill loading, and coding standards.

The English summary is being prepared. Showing the original description.

git diff 기준 변경 파일을 자동 탐지해 Composed Method 지향 Tidying Process를 TDD 사이클 없이 독립 실행. 완료 후 선택 기법 제안. "변경 파일 정리", "tidying만", "방금 바꾼 코드 정돈", "tidy first", "/tdd-tidy" 요청 시 사용. 단, 다른 클래스로 로직을 옮기는 구조 변경은 /system-wide-refactoring이 적합. /tdd-tidy [commit-ref]로 호출.

The English summary is being prepared. Showing the original description.

TDD 세션이 끝난 뒤 "어디서 시간·토큰이 많이 들었나"를 단계(Skill)·에이전트별로 집계하고 병목과 model/effort 조정안을 보고한다. 세션 transcript를 읽는 사후 분석이며 코드를 바꾸지 않는다. "이번 TDD 세션 병목 분석", "토큰 어디에 썼어", "어느 단계가 느렸어", "모델 조정 제안", "/tdd-profile" 요청 시 사용.

The English summary is being prepared. Showing the original description.

テストは存在するがアサーションが実質何も検証しておらず、実装が壊れても落ちない（常に PASS する）構造を diff-time で検出する。Check 1 missing assertion（テスト本体にアサーションが無い）、Check 2 tautological assertion（定数同士・入力自身・mock の戻り値自身を assert し SUT に依存しない）、Check 3 nonexistent expected literal（assertDontSee / assertNotContains 等の期待文字列が対象ファイルに実在しない）、Check 4 stale expected value（同一 diff で対象の出力が変わったのに期待値が据え置き）、Check 5 unscoped expectation（汎用的な属性・クラスを応答全体に対して assert し対象要素にスコープされていない）、Check 6 swallowed failure（例外の握り潰しや到達しない位置のアサーションで判定が成立しない）、の 6 Check を対象とする report-only。テストの有無は test-existence、未テスト経路の量は coverage-gap、非決定性は flaky-test、命名は test-naming、JS/TS の un-awaited resolves / rejects は vitest-mock-isolation、tdd-ledger artifact ベースの RED/GREEN 検証は plangate-tdd-evidence、.only / .skip / xit / @ts-ignore と空の catch は heuristic-review.mjs の決定論検出器へ委譲する

The English summary is being prepared. Showing the original description.

テスト駆動開発（TDD）の0spec-1red-2green-3blueサイクルを実施します。対話でテスト対象を絞り込み、コンテキスト消費を最小化します。

The English summary is being prepared. Showing the original description.

features.json を読み込み、pending な機能を1件ずつ tdd-guide エージェント（内部で tdd-cycle を使用）で実装するスキル。 Context anxiety（トークン上限接近による焦り）と Context rot（情報劣化）を防ぐため、 機能単位のループ・状態管理・implementation-notes.md への記録を担う。 builder エージェントが実装フェーズを開始するときは必ずこのスキルを呼ぶ。

The English summary is being prepared. Showing the original description.

Master TDD orchestrator specializing in red-green-refactor discipline, multi-agent workflow coordination, and comprehensive test-driven development practices. Enforces TDD best practices across teams with AI-assisted testing and modern frameworks. Use PROACTIVELY for TDD implementation and governance.

The English summary is being prepared. Showing the original description.

Develop and refactor Quarkus 3.x LTS services by writing tests first. Covers API responses, event handling, and asynchronous operations, with unit and integration tests plus coverage checks to show how much code is tested.

• Adding REST endpoints with tests first
• Reproducing bugs before fixing them
• Testing Apache Camel routes and event handling

Coordinate a new feature from research and planning through tests, implementation, review, and commit. Assign phases to matching ECC agents, write failing tests before implementation, and pause for approval of the plan and before committing.

• Adding a capability that does not exist yet
• Implementing a feature with tests written first
• Reviewing an authentication feature for security

Coordinate feature work, bug fixes, refactoring, and MVP development through shared phases scaled to the change. Related operation skills use this workflow to delegate research, planning, test-first implementation, review, and commits with human approval checkpoints.

• Using a shared process for feature additions and bug fixes
• Scaling development steps to the size of a change
• Organizing MVP development from a design document

Build Laravel features test first with PHPUnit or Pest. Create tests for models, HTTP endpoints, authentication, and permissions, simulate external services, and measure coverage to see which code your tests exercise.

• Building Laravel features test first
• Testing API authentication and permissions
• Simulating payments, mail, and queues in tests

Write Kotlin tests with Kotest and MockK using test-driven development, where tests come before implementation. Cover asynchronous code, check behavior across generated inputs, and use Kover reports to measure how much code the tests exercise.

• Adding tests to existing Kotlin code
• Developing new functions by writing tests first
• Testing coroutines and Flow behavior

Helps build Go tests using a test-first workflow. Covers grouped test cases, HTTP response checks, performance benchmarks, fuzzing to explore generated inputs, and coverage reports showing which code was exercised by tests.

• Developing Go functions with tests written first
• Adding normal and error cases to existing tests
• Measuring execution time and memory allocations

Write Django and Django REST Framework tests with pytest-django, starting with tests before implementation. Covers test data generation, simulated external services, model and API checks, and coverage reports showing which code the tests exercise.

• Developing Django features by writing tests first
• Testing API authentication and input validation
• Generating reusable test data

Develop features through a test-first workflow using mocks, or stand-ins for dependencies. Write a failing behavior test, implement the minimum code, refactor, and record observed results from final target and regression tests.

• Define expected behavior before implementing a feature
• Test modules with mocked external dependencies
• Refactor code while keeping tests passing

Automatically repair source code against a failing test while preserving the test itself. Set a spending limit and attempt count, then receive verification results and usage costs based on rerunning the test command.

• Repairing a failing CI test after a commit
• Implementing code to pass a test written first
• Investigating a regression within a fixed budget

Follow Conductor's development plans using test-driven development: write a failing test, implement the change, then improve the code. Manage phase verification, progress updates, and focused git commits as tasks move toward completion.

• Implementing tasks from plan.md
• Following the test-driven development cycle
• Verifying completion at phase checkpoints

Implement the minimal code needed to make failing tests pass in the TDD green phase.

The English summary is being prepared. Showing the original description.

Generate failing tests for the TDD red phase to define expected behavior and edge cases.

The English summary is being prepared. Showing the original description.

Refactor code while preserving passing tests and behavior. Use during the TDD refactor phase to remove duplication, improve design, and verify each structural change.

The English summary is being prepared. Showing the original description.

Coordinate the test-driven development cycle from requirements and failing tests through implementation, refactoring, and validation. Use when building a feature with a structured TDD workflow.

The English summary is being prepared. Showing the original description.

Guides the red-green-refactor TDD workflow: write a failing test first, implement the minimum code to make it pass, then refactor while keeping tests green. Use when a user asks to practice TDD, write tests first, follow red-green-refactor, do test-driven development, write failing tests before code, or phrases like 'make the test pass', 'test coverage', or 'unit tests before implementation'.

The English summary is being prepared. Showing the original description.