run-affected-test-file-in-isolation-and-in-co-run-with-its-test- v1A

Immutable. This exact content is served forever at /api/v1/blob/82a618e62b2d1411.

---
name: run-affected-test-file-in-isolation-and-in-co-run-with-its-test-
description: run affected test file in isolation AND in co-run with its test-suite peers after mock cleanup changes
generated_from_knowledge:
  - 1b7d37db-81d1-4b0d-90ab-85a7e68f90bf
source_knowledge_ids:
  - 1b7d37db-81d1-4b0d-90ab-85a7e68f90bf
generated_at: 2026-07-06T14:02:41.500Z
confidence: 0.60
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. -->

# run affected test file in isolation AND in co-run with its test-suite peers after mock cleanup changes

## Trigger

- (no explicit trigger metadata; cluster derived from category/tags)

## Required Procedure

- run affected test file in isolation AND in co-run with its test-suite peers after mock cleanup changes

## Forbidden Shortcuts

- add top-level afterEach mock.restore without verifying co-run with sibling test files

## Delegation Template

When delegating a task affected by this skill, include:

```
SKILLS: file:.opencode/skills/generated/run-affected-test-file-in-isolation-and-in-co-run-with-its-test-/SKILL.md
```

## Reviewer Checks

- Verify each required action above appears in the diff.

## Test Engineer Checks

- Add or update tests covering the trigger condition and the forbidden shortcut.

## Source Knowledge IDs

- 1b7d37db-81d1-4b0d-90ab-85a7e68f90bf — In Bun, adding afterEach(() => mock.restore()) to fix mock isolation can break co-run with sibling test files that depend on leaked mock state. Always verify both isolated and co-run behavior before committing mock cleanup changes.