skills.rest
endorhq
endorhqOFFICIAL
Explore all skills by this author →
Website𝕏@endorhqGitHub

fp-fix

Diagnose and fix failing E2E tests according to E2E_TESTS.md specifications.

6|Updated Mar 6, 2026
Search Tags:#code quality#automation#testing#debugging#e2e#ai agents
One-click install
npx skills add https://github.com/endorhq/flightplanner --skill fp-fix
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fp-fix
Source: https://github.com/endorhq/flightplanner/tree/main/skills/fp-fix
Command: npx skills add https://github.com/endorhq/flightplanner --skill fp-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of maintaining robust end-to-end (E2E) test suites by automatically diagnosing and fixing failing tests, ensuring the reliability of AI agent workflows.

Core Features & Use Cases

  • Automated Failure Diagnosis: Identifies the root cause of E2E test failures, categorizing them as test bugs, stale tests, environment issues, or flaky tests.
  • Targeted Test Repair: Modifies test implementations to resolve identified issues, strictly adhering to the E2E_TESTS.md spec as the source of truth.
  • Use Case: When an AI agent's E2E tests begin failing due to a recent code change, this Skill can automatically pinpoint the faulty test, understand the discrepancy between the test and the spec, and apply the necessary fix to the test implementation, restoring the test suite's green status.

Quick Start

Use the fp-fix skill to fix any failing E2E tests in the current project.

Frequently Asked Questions about fp-fix

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

FAQPage Schema
How do I automatically fix failing end-to-end tests?▼

To automatically fix failing end-to-end tests, you can use a diagnostic tool that runs your tests, categorizes failures as test bugs or stale tests, and applies targeted corrections to the test implementations.

Why does my E2E test suite fail after a recent code change?▼

E2E test suites fail after code changes due to test bugs, stale tests, environmental problems, or flakiness; diagnosing the discrepancy between the test and the specification pinpoints the exact cause.

How do I repair stale or flaky E2E tests without altering the master specification?▼

To repair stale or flaky tests without altering the master specification, apply targeted corrections strictly adhering to the E2E test documentation as the source of truth.

What is the best way to diagnose E2E test failures in AI agent workflows?▼

Diagnosing E2E test failures in AI agent workflows involves running red and green TDD cycles to identify root causes and automatically modifying test implementations to restore suite reliability.

Can I use automated test repair for environment issues and flakiness?▼

Yes, automated test repair can be used for environment issues and flakiness by diagnosing these specific failure categories and applying established patterns to modify the test implementations.

Related Skills

Explore More Software Engineering Skills→
RucloRuclo

/v3-test-heal

Diagnose and repair E2E test failures in OpenShift and KubeVirt environments.

Community
Advanced
changoo89changoo89
19

tdd

Execute Red-Green-Refactor cycles for test-first feature development.

Community
Intermediate
StrategicMilkStrategicMilk

Test Coverage Analysis

Identify untested code paths and generate test specifications with a JSON report.

Community
Advanced
keturkketurk
2

fix-codegen-sql

Analyze structured test results and fix SQL code generation failures.

Community
Advanced