confirm-failures-are-causally-linked-to-the-task-before-reportin skill
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.
MIT ★ 539 updated 2026-10-29
npx skills add ZaxbyHub/opencode-swarm --skill confirm-failures-are-causally-linked-to-the-task-before-reportin -a claude-codeWhat confirm-failures-are-causally-linked-to-the-task-before-reportin does
This skill guides test engineers and code reviewers in multi-agent pipelines. When a test suite fails, the agent must determine whether the failure stems directly from the new diff or existed prior to the current changes.
Reports must explicitly separate historical breakages from newly introduced regressions. Reviewers check the diff for this causal verification, while test engineers cover the trigger scenarios with dedicated test cases.
Without this rule, an agent rejects pull requests over pre-existing broken tests that fall outside the task scope.
What it helps with
- distinguish pre-existing test suite breakages from task-specific regressions
- prevent false rejections of working code in multi-agent swarms
- isolate task scope when reviewing failing test suites
Example prompts for the agent
- Inspect failing tests and verify whether they are causally linked to this diff before rejecting
- Separate pre-existing test failures from regressions introduced in this task report
How to install confirm-failures-are-causally-linked-to-the-task-before-reportin
1Skills CLI (Vercel)
npx skills add ZaxbyHub/opencode-swarm --skill confirm-failures-are-causally-linked-to-the-task-before-reportin -a claude-code2Manually: put the files in place
~/.claude/skills/confirm-failures-are-causally-linked-to-the-task-before-reportin/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/confirm-failures-are-causally-linked-to-the-task-before-reportin/
1Skills CLI (Vercel)
npx skills add ZaxbyHub/opencode-swarm --skill confirm-failures-are-causally-linked-to-the-task-before-reportin -a codex2Manually: put the files in place
.agents/skills/confirm-failures-are-causally-linked-to-the-task-before-reportin/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add ZaxbyHub/opencode-swarm --skill confirm-failures-are-causally-linked-to-the-task-before-reportin -a cursor2Manually: put the files in place
.cursor/skills/confirm-failures-are-causally-linked-to-the-task-before-reportin/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install ZaxbyHub/opencode-swarm .opencode/skills/generated/confirm-failures-are-causally-linked-to-the-task-before-reportin2Manually: put the files in place
.github/skills/confirm-failures-are-causally-linked-to-the-task-before-reportin/SKILL.md1Skills CLI (Vercel)
npx skills add ZaxbyHub/opencode-swarm --skill confirm-failures-are-causally-linked-to-the-task-before-reportin -a gemini-cli2Platform CLI
gemini skills install https://github.com/ZaxbyHub/opencode-swarm --path .opencode/skills/generated/confirm-failures-are-causally-linked-to-the-task-before-reportinManually: put the files in place
.devin/skills/confirm-failures-are-causally-linked-to-the-task-before-reportin/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add ZaxbyHub/opencode-swarm --skill confirm-failures-are-causally-linked-to-the-task-before-reportin -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about confirm-failures-are-causally-linked-to-the-task-before-reportin
How to install confirm-failures-are-causally-linked-to-the-task-before-reportin in Claude Code?
Run npx skills add ZaxbyHub/opencode-swarm --skill confirm-failures-are-causally-linked-to-the-task-before-reportin -a claude-code in your terminal.
What does confirm-failures-are-causally-linked-to-the-task-before-reportin do?
It prevents agents from rejecting code changes due to unrelated or pre-existing test failures.
How is this skill passed during task delegation?
Include SKILLS: file:.opencode/skills/generated/confirm-failures-are-causally-linked-to-the-task-before-reportin/SKILL.md in the delegation payload.
Source text
SKILL.md · MIT
--- name: confirm-failures-are-causally-linked-to-the-task-before-reportin description: confirm failures are causally linked to the task before reporting rejection metadata: generated_from_knowledge: '["820286b2-e40c-40f9-95d0-5ae2191c904f"]' source_knowledge_ids: '["820286b2-e40c-40f9-95d0-5ae2191c904f"]' generated_at: "2026-07-14T05:31:49.399Z" 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. --> # confirm failures are causally linked to the task before reporting rejection ## Trigger - (no explicit trigger metadata; cluster derived from category/tags) ## Required Procedure - confirm failures are causally linked to the task before reporting rejection - separate pre-existing failures from task-introduced regressions in test reports ## Forbidden Shortcuts - (none recorded) ## Delegation Template When delegating a task affected by this skill, include: ``` SKILLS: file:.opencode/skills/generated/confirm-failures-are-causally-linked-to-the-task-before-reportin/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 - 820286b2-e40c-40f9-95d0-5ae2191c904f — When test_engineer reports failures, verify whether they are pre-existing and unrelated to the task scope before rejecting coder work — unrelated failures should not block task completion.
© ZaxbyHub · MIT · ZaxbyHub/opencode-swarm