| name | update-or-delete-tests-that-assert-intentionally-removed-behavio |
| description | update or delete tests that assert intentionally removed behavior |
| generated_from_knowledge | ["ca60f911-c1d4-4fb1-8245-44bf6cf95045"] |
| source_knowledge_ids | ["ca60f911-c1d4-4fb1-8245-44bf6cf95045"] |
| generated_at | 2026-07-14T05:31:49.191Z |
| confidence | 0.83 |
| status | active |
| version | 1 |
| skill_origin | generated |
update or delete tests that assert intentionally removed behavior
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
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.