test-discipline

To prevent CI failures, you can keep tests in sync with API changes by running the test-discipline skill. It monitors API modifications and automatically updates corresponding test assertions to match the actual files on disk.

Stale tests cause CI breaks because test assertions no longer match the updated public API or file system state. Synchronizing test assertions ensures they accurately reflect new API modifications and prevents unexpected pipeline failures.

You need to update test assertions to match the file system state whenever a public API is modified. This ensures that your software development workflow maintains test integrity and avoids running outdated assertions.

Yes, tracking API changes works without external dependencies. The skill operates independently using scripts to monitor public interface modifications and synchronize test updates directly within your existing software engineering workflow.

The best way to automatically update tests when APIs change is to run the test-discipline skill. It tracks public interface modifications and directly updates corresponding test files to ensure test integrity and prevent CI breaks.

Using scripts for test synchronization is limited to tracking API changes and updating test assertions on disk. It does not generate new test cases from scratch but ensures existing tests remain accurate when public interfaces are modified.