Skip to main content
skill CX Codex

update-or-delete-tests-that-assert-intentionally-removed-behavio

update-or-delete-tests-that-assert-intentionally-removed-behavio is a Claude Code skill for revising or removing tests of deliberately removed behavior. It applies to code changes that retire a code path.

MIT ★ 539 updated 2026-10-29

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add ZaxbyHub/opencode-swarm --skill update-or-delete-tests-that-assert-intentionally-removed-behavio -a claude-code
Open on GitHub

What update-or-delete-tests-that-assert-intentionally-removed-behavio does

The skill checks whether tests still expect behavior that the code change intentionally removes. It can guide edits to those tests or their deletion, and calls out searches for traces such as Date.now() or deprecated API calls.

Run the full test suite after the change, then sort each failure into a regression or a stale assertion. When delegating affected work in OpenCode, include .opencode/skills/generated/update-or-delete-tests-that-assert-intentionally-removed-behavio/SKILL.md.

What it helps with

  • find tests that still assert a removed code path
  • revise stale expectations after a behavior change
  • sort test-suite failures into regressions and stale assertions

Example prompts for the agent

  • Remove this code path and revise tests that still expect its old behavior.
  • Find tests that assert removed Date.now() calls or deprecated APIs.
  • Run the full test suite and classify each failure as a regression or stale assertion.

How to install update-or-delete-tests-that-assert-intentionally-removed-behavio

1Skills CLI (Vercel)

npx skills add ZaxbyHub/opencode-swarm --skill update-or-delete-tests-that-assert-intentionally-removed-behavio -a claude-code

2Manually: put the files in place

~/.claude/skills/update-or-delete-tests-that-assert-intentionally-removed-behavio/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/update-or-delete-tests-that-assert-intentionally-removed-behavio/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about update-or-delete-tests-that-assert-intentionally-removed-behavio

How do I install update-or-delete-tests-that-assert-intentionally-removed-behavio in Claude Code?

Run npx skills add ZaxbyHub/opencode-swarm --skill update-or-delete-tests-that-assert-intentionally-removed-behavio -a claude-code. The skill file is placed at ~/.claude/skills/update-or-delete-tests-that-assert-intentionally-removed-behavio/SKILL.md.

What does update-or-delete-tests-that-assert-intentionally-removed-behavio do?

It helps revise or remove tests that still expect deliberately retired behavior, then classify failures after the full test suite runs.

What patterns can it look for in tests?

It can search for traces of removed code, including Date.now() timestamps and deprecated API calls.

Source text

SKILL.md · MIT
---
name: update-or-delete-tests-that-assert-intentionally-removed-behavio
description: update or delete tests that assert intentionally removed behavior
metadata:
  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
---

<!-- generated by opencode-swarm skill-generator. Do not edit by hand; edits will be preserved on regeneration only with controlled update mode. -->

# 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

- (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.

© ZaxbyHub · MIT · ZaxbyHub/opencode-swarm

Similar skills

All skills for Testing and QA →

From the same set121

The whole set →
issue-tracer issue-tracer takes a bug from reproduction to a PR-ready fix: locates the cause, plans the change, and puts it through critic review. CX Codex +1 ★ 539repo stars confirm-failures-are-causally-linked-to-the-task-before-reportin confirm-failures-are-causally-linked-to-the-task-before-reportin is a Claude Code skill that separates pre-existing test failures from new regressions before rejecting work. CX Codex +1 ★ 539repo stars writing-tests writing-tests sets test-authoring rules for the opencode-swarm repository. Use it before changing tests that involve mocks, temporary paths, or regression checks. CX Codex +1 ★ 539repo stars run-affected-test-file-in-isolation-and-in-co-run-with-its-test- run-affected-test-file-in-isolation-and-in-co-run-with-its-test- is a Claude Code skill that makes the agent run tests in isolation and with sibling files after mock cleanup changes. CX Codex +1 ★ 539repo stars use-internals-di-seam-pattern-for-test-injectable-functions use-internals-di-seam-pattern-for-test-injectable-functions is a Claude Code skill that uses _internals as a DI seam and checks mock isolation in combined Bun test runs. CX Codex +1 ★ 539repo stars worktree-retry-cleanup worktree-retry-cleanup is a Claude Code skill that cleans up a swarm worktree lane before a task is dispatched again. CX Codex +1 ★ 539repo stars swarm Enables a rigorous swarm-style posture with parallel searches, visible plan updates, and dual review gates for code changes. CX Codex +1 ★ 539repo stars research-first The research-first skill checks current documentation and discussions before tracing code when an issue depends on an external framework, tool, or platform. For repo-local questions, it searches the repository instead. CX Codex +1 ★ 539repo stars

Project sponsors

Companies that keep this analytics open