test-discipline

Update tests to align with changed APIs and disk state in commits.

1|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/DeDuva/squad --skill test-discipline-deduva
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-discipline
Source: https://github.com/DeDuva/squad/tree/main/packages/squad-sdk/templates/skills/test-discipline
Command: npx skills add https://github.com/DeDuva/squad --skill test-discipline-deduva

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Update tests when APIs or public interfaces change to ensure test suites stay in sync with the real disk state and commit boundaries.

Core Features & Use Cases

  • Sync test assertions with API changes: update corresponding tests in the same commit so CI remains green.
  • Disk-reality alignment: ensure tests reflect the actual files, counts, and structures on disk.
  • Prevent CI regressions: avoid flaky failures by keeping tests and data in lockstep when projects evolve.

Quick Start

Update tests in the same commit whenever APIs change to ensure test assertions reflect disk reality.

Frequently Asked Questions about test-discipline

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

FAQPage Schema
How do I update test assertions when API changes break my CI pipeline?

You can sync test assertions with disk reality by updating tests in the same commit as API changes, ensuring assertions accurately reflect actual files, counts, and structures on disk to prevent flaky CI failures.

Why do my test suites fail after modifying public interfaces and adding new files?

Tests fail after modifying public interfaces because existing assertions depend on outdated disk state, requiring you to update related test data and assertions in the same commit to prevent flaky CI regressions.

What is the best way to keep tests aligned with filesystem reality across commits?

The best way to align tests with filesystem reality is to update corresponding test assertions and data in the same commit whenever API changes occur, ensuring tests reflect actual files and structures on disk.

Do I need to update related test data in the same commit when changing APIs?

Yes, updating related test data in the same commit as API changes is required to keep test assertions synchronized with actual disk state and prevent CI regressions across evolving project boundaries.