Use only when the user explicitly invokes obra test-driven-development for iron-law examples. Core TDD is docs/ai/skills/tdd/SKILL.md. Do not use this for docs-only, formatting-only, or generated-mirror changes.
中文简介正在准备中。当前显示原文说明。
66 个 · 按相关度排序
Use only when the user explicitly invokes obra test-driven-development for iron-law examples. Core TDD is docs/ai/skills/tdd/SKILL.md. Do not use this for docs-only, formatting-only, or generated-mirror changes.
中文简介正在准备中。当前显示原文说明。
通过先写测试、确认失败再实现的流程添加功能或修复缺陷。只编写让测试通过所需的代码,再保持测试通过并整理代码,完成前运行项目的完整测试集。
通过测试创建、修订和发布前验证 AI 智能体技能,比较使用指令前后的行为,找出遗漏或误解,并调整文档结构、搜索说明和措辞。
先准备可重复复现症状的测试或命令,再按原因调查、正常示例对比、假设验证和修复四个阶段,定位根本原因并用回归测试验证结果。
将测试驱动开发用于功能新增和缺陷修复:先写测试并确认失败,再用最少代码使其通过,最后整理代码,逐项验证行为。
为新功能和缺陷修复先编写失败测试,再以最少代码实现通过并整理代码。反复验证预期行为及对现有功能的影响,遵循项目已有测试工具与约定。
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.
中文简介正在准备中。当前显示英语简介。
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.
中文简介正在准备中。当前显示英语简介。
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.
中文简介正在准备中。当前显示英语简介。
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.
中文简介正在准备中。当前显示英语简介。
Create and improve agent skills by testing behavior before and after adding guidance. The skill applies test-driven development to SKILL.md documents, covering structure, discovery descriptions, supporting files, and checks that reveal unclear or ineffective instructions.
中文简介正在准备中。当前显示英语简介。
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.
中文简介正在准备中。当前显示英语简介。
Use when implementing any feature or bugfix, before writing implementation code
中文简介正在准备中。当前显示原文说明。
Use when implementing any feature or bugfix, before writing implementation 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.
中文简介正在准备中。当前显示原文说明。
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.
中文简介正在准备中。当前显示原文说明。
Use when implementing any feature or bugfix, before writing implementation code
中文简介正在准备中。当前显示原文说明。
Use when implementing any feature or bugfix, before writing implementation code. Enforces RED-GREEN-REFACTOR cycle.
中文简介正在准备中。当前显示原文说明。
Test-first development practice where test specifications are written before production code, integrated into plan tasks as mandatory first sub-steps.
中文简介正在准备中。当前显示原文说明。
Strict RED-GREEN-REFACTOR cycle enforcement. Tests are never skipped or deferred. Run mode only, never watch mode. Exit code evidence mandatory.
中文简介正在准备中。当前显示原文说明。
Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first
中文简介正在准备中。当前显示原文说明。
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.
中文简介正在准备中。当前显示原文说明。
Guide red-green-refactor TDD with test generation, coverage-gap analysis, and multi- framework support. Use when writing tests first, analyzing coverage, generating test stubs, or converting tests between Jest, Pytest, JUnit, and Vitest.
中文简介正在准备中。当前显示原文说明。
Use when implementing any feature or bugfix, before writing implementation code
中文简介正在准备中。当前显示原文说明。