test-discipline

Detect API changes requiring corresponding test updates in the same commit.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/chdaly/eshop --skill test-discipline-chdaly
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-discipline
Source: https://github.com/chdaly/eshop/tree/main/.copilot/skills/test-discipline
Command: npx skills add https://github.com/chdaly/eshop --skill test-discipline-chdaly

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Tests can become out of date whenever public APIs change, leading to CI failures and unnoticed regressions.

Core Features & Use Cases

  • In-commit test updates: synchronize tests with API changes within the same commit.
  • Disk-reality validation: ensure test data and expectations match the repository state.
  • Documentation of expectations: capture test expectations alongside code changes for future maintenance.

Quick Start

Follow the practice to update tests in the same commit whenever API signatures or interfaces change.

Frequently Asked Questions about test-discipline

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I keep tests in sync when API changes happen in the same commit?

Validate disk-reality by checking that test data and expectations match the current repository state, ensuring that test assertions accurately reflect the public interfaces before pushing code changes.

Why do CI failures happen after public API changes if tests are not updated?

CI failures occur after public API changes because outdated test assertions no longer match the modified interfaces, leading to test data inconsistency and unnoticed regressions across commits.

What is the best way to document test expectations alongside code changes?

Document test expectations by capturing them within the same PR as the API changes, enforcing in-commit test updates that synchronize tests with code for future maintenance and clear regression tracking.

When do I need to validate disk-reality for test data consistency?

Validate disk-reality when modifying public interfaces, checking that test data and expectations match the repository state to ensure test assertions accurately reflect the current codebase.