skills.rest
lbouriez
lbouriezCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

test-discipline

Update tests in the same commit when public APIs change.

Updated Mar 27, 2026
Search Tags:#automation#quality-assurance#ci#api-changes#update-tests#test-assertions
One-click install
npx skills add https://github.com/lbouriez/Squad-Templates --skill test-discipline-lbouriez
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-discipline
Source: https://github.com/lbouriez/Squad-Templates/tree/main/Nectari-Devops-Squad/.copilot/skills/test-discipline
Command: npx skills add https://github.com/lbouriez/Squad-Templates --skill test-discipline-lbouriez

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When APIs or public interfaces change, tests must be updated in the same commit to avoid CI failures.

Core Features & Use Cases

  • Update tests in the same commit when API changes occur to keep codebase aligned with new interfaces.
  • Ensure test assertions reflect actual filesystem and API state to prevent flaky CI.
  • CI-friendly workflow: automatically review and adjust tests when APIs evolve.

Quick Start

Update tests in the same commit whenever you modify a public API and run the test suite to verify synchronization.

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 in sync with API changes in the same commit?▼

To keep tests in sync with API changes, you update test assertions and generated documentation in the same commit where public interfaces are modified. This consistency check prevents flaky CI failures and ensures the codebase stays aligned with new APIs.

Why do my CI pipeline tests fail after updating public interfaces?▼

CI pipeline tests fail after updating public interfaces because test assertions and generated documentation are not updated in the same commit. Ensuring test assertions reflect actual filesystem and API state prevents these flaky CI results.

What is the best way to automate test updates for API changes in pull requests?▼

The best way to automate test updates for API changes in pull requests is to enforce a CI-friendly workflow that automatically reviews and adjusts test suites when APIs evolve. This ensures test assertions reflect actual disk reality and new interfaces.

When should I update test assertions that depend on file counts?▼

You should update test assertions that depend on file counts whenever public APIs or interfaces change in the same commit. Validating that generated documentation and assertions reflect actual filesystem state keeps your test suite accurate and prevents CI failures.

Can I use this approach to validate CI results for generated documentation?▼

Yes, you can validate CI results for generated documentation by ensuring it stays in sync with disk reality. Updating tests and documentation in the same commit when APIs change guarantees that assertions reflect actual filesystem and API state.

Related Skills

Explore More Software Engineering Skills→
DeDuvaDeDuva
1

test-discipline

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

Community
Intermediate
ronniegeraghtyronniegeraghty
3

test-discipline

Update test assertions in the same commit as API changes.

Community
Intermediate
jperezdelrealjperezdelreal

test-discipline

Enforce in-commit test updates when APIs or public interfaces change.

Community
Intermediate
Izak90Izak90

test-discipline

Update tests in the same commit after API changes to prevent CI failures.

Community
Intermediate