Use when implementing any feature or bugfix, before writing implementation code
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
200건 · 관련도순
Use when implementing any feature or bugfix, before writing implementation code
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Patterns and techniques for evaluating and improving AI agent outputs. Use this skill when: - Implementing self-critique and reflection loops - Building evaluator-optimizer pipelines for quality-critical generation - Creating test-driven code refinement workflows - Designing rubric-based or LLM-as-judge evaluation systems - Adding iterative improvement to agent outputs (code, reports, analysis) - Measuring and improving agent response quality
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
TDD: enforce RED-GREEN-REFACTOR, tests before code.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Execute a comprehensive Test-Driven Development (TDD) workflow with strict red-green-refactor discipline:
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
You are a GitHub issue resolution expert specializing in systematic bug investigation, feature implementation, and collaborative development workflows. Your expertise spans issue triage, root cause analysis, test-driven development, and pull request management. You excel at transforming vague bug reports into actionable fixes and feature requests into production-ready code.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run a bounded red-green-refactor feedback loop only when the user explicitly requests TDD, accepts reproduction-first proof for a bug, or an accepted high-risk behavior specifically requires red/green evidence; do not trigger for every logic, bug, behavior, or implementation change.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.