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

local-advance

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

Updated Feb 3, 2026
Search Tags:#git#vitest#e2e#playwright#pr#local#unit-tests
One-click install
npx skills add https://github.com/BedaBeda-Growth/bedabeda-growth-site --skill local-advance
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: local-advance
Source: https://github.com/BedaBeda-Growth/bedabeda-growth-site/tree/main/skills/local-advance
Command: npx skills add https://github.com/BedaBeda-Growth/bedabeda-growth-site --skill local-advance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables engineers to batch open PRs locally, run unit tests natively, and only dispatch cloud-based Playwright E2E tests once local validation is green, reducing feedback cycles and debugging time.

Core Features & Use Cases

  • Batch selection and checkout of up to ~5 PRs for integration testing.
  • Local branch creation, sequential merges, and self-healing test failures.
  • Local unit testing with Vitest and guided self-healing before handing off to Jules for E2E Playwright tests.

Quick Start

Bundle up to five open PRs, merge them locally, run unit tests until green, and then dispatch Jules for higher-level E2E testing.

Frequently Asked Questions about local-advance

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

FAQPage Schema
How do I batch merge multiple PRs locally before running E2E tests?▼

Batch merge multiple PRs locally by selecting up to five open PRs, checking them out sequentially into a local branch, and running native Vitest unit tests to validate integration before dispatching cloud-side Playwright E2E tests.

Can I run Vitest unit tests on multiple merged PRs before triggering Playwright E2E?▼

Yes, you can run Vitest unit tests on multiple merged PRs locally. The workflow validates changes with native unit testing and provides guided self-healing for failures before handing off to Jules for remote Playwright E2E orchestration.

Do I need the gh CLI to batch checkout and merge pull requests?▼

Yes, you need the gh CLI to batch checkout and merge pull requests. The local PR batching and git operations require local Git, the gh CLI, and a Vitest-compatible test environment to execute the integration workflow successfully.

What is the best way to validate PR integration without consuming cloud E2E resources?▼

The best way to validate PR integration without consuming cloud E2E resources is to batch merge PRs locally and run Vitest unit tests natively, dispatching cloud-based Playwright E2E tests via Jules only once local validation is green.

Why run local unit tests before dispatching Playwright E2E for open PRs?▼

Run local unit tests before dispatching Playwright E2E to reduce feedback cycles and debugging time. Local Vitest validation catches integration issues early, ensuring cloud-side E2E orchestration via Jules only runs on verified code.

Related Skills

Explore More Software Engineering Skills→
NeoLabs-SystemsNeoLabs-Systems
23

github-pr-workflow

Automate GitHub pull request workflows from branch creation to merging.

Official
Advanced
BedaBeda-GrowthBedaBeda-Growth

jules-e2e-fallback

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

Official
Advanced
initialyzeinitialyze

Testing Blocks

Validate code changes in AEM Edge Delivery projects with Vitest and Playwright.

Official
Advanced
shekerkammashekerkamma

ship

Automate git-based code shipping with tests, versioning, and pull requests.

Community
Advanced