AGENT SKILL

test-discipline

Update tests when changing APIs — no exceptions

License 许可
MIT
所属仓库
zuwasi/wazatator
最近更新
2026-10-05
Stars
★ 2
Forks
1

01 前言 Front Matter

name
test-discipline
domain
quality
source
earned (Fenster/Hockney incident, test assertion sync violations)
confidence
high
description
Update tests when changing APIs — no exceptions

03 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

04 同仓库更多 Skills

zuwasi
zuwasi/wazatator

waza-runner

Run evaluations on Agent Skills to measure their effectiveness. USE FOR: "run skill evals", "evaluate my skill", "test skill quality", "check skill triggers", "skill compliance check", "measure skill performance", "run evals on [skill-name]", "grade skill execution". DO NOT USE FOR: writing skills (use skill-authoring), improving frontmatter (use sensei), or general testing unrelated to skills.

★ 2
zuwasi
zuwasi/wazatator

waza

**WORKFLOW SKILL** - Evaluate AI agent skills using structured benchmarks with YAML specs, fixture isolation, and pluggable validators. USE FOR: run waza, waza help, run eval, run benchmark, evaluate skill, test agent, generate eval suite, init eval, compare results, score agent, agent evaluation, skill testing, cross-model comparison. DO NOT USE FOR: improving skill frontmatter (use waza dev), creating new skills from scratch (use skill-creator), token counting or budget checks (use waza tokens). INVOKES: Copilot SDK executor, mock engine, code/regex validators. FOR SINGLE OPERATIONS: use waza run directly for a single benchmark.

★ 2
zuwasi
zuwasi/wazatator

waza-interactive

Interactive workflow partner for creating, testing, and improving AI agent skills with waza. USE FOR: run my evals, check my skill, compare models, create eval suite, debug failing tests, is my skill ready, ship readiness, interpret results, improve score. DO NOT USE FOR: general coding, non-skill work, writing skill content (use skill-authoring), improving frontmatter only (use sensei).

★ 2
zuwasi
zuwasi/wazatator

code-explainer

Explains code snippets in plain English, breaking down what the code does step by step. Perfect for learning, code reviews, or documentation.

★ 2
zuwasi
zuwasi/wazatator

code-explainer

**UTILITY SKILL** - Explain code snippets, functions, and algorithms in plain language. USE FOR: explain code, what does this code do, break down this function, help me understand this, walk through this algorithm, clarify this logic, explain this snippet, describe what happens here. DO NOT USE FOR: writing new code (use code generation), fixing bugs (use debugging), refactoring (use refactoring skills), code review with action items. INVOKES: file reading tools to access code, language detection for tailored explanations. FOR SINGLE OPERATIONS: If the user just needs to see file contents, use file reading tools directly.

★ 2
zuwasi
zuwasi/wazatator

profile-test-skill

**PROFILE TEST** - A skill for testing the profile command. USE FOR: testing profile analysis, verifying structural metrics. DO NOT USE FOR: production use.

★ 2