'tdd' 검색 결과

Carry out an existing implementation plan one task at a time in the current session. Verify each task with tests, record progress and decisions in a file, and review the whole branch after implementation.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Implementing an existing plan in a single session
• Resuming work from a saved progress ledger
• Recording decisions when a plan conflicts with its specification

Guides feature development and bug fixes through test-driven development: write a test, confirm the expected failure, then add the minimum code to pass. It also covers refactoring and checking the full test suite.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Define expected behavior before building a feature
• Reproduce a bug with a failing test
• Refactor code while keeping tests passing

Turn a specification and its linked tickets into code. Multiple agents work on available tasks in separate worktrees, combine changes on one integration branch, and complete a code review before preparing the result for review or closing tickets.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Implementing a specification and its linked tickets
• Working through tasks with blocking dependencies
• Coordinating parallel implementation in separate worktrees

Implement work described in a specification or set of tickets, using test-first development where agreed. Run type checks and tests throughout, review the completed changes, and commit the work to the current branch.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Implementing work from a specification
• Completing a set of development tickets
• Checking changes with types and tests

Build features or fix bugs by writing one failing test, then the minimum code needed to pass it. Test agreed public interfaces, the boundaries callers use, to check behavior without depending on internal implementation details.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Building a feature through test-first development
• Fixing a bug with a failing test first
• Writing behavior-focused integration tests

Develop behavior changes by first observing an expected test failure, then making the smallest passing implementation. Refactor with tests passing, and document preserved behavior and measured runtime whenever tests are consolidated.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Add behavior through a failing test
• Fix a bug with a test that reproduces it
• Refactor while keeping affected tests passing

Build a planned feature by following an existing task list and technical plan. The skill respects task dependencies, runs tests before related implementation where applicable, records progress, and checks the completed work against the specification.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Implementing a feature from an existing task breakdown
• Developing with tests before the related implementation
• Tracking completed tasks and checking the final result

Evaluate existing code review comments against the actual codebase before making changes. The skill guides clarification, technical responses, prioritized fixes, and individual testing, helping assess whether suggestions fit current behavior and compatibility requirements.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Assessing CodeRabbit or GitHub review comments
• Clarifying ambiguous requests before making changes
• Explaining why a suggested change would break compatibility

Implement approved development tasks one at a time using test-driven development, which starts with a failing test. Process all pending tasks or selected ones, check changes against requirements and design, and update progress after review and completion verification.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Working through all approved pending tasks
• Implementing selected task numbers
• Developing features with tests written first

Use only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious cheap local test target. Skip when the test path is unclear, expensive, integration-heavy, or not requested.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Drive a change through a red-green-refactor loop - failing test first, minimal code to pass, then clean up. Use when implementing a feature or fixing a bug where correctness matters and a test can pin the behavior. Says "TDD", "test first", "red green refactor", "write the test first".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious cheap local test target. Skip when the test path is unclear, expensive, integration-heavy, or not requested.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

在编写新功能、修复 Bug 或重构代码时使用此技能。强制执行测试驱动开发（TDD），包括单元测试、集成测试和端到端（E2E）测试，覆盖率需达到 80% 以上。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Django 测试策略，包括 pytest-django、TDD 方法、factory_boy、模拟、覆盖率以及测试 Django REST Framework API。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

在创建新功能、修复 Bug 或重构代码时使用此技能。强制执行测试驱动开发（TDD），要求包括单元测试、集成测试和 E2E 测试在内的测试覆盖率达到 80% 以上。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

使用 JUnit 5, Mockito, MockMvc, Testcontainers 和 JaCoCo 进行 Spring Boot 的测试驱动开发（TDD）。适用于添加新功能、修复 bug 或重构场景。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

在编写新功能、修复 Bug 或重构代码时使用此技能。强制执行测试驱动开发（TDD），包括单元测试、集成测试和 E2E 测试，且覆盖率需达到 80% 以上。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Django testing strategies with pytest-django, TDD methodology, factory_boy, mocking, coverage, and testing Django REST Framework APIs.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

使用 pytest-django 进行 Django 测试的策略、TDD 方法论、factory_boy、Mock 模拟、测试覆盖率以及测试 Django REST Framework API。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

使用 JUnit 5、Mockito、MockMvc、Testcontainers 和 JaCoCo 进行 Spring Boot 的测试驱动开发 (TDD)。在添加功能、修复 Bug 或进行重构时使用。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Drive feature development using Outside-In TDD with Hexagonal Architecture. Design emerges through inline code, in-memory fakes, interface extraction, and deferred I/O. Use when building features, writing tests, or structuring backend services. Triggers on: TDD, outside-in, hexagonal, ports and adapters, emergent design, acceptance test, component test, walking skeleton, in-memory fakes, component, contract test, adapter, fast tests, sub-second feedback. Language-agnostic (Go, Rust, Python, TypeScript, Java, C#).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Red-Green-Refactor TDD methodology with mandatory failing tests, minimal implementation, quality refactoring, and 80% coverage gating.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the user explicitly requests strict or test-first TDD, or when the current conversation already contains an explicit `TDD Route: strict` decision from another Aegis workflow.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.