“test-first”的搜索结果

Drive one feature through a strict TDD Red-Green-Refactor cycle with checklists for each phase. Use when implementing new functionality test-first, or when the user runs /test-first.

中文简介正在准备中。当前显示原文说明。

Implement approved development stories and code changes with Amelia, a senior software engineer persona. Follow a test-first process: write a failing test, make it pass, then improve the code while checking every acceptance criterion.

中文简介正在准备中。当前显示英语简介。

• Implementing an approved development story
• Making code changes with a test-first process
• Checking implementation against acceptance criteria

Develop behavior through one failing test and one minimal implementation at a time. Tests use agreed interfaces and expected results from specifications or documented examples, producing evidence of both failure and success, including for bug fixes.

中文简介正在准备中。当前显示英语简介。

• Adding behavior through small test-first steps
• Reproducing a bug before fixing it
• Checking results against specifications

Transform SDD tasks into test-first TDD task pairs. Reads existing tasks from /create-tasks and generates paired test tasks with RED-GREEN dependencies. Use when user says "create tdd tasks", "add tdd pairs", "convert to tdd", or wants to apply test-first ordering to SDD tasks.

中文简介正在准备中。当前显示原文说明。

Use this skill when writing test-first, behavior-driven acceptance criteria in Given/When/Then format for a Salesforce user story. Covers happy path, edge cases, negative paths, permission boundaries, and data-state preconditions so the AC block can drive UAT scripts and Apex test design downstream. Trigger keywords: given when then, gherkin, behavior driven AC, test first acceptance criteria, scenario outline, BDD acceptance criteria. NOT for the user-story format itself (use admin/user-story-writing-for-salesforce). NOT for UAT script writing (use admin/uat-test-case-design). NOT for Apex test method generation (use agents/test-class-generator). NOT for high-level UAT planning (use admin/uat-and-acceptance-criteria). More triggers: acceptance criteria record, ac_id, req_id on a criterion, artefact under test, negative case for a rule-type requirement, no-match fall-through criterion, oracle for a Then clause, test type apex flow manual, criteria linter, check_ac_format.py, --manifest-dir.

中文简介正在准备中。当前显示原文说明。

Drive Keel agent test-first or evidence-first execution for a selected OpenSpec task. Use when a task needs software tests, hardware testbench, assertions, lint, new behavior proof, regression coverage, or red/green evidence before implementation.

中文简介正在准备中。当前显示原文说明。

Runs the test-first build loop (spec, plan, thin slices, failing test first, verify, commit) for a Godot 4 game in GDScript or C# first; in a TypeScript, Python or other repo when test-first, slices or a reproduce-first fix is asked for. Trigger to build or add a game feature, mechanic, stat, system or milestone, even when told to test later; to turn a spec or grill record into slices; to fix a game bug from a reproduction, one hypothesis at a time; on "write the test first", "what's the next slice", "is this slice done" or "is this milestone ready to exit"; or say slicesmith (spec, plan, slice, fix, exit). Run proof and gate rulings are godotsmith's; diff review a review tool's; repo maps researchscribe's; art pixelsmith's; audio soundsmith's; interviews grillwright's; fan-out dispatchwright's.

中文简介正在准备中。当前显示原文说明。

通过先写失败测试、再添加最小实现来开发功能或修复缺陷。从调用方使用的公开接口验证行为，编写不依赖内部结构的测试。

• 先写测试再添加功能
• 从缺陷复现测试开始修复
• 确定集成测试覆盖的接口

使用pytest设计和编写Python测试，复用准备与清理步骤，模拟外部服务，以多组输入验证行为，并测量代码覆盖率、找出尚未验证的部分。

• 先写测试再开发Python功能
• 复用测试准备与清理步骤
• 模拟外部API进行验证

支持编写和运行Perl测试、替换外部依赖、验证异常及测量代码覆盖率，也可用于测试先行的开发、失败原因排查和现有测试的迁移。

• 先写测试再开发Perl代码
• 迁移Test::More测试
• 独立验证API和数据库交互

按照先写测试的流程编写Rust单元、集成和异步测试，涵盖生成多样输入、替换依赖、性能基准测试与覆盖率检查，用于验证行为并补充未测试部分。

• 先写测试再开发Rust代码
• 为现有代码补充测试
• 验证异步操作与超时

从测试开始实现 Laravel 功能，使用 PHPUnit 或 Pest 验证模型、API、身份认证和权限，模拟外部服务，并通过覆盖率了解测试执行了哪些代码。

• 从测试开始实现 Laravel 功能
• 验证 API 身份认证与权限
• 模拟支付、邮件和队列

根据变更规模，为功能开发、缺陷修复等工作选择调研、规划、测试和审查阶段。这套相关技能共用的流程包含计划审批和提交前确认。

• 统一功能开发与缺陷修复流程
• 根据变更规模选择开发阶段
• 依据设计文档开发MVP

按先写测试的流程开发Go代码，支持多组用例、HTTP响应验证、性能基准测试、自动生成输入的模糊测试，以及查看测试执行范围的覆盖率检查。

• 先写测试再开发Go代码
• 补充正常与异常测试用例
• 比较运行时间和内存分配量

通过先写测试再实现功能的流程，验证Django模型、页面和API，涵盖测试数据生成、外部服务模拟及代码覆盖率，帮助确认功能行为与测试范围。

• 先写测试再开发Django功能
• 检查API认证和输入验证
• 准备可复用的测试数据

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

Coordinate multiple agents to maintain context-mode, from sorting GitHub issues and reviewing pull requests to preparing releases and announcements. Workflows require reproduced bugs, source evidence, test-first changes, and checks across supported platforms.

中文简介正在准备中。当前显示英语简介。

• Investigating reported bugs and their history
• Reviewing contributor pull requests
• Preparing releases and compatibility checks

Write and review Handsontable tests that check intended behavior. The skill guides bug reproduction, meaningful assertions, failure diagnosis, and fresh test runs, while covering mock boundaries and migration of broken legacy tests to Playwright.

中文简介正在准备中。当前显示英语简介。

• Reproducing a bug with a failing test
• Diagnosing whether code or test expectations are wrong
• Reviewing assertions for meaningful behavior checks

Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.

中文简介正在准备中。当前显示原文说明。

Test-driven development workflow with philosophy guide - plan → write tests → implement → validate

中文简介正在准备中。当前显示原文说明。

Test-first development route for TDD, writing failing tests first, RED -> GREEN -> REFACTOR, and behavior-changing feature/bug/refactor work. Do not use for already-failing test root-cause debugging, test-report packaging, or final completion evidence.

中文简介正在准备中。当前显示原文说明。

Root-cause route for actual bugs, failing tests, build errors, crashes, stack traces, and unexpected behavior. Do not use for test-first/TDD feature work, test-report packaging, review-feedback handling, or final completion evidence.

中文简介正在准备中。当前显示原文说明。

Default code-quality route for broad code review, PR review, maintainability, correctness, and regression-risk checks. Do not use as the primary route for dedicated OWASP/security audits, review-feedback handling, completion verification, AI-code cleanup, or TDD/test-first work.

中文简介正在准备中。当前显示原文说明。

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.

中文简介正在准备中。当前显示原文说明。