Skip to main content
skill CX Codex

run-relevant-tests-after-logic-changes — Claude Code skill

run-relevant-tests-after-logic-changes enforces running target test suites after code changes and forbids reporting completion until all checks pass.

MIT ★ 539 updated 2026-10-29

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add ZaxbyHub/opencode-swarm --skill run-relevant-tests-after-logic-changes -a claude-code
Open on GitHub

What run-relevant-tests-after-logic-changes does

This skill instructs the agent to run relevant test suites whenever logic changes. Passing linters or formatters is not enough; the assistant must confirm tests actually pass before concluding work.

Boundary-condition updates such as swapping > for >= frequently break tests expecting older behavior. The skill specifically targets these regressions by demanding proof of passing test runs directly in the workflow.

It also provides concrete checklist items for reviewers and test engineers to ensure verification steps appear in diffs and trigger conditions receive test coverage.

What it helps with

  • prevent the agent from claiming success before executing tests
  • catch regressions caused by boundary condition edits
  • require actual test suite execution instead of lint checks alone
  • provide review checks for verifying test execution inside the diff

Example prompts for the agent

  • I adjusted the discount logic in the checkout service, run the relevant tests and confirm they pass
  • Update the boundary comparisons in the validator and verify the suite before reporting completion
  • Refactor the order calculation logic and execute the related test suite

How to install run-relevant-tests-after-logic-changes

1Skills CLI (Vercel)

npx skills add ZaxbyHub/opencode-swarm --skill run-relevant-tests-after-logic-changes -a claude-code

2Manually: put the files in place

~/.claude/skills/run-relevant-tests-after-logic-changes/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/run-relevant-tests-after-logic-changes/

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

Questions about run-relevant-tests-after-logic-changes

How to install run-relevant-tests-after-logic-changes in Claude Code?

Run npx skills add ZaxbyHub/opencode-swarm --skill run-relevant-tests-after-logic-changes -a claude-code. Alternatively, place the file directly at ~/.claude/skills/run-relevant-tests-after-logic-changes/SKILL.md.

What does run-relevant-tests-after-logic-changes do?

It forces the agent to execute affected test suites after modifying behavioral code and confirm passing status before declaring the task done.

Why does this skill highlight boundary condition edits?

Modifying operators such as > or >= often breaks tests relying on earlier semantics, making full test execution mandatory.

Source text

SKILL.md · MIT
---
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.

© ZaxbyHub · MIT · ZaxbyHub/opencode-swarm

Similar skills

All skills for Testing and QA →

From the same set121

The whole set →
run-failing-tests-immediately-after-test-gate-failure run-failing-tests-immediately-after-test-gate-failure is a Claude Code skill that makes the agent rerun failing tests when test_gate fails and repair the root cause before claiming the task is done. CX Codex +1 ★ 539repo stars run-tests-on-the-unmodified-codebase-before-starting-to-establis run-tests-on-the-unmodified-codebase-before-starting-to-establis is a Claude Code skill that requires running tests on untouched code before edits, recording failures to distinguish them from new regressions. CX Codex +1 ★ 539repo stars engineering-conventions The engineering-conventions skill sets a workflow for changes that could affect opencode-swarm’s engineering invariants. Use it when editing architecture, tests, or session state. CX Codex +1 ★ 539repo stars include-test-files-that-assert-on-behavior-being-changed-in-decl include-test-files-that-assert-on-behavior-being-changed-in-decl is a Claude Code skill that puts tests for changed behaviour in scope, so an agent fixes code alongside its checks. CX Codex +1 ★ 539repo stars pr-review-fix The pr-review-fix skill checks PR review findings against the current branch and fixes confirmed issues. Use it to work through reviewer comments, bot feedback, or a CI review summary. CX Codex +1 ★ 539repo stars verify-skill-mirror-pairs-exist-in-both-opencode-skills-and-clau verify-skill-mirror-pairs-exist-in-both-opencode-skills-and-clau is a Claude Code skill that checks generated skill trees for missing mirrors and folder-slug mismatches. CX Codex +1 ★ 539repo stars isolate-the-specific-failure-mode-before-proposing-a-fix isolate-the-specific-failure-mode-before-proposing-a-fix is a Claude Code skill that identifies the cause of each test failure before fixes, keeping unrelated failures in separate patches. CX Codex +1 ★ 539repo stars run-test-suite-after-registration-changes The run-test-suite-after-registration-changes skill calls for running the test suite after registration edits and checking that each registration point stays in sync. Use it when changing skill files and their manifests. CX Codex +1 ★ 539repo stars

Project sponsors

Companies that keep this analytics open