run-affected-test-file-in-isolation-and-in-co-run-with-its-test-
SkillFiles & storagerun affected test file in isolation AND in co-run with its test-suite peers after mock cleanup changes
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 run-affected-test-file-in-isolation-and-in-co-run-with-its-test- skill
What this skill tells your AI
The instructions your AI receives, as published by zaxbyhub/opencode-swarm in .opencode/skills/generated/run-affected-test-file-in-isolation-and-in-co-run-with-its-test/SKILL.md and read by ahel’s review.
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.
Signals
- GitHub stars
- 467
- Forks
- 51
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
run-affected-test-file-in-isolation-and-in-co-run-wi-1nsdrh8- Source
- github.com/zaxbyhub/opencode-swarm