skills.rest
BedaBeda-Growth
BedaBeda-GrowthOFFICIAL
Explore all skills by this author →
GitHub

jules-e2e-fallback

Diagnose failing Jules E2E branches, patch code, and re-dispatch Playwright runs.

Updated Feb 3, 2026
Search Tags:#vitest#debugging#e2e#playwright#ci-cd#jules#branch-management
One-click install
npx skills add https://github.com/BedaBeda-Growth/bedabeda-growth-site --skill jules-e2e-fallback
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: jules-e2e-fallback
Source: https://github.com/BedaBeda-Growth/bedabeda-growth-site/tree/main/skills/jules-e2e-fallback
Command: npx skills add https://github.com/BedaBeda-Growth/bedabeda-growth-site --skill jules-e2e-fallback

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When Jules E2E runs into persistent failures or timeouts, this skill provides a fast-path to pull the failing branch, diagnose the issue, apply fixes locally, and re-run E2E verification to maintain development velocity.

Core Features & Use Cases

  • Diagnose failing Jules sessions and retrieve logs to identify root causes.
  • Pull, checkout, and fix the failing branch locally, updating tests or UI as needed.
  • Run the fast unit-test suite (Vitest) to ensure no regressions, then push fixes and re-dispatch Jules for final E2E run.
  • Provide a clean handoff back to Jules with clear success criteria and preserved branch state.

Quick Start

To begin, pull the failing branch, fix the E2E issue locally, verify unit tests green, and re-dispatch Jules for a final E2E run.

Frequently Asked Questions about jules-e2e-fallback

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

FAQPage Schema
How do I fix failing Playwright E2E tests from a Jules branch?▼

To fix failing Playwright E2E tests, pull the failing Jules branch, diagnose the root cause from logs, patch local code or UI components, and re-dispatch Jules for a final run.

What is the workflow to diagnose and patch a failing Jules E2E session?▼

The Jules E2E workflow involves pulling the failing branch, diagnosing logs for root causes, applying local fixes, validating with Vitest, and pushing a clean branch for re-run.

Do I need to run Vitest before re-dispatching Jules for an E2E run?▼

Yes, you must run Vitest to ensure unit tests are green before re-dispatching Jules, enforcing safe guardrails to prevent regressions during the final Playwright run.

What tools are required to debug and restore Jules E2E branches locally?▼

Debugging and restoring Jules E2E branches requires access to git, Playwright and Vitest tooling, and Jules commands to pull, patch, validate, and re-dispatch the failing branch.

What's the best way to handle persistent E2E timeouts in CI-CD pipelines?▼

Handling persistent E2E timeouts involves pulling the failing branch, applying local patches to UI or tests, verifying with Vitest, and re-dispatching Jules to restore pipeline velocity.

Related Skills

Explore More Software Engineering Skills→
BedaBeda-GrowthBedaBeda-Growth

local-advance

Batch merge PRs locally and run Vitest unit tests before dispatching Playwright E2E.

Official
Advanced
Chachamaru127Chachamaru127
3.0k

verify

Verify builds, recover from errors, and apply review fixes across CI pipelines.

Community
Intermediate
Thanh-aperoThanh-apero
1

web-testing

Automate web testing with Playwright, Vitest, k6, and Lighthouse.

Community
Advanced
BedaBeda-GrowthBedaBeda-Growth

finish-pipeline

Coordinate Jules sessions, PR merges, and local tests for a stable test branch.

Official
Advanced