test-discipline

Name: test-discipline
Availability: InStock
Author: jperezdelreal

Enforce in-commit test updates when APIs or public interfaces change.

Updated Apr 6, 2026

Search Tags:#quality-assurance #ci #api-changes #update-tests #test-assertions #disk-reality

Ready to run

npx skills add https://github.com/jperezdelreal/GymBro --skill test-discipline-jperezdelreal

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: test-discipline
Source: https://github.com/jperezdelreal/GymBro/tree/main/.copilot/skills/test-discipline
Command: npx skills add https://github.com/jperezdelreal/GymBro --skill test-discipline-jperezdelreal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When APIs or public interfaces change, tests must be updated in the same commit. When test assertions reference file counts or expected arrays, they must be kept in sync with disk reality. Stale tests block CI for other contributors.

Core Features & Use Cases

Enforces in-commit test updates on API changes
Keeps test assertions in sync with disk reality
Guards CI by ensuring derived expectations stay current

Quick Start

Update related tests in the same commit whenever you change an API signature or public interface.

Frequently Asked Questions about test-discipline

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

FAQPage Schema

How do I keep test assertions in sync with API changes across commits?▼

To keep test assertions in sync with API changes, you must enforce in-commit updates to tests whenever public interfaces are modified. This prevents stale tests and ensures deterministic consistency by validating patterns, counts, and documentation across the codebase.

Why does stale CI block other contributors when public interfaces change?▼

Stale CI blocks contributors because outdated test assertions referencing file counts or expected arrays no longer match disk reality. Enforcing in-commit test updates during API changes keeps derived expectations current and prevents CI failures for other developers.

What is the best way to enforce test updates when API signatures change?▼

The best way to enforce test updates for API signature changes is to require related tests to be updated in the same commit. This guarantees deterministic test consistency and disk-reality alignment by validating patterns and counts across the codebase.

How do I validate test counts and patterns against disk reality in CI?▼

Validating test counts and patterns against disk reality requires synchronizing test assertions with actual file states during API updates. Enforcing in-commit updates ensures derived expectations stay current and guards CI from deterministic test consistency failures.

Can I use this approach for software development workflows with frequently updated public interfaces?▼

Yes, this approach applies directly to software development workflows where public interfaces and assertions are frequently updated across commits, pull requests, and CI runs. It enforces in-commit test updates to maintain deterministic test consistency and disk-reality alignment.