test-discipline

Update tests in sync with API changes and disk data.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures that tests remain accurate and functional when APIs change or data on disk is updated, preventing CI breaks and promoting code quality.

Core Features & Use Cases

  • API Change Tracking: Updates tests in the same commit as API changes to maintain test integrity.
  • Data Synchronization: Ensures that test assertions match the actual data on disk.
  • Use Case: When you update a function signature, this Skill prompts you to update the corresponding tests in the same commit, preventing CI failures due to stale tests.

Quick Start

Run the skill to check for test integrity after updating an API or adding new files.

Frequently Asked Questions about test-discipline

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

FAQPage Schema
How do I keep tests updated when API changes happen in my codebase?

To keep tests updated with API changes, you need a mechanism that tracks function signature modifications and prompts you to update corresponding tests within the same commit, preventing CI failures.

What is test integrity in a CI/CD pipeline?

Test integrity in a CI/CD pipeline means ensuring that test assertions accurately match the actual data on disk and remain functional when APIs change, preventing pipeline breaks and promoting code quality.

How do I synchronize test assertions with disk reality after file updates?

To synchronize test assertions with disk reality, you must monitor file system changes and apply updates to your tests so they reflect the actual data on disk, ensuring assertions do not fail due to stale data.

Why do my CI pipelines break after updating function signatures?

CI pipelines break after updating function signatures because the corresponding tests are often not updated in the same commit, leaving stale tests that fail against the new API changes.

Can I use scripts to monitor API and file system changes for test accuracy?

Yes, you can use scripts to monitor API and file system changes, which helps maintain test accuracy by prompting updates whenever data on disk or function signatures are modified.

What is the best way to prevent stale tests from breaking continuous integration?

The best way to prevent stale tests from breaking continuous integration is to enforce test integrity by updating tests in the same commit as API changes, ensuring assertions match disk reality.