Skip to content
Skills Library
Programming · Building & coding

test-driven-development

/test-driven-development

Develop behavior through a failing test or reproducer, implementation, and refactoring. Use when test-first development is requested or a new behavior or bug fix benefits from an executable regression before implementation.

Repository
malskill ↗
Licence
MIT
Last repository change
13.11.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Develop behavior through a failing test or reproducer, implementation, and refactoring. Use when test-first development is requested or a new behavior or bug fix benefits from an executable regression before implementation.

Original author description

Develop behavior through a failing test or reproducer, implementation, and refactoring. Use when test-first development is requested or a new behavior or bug fix benefits from an executable regression before implementation.

How it works

  1. Choose the appropriate entry point
  2. RED-GREEN-REFACTOR
  3. Diagnose an unexpected test result
  4. Apply to security tooling
Original SKILL.md headings · 34 lines, 480 words
SKILL.md preview
---
name: test-driven-development
description: "Develop behavior through a failing test or reproducer, implementation, and refactoring. Use when test-first development is requested or a new behavior or bug fix benefits from an executable regression before implementation."
license: MIT
compatibility: "Language-agnostic TDD workflow. Pair with language-specific testing skills for commands and framework details."
metadata:
  author: AeonDave
  version: "1.1"
---

# Test-Driven Development

Make the intended behavior observable before implementing it, then use the check to guide a small complete change. A passing test supports the behavior it covers; it is not a proof of correctness.

## Choose the appropriate entry point

- For a new behavior or reproducible bug, use the failing-check loop below when practical. Follow explicit user and repository testing requirements.
- For a behavior-preserving refactor, establish a passing baseline and add characterization only for relevant uncovered behavior. Keep those checks green; do not manufacture a failure for behavior that should stay unchanged.
- For code already written, preserve it and assess the missing verification. Add meaningful checks; use an isolated pre-change baseline or controlled fault to test their sensitivity when useful. Do not discard work or restart implementation merely to recreate test-first history.
- For exploration, configuration, generated artifacts, or changes that do not benefit from a new automated test, choose the appropriate existing check, generator test, static validation, or reproducible manual procedure. State what remains unverified; do not describe tests written afterward as a test-first sequence.

For an urgent incident, use `systematic-debugging` to prioritize authorized mitigation and preserve evidence. Missing deterministic reproduction does not forbid investigation or recovery.

## RED-GREEN-REFACTOR

1. **Specify** one behavior and its observable outcome. Reuse a relevant existing check or failing artifact rather than creating a duplicate.
2. **RED**: write the smallest useful test/reproducer and run it. Confirm that failure represents the missing behavior or defect; distinguish an intentionally absent API from an unrelated import, fixture, or environment error.
3. **GREEN**: implement the smallest complete change that satisfies the behavior. Run the focused check and relevant neighboring cases; do not weaken assertions to make it pass.
4. **REFACTOR**: improve the affected structure while preserving the contract and keeping checks green. Use `software-architecture` for consequential design or simplification decisions.
5. **Continue and verify**: take the next behavior when needed and run applicable broader checks. Use `verification-before-completion` for required gates, evidence freshness, and completion claims.

## Diagnose an unexpected test result

- If a proposed regression already passes, check whether the behavior exists, the intended path ran, and the chosen input/assertion can detect the defect. A passing characterization test is expected.
- If setup fails, repair the relevant fixture or environment before treating the result as evidence about the behavior.
- If setup is excessive, inspect the test scope and existing seams before changing production APIs. Use `testing-reliability` for weak assertions, misleading doubles, fixture coupling, or flakes.

## Apply to security tooling

For parsers, exploit harnesses, or payload tooling, preserve the relevant input, seed, transcript, or artifact before changing code and turn it into a bounded local regression where practical. Use `testing-reliability` for what the assertion must establish and the language/domain testing skill for harness mechanics.

Use `software-guidelines` for patch scope and affected consumers. Language-specific testing skills own framework syntax and execution commands.

Versions

RepositoryScoreLicence
This page · aeondave/malskill90MIT
GanyuanRan/Aegis100MIT
lucasouzadev/agent-kit-skill100MIT
zeative/satgas100AGPL-3.0
nikospavlopoulos/devops-mutant-powers100MIT
JohnStrunk/CommonCast100LGPL
Sanit-mann/The-Insectoids100MIT
mastro993/fstack100MIT
jelvodev/yaap100MIT

Database snapshot: 13.11.2026 · package version b56ba6c148d6 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100054-design-tdd
    Use when Java implementation work should be guided by Test-Driven Development, including maintaining a test list, choosing the next behavior, writing a failing test first, implementing only enough production code to pass, and refactoring while keeping tests green. This should…
  • 100tdd
    Test-driven development through public seams, with a failing test that measures the right behavior before the fix. Use when the user wants to build features or fix bugs test-first, mentions red-green-refactor, asks for a regression test, or wants integration tests.
  • 100tdd
    Test-driven development: the agent writes the failing test, then the code, one behavior at a time. Use when building a feature or fixing a bug test-first, or when the user says tdd, red-green, or test-first.
  • 96sr-test-driven-development
    Use when implementing any feature or bugfix, before writing implementation code
  • 100behavior-driven-development
    Applies behavior-driven development principles including Gherkin scenarios and test-driven development. This skill should be used when the user asks to implement features, fix bugs, or when writing executable specifications and tests before writing production code.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.