'test-driven' 검색 결과

증상을 재현하는 테스트나 명령을 준비하고 원인 조사, 정상 사례 비교, 가설 검증, 수정의 네 단계를 진행합니다. 근본 원인을 찾고 회귀 테스트로 결과를 확인합니다.

• 테스트나 빌드 실패 조사
• 여러 시스템에 걸친 이상 추적
• 간헐적인 버그 재현

Develop and fix code by first writing a failing test, then making it pass and improving the implementation. The skill follows the project's testing tools and checks both the intended behavior and existing functionality.

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

• Implement new logic with tests written first
• Reproduce a reported bug before fixing it
• Check existing behavior when changing code

Organize software development from requirements and architecture through testing, review, and deployment. Use specialized agent roles, shared memory, and test-driven development, where tests are written before code, to coordinate work across the project.

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

• Plan and implement a new feature
• Refactor legacy code with supporting tests
• Review code security and performance

Build features or fix bugs by writing a small test first, checking that it fails for the expected reason, and making the smallest code change needed. Run related tests and review the changes for unintended effects.

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

• Reproducing a bug with a regression test
• Defining expected behavior before implementing a feature
• Checking parser, routing, or UI behavior changes

Guide Rust development through test-driven development: write a failing test, implement enough code to pass, then refactor. Includes practical test patterns and final checks for formatting, static analysis, and test results.

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

• Adding Rust features with tests first
• Reproducing bugs with failing tests before fixing them
• Testing invalid inputs and error paths

Turn specifications and designs into working code using test-driven development: write failing tests, implement enough code to pass, then refactor. The workflow also covers error handling, performance improvements, documentation, and coordinated changes across components.

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

• Implementing a feature from specifications and designs
• Developing authentication or APIs with tests
• Refactoring code while checking test results

Create automated shell script tests with Bats, a Bash testing tool. Check exit codes, output, and failure cases, organize reusable test helpers and data, and run checks across shells or in CI/CD pipelines.

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

• Add automated tests to shell scripts
• Check invalid input and missing file errors
• Test behavior in bash, sh, and dash

Create and organize Python tests with pytest. Use reusable setup, mock replacements for external services, controlled test time, and coverage reports to check normal behavior, failures, retries, and interactions between application components.

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

• Add unit and integration tests to Python code
• Replace external services with mocks in tests
• Check retry behavior and time-dependent logic

Write JavaScript and TypeScript tests with Jest, Vitest, and Testing Library. Covers functions, UI components, and APIs, including mock replacements for external services, reusable test data, and setup for automated testing.

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

• Set up testing for a new project
• Test functions and API error handling
• Check React component behavior

Design workflows that evaluate and refine AI outputs through self-review, separate generation and evaluation roles, tests, or weighted scoring criteria. Includes patterns for structured feedback, iteration limits, and stopping when quality stops improving.

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

• Adding self-review and revision loops to AI outputs
• Separating generation from evaluation
• Refining generated code using test results

Guide development from problem definition and planning through testing, debugging, review, and final verification. It uses test-driven development, writing a failing test before implementation, and requires evidence before reporting work as complete.

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

• Define a development goal and acceptance checks
• Implement a change starting with a failing test
• Investigate a reproducible bug through small experiments

Investigate bugs, failing tests, and unexpected behavior through reproducible steps, logs, and comparisons with working code. Follow four stages to identify the root cause, test a hypothesis, apply a focused fix, and verify the result.

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

• Investigating failing tests
• Tracing production bugs to their source
• Finding where a build or integration breaks

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

Develop features and fix bugs by writing a behavior test first, observing its expected failure, and adding the minimum code needed to pass. Then clean up the code while keeping tests passing, applying this process where regression risk warrants it.

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

• Developing a feature from a failing behavior test
• Reproducing a bug before implementing its fix
• Refactoring while keeping behavior tests passing

Write Jest unit tests for component behavior and user interactions. Includes reusable test data builders, mock replacements for dependencies, and test-driven development, where a failing test guides implementation before the code is cleaned up.

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

• Testing component rendering and form interactions
• Creating reusable test data with selective overrides
• Replacing modules and GraphQL hooks in tests

Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.

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

Collaboratively build and refine paper screening rubrics through brainstorming, test-driven development, and iterative feedback

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

Use when implementing any feature or bugfix, before writing implementation code

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

Troubleshoot Golang programs systematically - find and fix the root cause. Use when encountering bugs, crashes, deadlocks, races, or unexpected behavior in Go code. Covers debugging methodology, common Go pitfalls, test-driven debugging, pprof setup and capture, Delve, race detection, GODEBUG tracing, and production debugging. Start here for any 'something is wrong' situation. Not for interpreting profiles or benchmarking (→ See `samber/cc-skills-golang@golang-benchmark` skill), applying optimization patterns (→ See `samber/cc-skills-golang@golang-performance` skill), or designing new code (→ See `samber/cc-skills-golang@golang-safety` skill for defensive coding, `samber/cc-skills-golang@golang-concurrency` skill for concurrency design).

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

Use when implementing any feature or bugfix, before writing implementation code

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

Guides implementation of code tasks using test-driven development in an Explore, Plan, Code, Commit workflow. Acts as a Technical Implementation Partner and TDD Coach — following existing patterns, avoiding over-engineering, and producing idiomatic, modern code.

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

Unified TDD skill with three input modes — from spec, from task, or from description. Enforces test-first development using repository patterns, with proptest guidance and backpressure integration.

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

Test-driven development workflow with Red-Green-Refactor cycle across languages

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

Drives implementation by writing a failing test first, then the smallest code that passes it. Use this before writing implementation code for any feature or bugfix, when a bug needs a regression test, when existing code is hard to change safely, or when someone asks whether a change is covered. Also use to decide what is worth testing and what is not.

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