Skill Store 33

Testing Changes

Use when deciding what tests a change needs - a feature, a bug fix, a refactor, any behavior chan…

by riekelt

The skill

Use when deciding what tests a change needs - a feature, a bug fix, a refactor, any behavior change - or when reviewing whether a diff's tests are sufficient. Encodes tests-change-with-behavior, the bug-regression pattern, and assertion discrimination. Use whenever behavior changes and the test diff is empty, especially when the change is "too small to test".

This skill's licence does not allow redistribution, so the store does not show its text. Read it at the source.

Use this skill

Connect your agent to the Skill Store MCP server and ask for it by ref: riekelt/testing-changes-58277889014.

Markdown version

Details

Publisher
riekelt
Category
Software Development › Testing & QA
Updated
2026-09-11

References

More from riekelt

  • Adding Dependencies Use when about to add, update, vet, or remove a dependency - a package, library, SDK, GitHub acti…
  • Grounding Before Coding Use when starting any non-trivial change, investigating a bug, or working in unfamiliar code - be…
  • Guarding Architecture Use when a change crosses module boundaries, adds a dependency direction between modules, touches…
  • Handling Failures Use when writing or touching any error path, catch block, fallback, default value, retry, or degr…

Related skills

  • Testing Craft Use when writing, reviewing, or refactoring tests, or choosing verification for a code change.
  • Testing Design and write effective tests for behavioural changes, bug fixes, and refactors.
  • Tdd You MUST use this when implementing testable behavior changes - new features, bug fixes, or refac…
  • Test Value Evidence Assess tests for an identified code or test change, feature, PR or commit.
  • Change Impact Find forgotten follow-up changes outside a behavior-changing diff in tests, examples, documentati…