Skip to content
Skills Library
Programming · Testing

test-driven-change

/test-driven-change

Implement a behavior change with tests that demonstrate the requirement and protect regressions. Use for bug fixes, new features, and changes with observable inputs and outputs.

Licence
MIT
Last repository change
30.10.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 30.10.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

Implement a behavior change with tests that demonstrate the requirement and protect regressions. Use for bug fixes, new features, and changes with observable inputs and outputs.

Original author description

Implement a behavior change with tests that demonstrate the requirement and protect regressions. Use for bug fixes, new features, and changes with observable inputs and outputs.

How it works

  1. Operating rule
  2. Procedure
  3. Evidence to report
  4. Boundaries
Original SKILL.md headings · 23 lines, 229 words
SKILL.md preview
---
name: test-driven-change
description: Implement a behavior change with tests that demonstrate the requirement and protect regressions. Use for bug fixes, new features, and changes with observable inputs and outputs.
license: MIT
---

# Test-Driven Change

## Operating rule
A test is evidence only if it can fail for the defect or missing behavior being addressed. Do not add tests that merely repeat the implementation.

## Procedure
1. Find the project's existing test framework and nearest representative tests. Preserve local conventions.
2. Write or adapt the smallest test that captures the desired behavior. For a reported bug, make sure it fails before the fix when practical.
3. Run the targeted test and record the initial result. If it does not fail, explain why and improve the test.
4. Implement the smallest production change that makes the test pass. Avoid unrelated refactors in the same diff.
5. Add edge cases around boundaries, invalid input, empty states, errors, and backwards compatibility where relevant.
6. Run targeted tests, then the appropriate broader suite, formatter, linter, and type checker when available.
7. Inspect the final diff for changed behavior not covered by tests.

## Evidence to report
State which tests were run, their actual results, and any checks not run. Include commands when useful.

## Boundaries
- Do not weaken assertions, skip failing tests, or mock away the behavior under test just to obtain a green result.
- Do not claim a test passed if it was not executed.
- If the repository has no test infrastructure, propose the smallest useful check and disclose the limitation.

Versions

The database has no other skills named test-driven-change.

Database snapshot: 13.11.2026 · package version 6588288dd751 (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

  • 100tdd
    Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
  • 100tdd
    Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
  • 100tdd
    Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
  • 100tdd
    Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
  • 100tdd
    Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
  • 100tdd
    Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

Feedback and reports

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