agentleFS
Sign inStart free
kubefleet-devkubefleet-dev/kubefleet/.github/skills/test-discipline/SKILL.md

test-discipline

Skill164 starsChanged 6 days agoApache-2.0View on GitHub

Update tests when changing APIs — no exceptions

15 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use squad-commands, architectural-proposals and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Microsoft AzureSkill

    squad-commands

    Categorized catalog of common Squad operations. Coordinator reads this file and presents it as an interactive menu when the user asks for available commands or help.

    Also in 4 projects that use this

  • Microsoft AzureSkill

    architectural-proposals

    How to write comprehensive architectural proposals that drive alignment before code is written

    Also in 3 projects that use this

  • +10 more from Azure

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

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

    line 11
  2. Distinctive:

    API changes → test updates (same commit): If you change a function signature, public interface, or exported API, update the corresponding …

    line 15
  3. Very specific:

    Test assertions → disk reality: When test files contain expected counts (e.g., EXPECTED_FEATURES, EXPECTED_SCENARIOS), they must match the …

    line 16
  4. Distinctive:

    Add files → update assertions: When adding docs pages, features, or any counted resource, update the test assertion array in the same commit

    line 17
  5. Distinctive:

    CI failures → check assertions first: Before debugging complex failures, verify test assertion arrays match filesystem state

    line 18
  6. Distinctive:

    Test says "expected 7 files" but disk has 25 (assertion staleness)

    line 30

“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Context

When APIs or public interfaces change, tests must be updated in the same commit. When test assertions reference file counts or expected arrays, they must be kept in sync with disk reality. Stale tests block CI for other contributors.

Patterns

  • API changes → test updates (same commit): If you change a function signature, public interface, or exported API, update the corresponding tests before committing
  • Test assertions → disk reality: When test files contain expected counts (e.g., EXPECTED_FEATURES, EXPECTED_SCENARIOS), they must match the actual files on disk
  • Add files → update assertions: When adding docs pages, features, or any counted resource, update the test assertion array in the same commit
  • CI failures → check assertions first: Before debugging complex failures, verify test assertion arrays match filesystem state

Examples

✓ Correct:

  • Changed auth API signature → updated auth.test.ts in same commit
  • Added distributed-mesh.md to features/ → added 'distributed-mesh' to EXPECTED_FEATURES array
  • Deleted two scenario files → removed entries from EXPECTED_SCENARIOS

✗ Incorrect:

  • Changed spawn parameters → committed without updating casting.test.ts (CI breaks for next person)
  • Added built-in-roles.md → left EXPECTED_FEATURES at old count (PR blocked)
  • Test says "expected 7 files" but disk has 25 (assertion staleness)

Anti-Patterns

  • Committing API changes without test updates ("I'll fix tests later")
  • Treating test assertion arrays as static (they evolve with content)
  • Assuming CI passing means coverage is correct (stale assertions can pass while being wrong)
  • Leaving gaps for other agents to discover

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free