test-driven-development

Use when code behaviour is changing and tests should prove the change or guard the regression — a bug fix, a new rule, a refactor with observable effects.

Skill by arbor-ai-inc

IndexedApache-2.0

Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/arbor-ai-inc-test-driven-development

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

About

Use when code behaviour is changing and tests should prove the change or guard the regression — a bug fix, a new rule, a refactor with observable effects. Covers test quality, not just test presence.

Use cases: testing, agent-building

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools: No tools found
Secrets: None asked for
Install scripts: None found

Network hosts it talks to 1

codeload.github.com · found in install command

Files it touches

~/.claude/skills/test-driven-development

What's inside

Skill name: test-driven-development
Description: Use when code behaviour is changing and tests should prove the change or guard the regression — a bug fix, a new rule, a refactor with observable effects. Covers test quality, not just test presence.
License: Apache-2.0
Instructions: 18 lines in SKILL.md · view on GitHub

Files (1)

SKILL.md

SKILL.md (first lines)

<!-- GENERATED by scripts/gen_adapters.py from skills/test-driven-development/SKILL.md.
Do not edit: run the generator instead. The canonical workflow is
reference/test-driven-development.md; this file only routes an agent to it. -->
Follow the canonical procedure in `.cadence/reference/test-driven-development.md` exactly.

Start from the nearest existing tests — they carry the framework, the fixtures and the invocation. Prefer local conventions over introducing a second framework.

**Mutation-test any change that adds a rule.** Break the thing deliberately, watch the test fail, restore it. A guard nobody has seen fail is not known to work, and a passing suite proves nothing about a check the harness never reaches.

State the rule over the **property**, not over the syntactic form you happened to delete — an absence audit written to one spelling passes on every other spelling, which is a silent false negative.

A comment asserting an invariant is a test you have not written yet. Either write it, or downgrade the prose to intent.

**Coverage that does not exist reports the same green as coverage that passes.** A suite no job runs, and a migration nothing executes, both look covered. Verify what actually runs.

Run the project's `[commands].test` before claiming green, and quote what it printed — never "tests pass".

From arbor-ai-inc/cadence, Apache-2.0.

Signals

Stars: 0
Forks: 0
Open issues: 0
Last commit (this folder): Sep 8, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026).

Details

License: Apache-2.0
Repository: github.com/arbor-ai-inc/cadence
First seen: Oct 24, 2026
Last checked: Oct 24, 2026
Source: GitHub github-graphql

More from arbor-ai-inc

Cite this page

test-driven-development skill. Agent Mart. https://agentmart.dev/skills/arbor-ai-inc-test-driven-development (last updated 2026-10-24)