test-discipline

Update tests in the same commit when APIs change.

Updated Aug 23, 2026

Search Tags:#testing #code-quality #assertions #ci #test-discipline #api-change-management #test-updates

Ready to run

npx skills add https://github.com/CarlosSardo/nats-poc-simulator --skill test-discipline-carlossardo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: test-discipline
Source: https://github.com/CarlosSardo/nats-poc-simulator/tree/main/.copilot/skills/test-discipline
Command: npx skills add https://github.com/CarlosSardo/nats-poc-simulator --skill test-discipline-carlossardo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When APIs or public interfaces change, tests must be updated in the same commit. Stale tests block CI and cause drift between tests and actual disk state.

Core Features & Use Cases

Enforces updating tests in the same commit when an API changes.
Keeps test assertions in sync with actual files, counts, and arrays.
Guides teams to maintain CI reliability by aligning test updates with code changes.

Quick Start

Update tests in the same commit whenever APIs change to keep test assertions in sync with disk reality.

Frequently Asked Questions about test-discipline

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

FAQPage Schema

Why do my test assertions break in CI after an API change?▼

Test assertions break because they reference stale disk state like file counts or arrays. When APIs change without updating tests in the same commit, test suites drift and block CI pipelines.

How do I keep tests in sync with API changes?▼

To keep tests in sync with API changes, update test assertions and documentation in the same commit as the API modification. This aligns test expectations with actual disk reality and prevents drift.

What is test-suite drift and how does stale state cause it?▼

Test-suite drift occurs when tests reference outdated disk state such as file counts or arrays. Stale tests no longer match actual files, causing CI failures and degrading test integrity over time.

Can I use this approach for codebases where tests reference disk state like counts and arrays?▼

Yes, this approach specifically applies to codebases where tests reference disk state like counts and arrays. It enforces updating those tests in the same commit to match actual files across CI pipelines.

What is the best way to prevent stale tests from blocking CI pipelines?▼

The best way to prevent stale tests from blocking CI is enforcing test discipline by updating tests, assertions, and documentation in the same commit whenever APIs or public interfaces change.

When should I update test assertions to maintain CI reliability?▼

You should update test assertions whenever APIs or public interfaces change. Updating tests in the same commit maintains CI reliability by aligning test updates with code modifications.