run-relevant-tests-after-logic-changes v1A

Immutable. This exact content never changes and is served at /api/v1/blob/a7b2fde1397c6b69.

---
name: run-relevant-tests-after-logic-changes
description: run relevant tests after logic changes
metadata:
  generated_from_knowledge: '["78334fd4-d394-41c8-a845-7f5da6e15096"]'
  source_knowledge_ids: '["78334fd4-d394-41c8-a845-7f5da6e15096"]'
  generated_at: "2026-07-14T05:31:50.518Z"
  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 relevant tests after logic changes

## Trigger

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

## Required Procedure

- run relevant tests after logic changes
- confirm test pass before reporting completion

## Forbidden Shortcuts

- (none recorded)

## Delegation Template

When delegating a task affected by this skill, include:

```
SKILLS: file:.opencode/skills/generated/run-relevant-tests-after-logic-changes/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

- 78334fd4-d394-41c8-a845-7f5da6e15096 — Run the actual test suite after behavioral changes, not just linting/formatting. Boundary-condition fixes (>, >=) often break existing tests that depend on the prior semantics.