test-discipline

Synchronize test assertions with codebase modifications and filesystem state.

Updated Apr 16, 2026

Search Tags:#automation #testing #quality assurance #refactoring #assertions #ci

Ready to run

npx skills add https://github.com/Quintenps/contactswap-agents --skill test-discipline-quintenps

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents CI failures and integration bottlenecks caused by stale tests or mismatched assertions when APIs and file structures evolve.

Core Features & Use Cases

API-Test Synchronization: Ensures function signatures and public interfaces are updated in the same commit as their corresponding tests.
Assertion Integrity: Validates that test assertions regarding file counts or expected arrays remain in sync with the actual filesystem state.
Use Case: When adding a new feature file to the repository, this Skill guides you to update the corresponding EXPECTED_FEATURES array in your test suite to prevent build failures.

Quick Start

Use the test-discipline skill to verify that all current test assertions match the existing file structure in the repository.

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 synchronized with API refactoring to prevent CI failures?▼

To keep test assertions synchronized with API refactoring, enforce atomic commit patterns where interface changes and test updates occur simultaneously, preventing CI bottlenecks caused by stale tests.

Why does adding a new feature file break my continuous integration build?▼

Adding a new feature file breaks CI builds when test assertions regarding expected file counts or arrays are not updated to match the new filesystem state. Synchronizing test suite arrays prevents these failures.

What is atomic commit pattern enforcement for test-code synchronization?▼

Atomic commit pattern enforcement for test-code synchronization requires modifying function signatures and their corresponding test assertions in the same commit, ensuring continuous integration stability during software engineering workflows.

How do I validate that test assertions match the existing file structure in my repository?▼

To validate that test assertions match the existing file structure, verify that all expected arrays and file count validations in your test suite accurately reflect the current repository state before running continuous integration pipelines.

Does this test synchronization approach work for filesystem-dependent test validations?▼

Yes, test synchronization works for filesystem-dependent test validations by ensuring assertion integrity checks that expected arrays and file counts remain in sync with the actual filesystem state during feature additions.