finish-pipeline

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

Updated Feb 3, 2026

Search Tags:#orchestration #pipeline #playwright #unit-tests #jules #branch-management #ci-testing

Ready to run

npx skills add https://github.com/BedaBeda-Growth/bedabeda-growth-site --skill finish-pipeline

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: finish-pipeline
Source: https://github.com/BedaBeda-Growth/bedabeda-growth-site/tree/main/skills/finish-pipeline
Command: npx skills add https://github.com/BedaBeda-Growth/bedabeda-growth-site --skill finish-pipeline

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This meta-orchestrator skill coordinates the repo's completion flow by waiting for Jules sessions, merging into the test branch, running the unit test suite until green, and dispatching the final Playwright E2E run to Jules. It explicitly avoids touching the main branch, requiring a controlled pre-production path.

Core Features & Use Cases

Repo-scoped orchestration: coordinates check-jules-status, jules-merge-verify, local unit tests, and final Playwright dispatch in a single repo.
Branch safety guardrails: ensures changes land only in ci-testing-verify or staging, never in main.
Self-healing loop readiness: supports running tests until 100% green and retrying fixes in place.
Hands-off handoff: automates handoff to Jules for E2E validation after local readiness.

Quick Start

Trigger the finish-pipeline workflow for the current repository to start the end-to-end finish orchestration.

Frequently Asked Questions about finish-pipeline

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

FAQPage Schema

How do I orchestrate a finish pipeline for automated testing without touching the main branch?▼

Finish pipeline orchestration coordinates Jules sessions, PR merges, and local test self-healing to ensure a stable test branch. It enforces branch usage, routing changes to ci-testing-verify or staging, and automates checks without touching main.

What is the best way to run unit tests until green before dispatching Playwright E2E runs?▼

Use a finish pipeline to run your unit test suite in a self-healing loop until 100% green, then automatically hand off to Jules for final Playwright E2E dispatch. This hands-off handoff ensures local readiness before E2E validation.

Can I use finish-pipeline to merge changes into staging instead of ci-testing-verify?▼

Yes, finish-pipeline supports both ci-testing-verify and staging branches for pre-production paths. The branch safety guardrails ensure changes land only in these controlled branches, explicitly avoiding the main branch.

How does Jules session coordination work within a repo-scoped finish workflow?▼

Jules session coordination waits for active sessions to complete, verifies PR merges into the test branch, and dispatches the final Playwright E2E run. It spans the workflow from check-jules-status through final E2E validation.

Why does my finish pipeline require explicit final verification before deploying?▼

Explicit final verification is required to ensure the test branch remains stable and fully validated before any deployment. The pipeline automates test runs and E2E dispatch but mandates a controlled pre-production path for safety.