update or delete tests that assert intentionally removed behavior
SkillDev toolsupdate or delete tests that assert intentionally removed behavior
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the update or delete tests that assert intentionally removed behavior skill
What this skill tells your AI
The instructions your AI receives, as published by zaxbyhub/opencode-swarm in .opencode/skills/generated/update-or-delete-tests-that-assert-intentionally-removed-behavio/SKILL.md and read by ahel’s review.
Trigger
- (no explicit trigger metadata; cluster derived from category/tags)
Required Procedure
- update or delete tests that assert intentionally removed behavior
- verify no test asserts behavior the changeset deliberately removes
Forbidden Shortcuts
- (none recorded)
Delegation Template
When delegating a task affected by this skill, include:
SKILLS: file:.opencode/skills/generated/update-or-delete-tests-that-assert-intentionally-removed-behavio/SKILL.md
Reviewer Checks
- grep test files for removed code patterns (e.g. Date.now() timestamps, deprecated API calls)
- run full test suite after changes and classify every failure as regression vs stale-test
Test Engineer Checks
- Add or update tests covering the trigger condition and the forbidden shortcut.
Source Knowledge IDs
- ca60f911-c1d4-4fb1-8245-44bf6cf95045 — When intentionally removing a code path, update or delete all tests asserting the old behavior in the same changeset — stale assertions that validate removed behavior count as test failures, not expected regressions.
Signals
- GitHub stars
- 467
- Forks
- 51
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
update-or-delete-tests-that-assert-intentionally-rem-177qsc2- Source
- github.com/zaxbyhub/opencode-swarm