test-discipline

Update tests when APIs change and synchronize assertions with the file system.

Updated May 10, 2026
One-click install
npx skills add https://github.com/AshleyHollis/agentic-identity-lab --skill test-discipline-ashleyhollis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-discipline
Source: https://github.com/AshleyHollis/agentic-identity-lab/tree/main/.copilot/skills/test-discipline
Command: npx skills add https://github.com/AshleyHollis/agentic-identity-lab --skill test-discipline-ashleyhollis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures that tests remain up-to-date with API changes and that test assertions match the actual file system, preventing CI issues and improving code quality.

Core Features & Use Cases

  • API Change Tracking: Automatically update tests when APIs change, ensuring test coverage is maintained.
  • Assertion Synchronization: Keep test assertions in sync with the actual file system to prevent stale tests.
  • Use Case: When you modify an API, the Skill will prompt you to update the corresponding tests in the same commit, and if you add new files, it will update the expected counts in the tests.

Quick Start

Use the test-discipline skill to update tests when you make changes to an API.

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 in sync with file system changes?

To keep test assertions in sync with the file system, this skill monitors disk reality and automatically updates expected file counts in your tests when new files are added.

How do I automatically update tests when APIs change?

To automatically update tests when APIs change, this skill monitors API modifications and prompts you to update corresponding tests within the same commit to maintain coverage.

What is the best way to prevent CI issues caused by stale tests?

Preventing CI issues caused by stale tests requires maintaining test integrity by synchronizing test assertions with actual file system states and API changes without manual intervention.

Does this test synchronization approach work without manual intervention?

Yes, this test synchronization approach works without manual intervention by automatically tracking API changes and file system states to ensure tests remain up-to-date.

When do I need to update test assertions for file system reality?

You need to update test assertions for file system reality whenever you add new files to your project, ensuring expected counts in tests match the actual disk state.