skip-failed-test

Analyze failing tests and create GitHub issues for unrelated skips.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/drdanmaggs/rocket-fuel --skill skip-failed-test
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skip-failed-test
Source: https://github.com/drdanmaggs/rocket-fuel/tree/main/internal/plugin/skills/skip-failed-test
Command: npx skills add https://github.com/drdanmaggs/rocket-fuel --skill skip-failed-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Handle test failures blocking PR progress when tests appear unrelated to current work. Use when tests fail on your branch or in CI but seem unrelated to your changes. Analyzes connection between failing test and your work using codebase exploration and sequential thinking. If unrelated and flaky, skips test and creates documented GitHub issue. If related, routes to test-fixer skill. Pragmatic workflow to keep PRs moving without ignoring real issues. Auto-triggers on phrases like "test is now failing", "different test failing", "blocking PR", "unrelated test failure", "CI failing on", or when multiple tests fail during PR work.

Core Features & Use Cases

  • Fast-path screening for obviously unrelated failures (CI-only or domain mismatch scenarios).
  • Deep analysis to decide whether to route to test-fixer or skip with documentation.
  • Automatic GitHub issue creation detailing context when a test is skipped.
  • Routing integration to /test-fixer when a link is plausible.

Quick Start

Invoke skip-failed-test on the failing PR to triage the test and route to test-fixer when a plausible link is found.

Frequently Asked Questions about skip-failed-test

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I skip failing tests that are blocking my PR in CI?

This skill triages failing CI tests by analyzing whether they are unrelated, flaky, or related to your current changes. If unrelated, it skips the test and creates a documented GitHub issue to unblock your PR.

What happens when a failing test is related to my code changes?

When a failing test is related to your code changes, the skill routes the failure to the test-fixer skill for resolution. This ensures actual code regressions are addressed rather than skipped during PR triage.

How does CI test triage determine if a failing test is flaky or unrelated?

Test triage uses codebase exploration and sequential thinking to analyze the connection between failing tests and your current changes. It applies fast-path screening for obvious failures and deep analysis for plausible links.

When should I use a workflow to skip unrelated test failures?

Use a test-skipping workflow when tests fail on your branch or in CI but appear disconnected from your current changes. It auto-triggers on phrases like 'blocking PR' or 'unrelated test failure' to unblock progress.

Does the skill document skipped tests in GitHub?

Yes, the skill automatically creates a GitHub issue detailing the context whenever a test is skipped. This ensures skipped tests are documented and tracked for future resolution rather than being silently ignored.