test-discipline

Name: test-discipline
Availability: InStock
Author: sudhakrms

Enforce test-suite synchronization with API changes during code reviews.

1|Updated Apr 17, 2026

Search Tags:#quality-assurance #assertions #ci #tests #commit-management #api-changes #disk-reality

Ready to run

npx skills add https://github.com/sudhakrms/CalendarControl --skill test-discipline-sudhakrms

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Update tests when APIs change to keep the test suite in sync; prevents CI blockers and flaky failures by ensuring tests reflect the actual state on disk.

Core Features & Use Cases

API changes → test updates (same commit): When you change a function signature, public interface, or exported API, update the corresponding tests in the same commit.
Test assertions → disk reality: Ensure test files that contain counts or arrays match the actual files on disk.
Add files → update assertions: When adding docs, features, or any counted resource, update the test assertion arrays in the same commit.
CI failures → check assertions first: Verify test assertion arrays align with the filesystem before debugging complex failures.

Quick Start

Update related tests in the same commit whenever you change an API.

Frequently Asked Questions about test-discipline

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

FAQPage Schema

Why do my CI tests fail after API changes even when the code passes locally?▼

CI tests fail after API changes when test assertions are not updated in the same commit to reflect the new on-disk reality. Validating assertion arrays against the actual filesystem state prevents these blockers and flaky regressions.

How do I keep test suites in sync when modifying function signatures?▼

To keep test suites in sync when modifying function signatures, update the corresponding tests and assertion arrays within the same commit to match the exported API changes and current disk state.

What is the best way to prevent flaky test failures when adding new files?▼

The best way to prevent flaky test failures when adding files is to update test assertion arrays in the same commit, ensuring expected counts and arrays match the actual files on disk.

When should I check test assertions during the code review process?▼

You should check test assertions during code reviews when APIs change, verifying that test updates align with on-disk reality and documenting anti-patterns to mitigate regression risk.

Does updating tests in the same commit as API changes prevent CI regressions?▼

Yes, updating tests in the same commit as API changes prevents CI regressions by enforcing test-suite synchronization and ensuring assertions match the actual state on disk.

What are common anti-patterns for test assertions after changing public interfaces?▼

Common anti-patterns include leaving assertion arrays unvalidated against disk state or failing to update tests in the same commit as public interface changes, both of which increase regression risk.