build-e2e-ci-ephemeral

Name: build-e2e-ci-ephemeral
Availability: InStock
Author: mwolff328-stack

Provision ephemeral Neon databases and run Playwright tests in GitHub Actions.

1|1|Updated Apr 2, 2026

Search Tags:#automation #testing #neon #playwright #github-actions #ci-cd

Ready to run

npx skills add https://github.com/mwolff328-stack/WolffClaude --skill build-e2e-ci-ephemeral

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: build-e2e-ci-ephemeral
Source: https://github.com/mwolff328-stack/WolffClaude/tree/main/scheduled-tasks/build-e2e-ci-ephemeral
Command: npx skills add https://github.com/mwolff328-stack/WolffClaude --skill build-e2e-ci-ephemeral

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill solves the issue of blocked CI access to Cloudflare-protected deployments by orchestrating an isolated, ephemeral end-to-end testing environment that runs entirely within GitHub Actions.

Core Features & Use Cases

Ephemeral Infrastructure: Automatically provisions a dedicated Neon test database and boots the application on localhost for isolated testing.
CI Pipeline Integration: Configures a new GitHub Actions workflow to run Playwright tests against the ephemeral instance without touching production.
Use Case: Use this to implement a robust E2E gate for a project that is otherwise inaccessible to CI runners due to network restrictions, ensuring code quality without risking production data.

Quick Start

Execute the build-e2e-ci-ephemeral skill to initialize the CI test database and configure the ephemeral Playwright workflow for the current project.

Frequently Asked Questions about build-e2e-ci-ephemeral

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

FAQPage Schema

How do I run Playwright E2E tests in GitHub Actions when my deployment is behind Cloudflare?▼

To run E2E tests behind Cloudflare, you can automate an ephemeral testing environment within GitHub Actions by provisioning an isolated Neon database and booting the app on localhost. This allows Playwright to test locally without network restrictions.

What is an ephemeral testing environment for CI pipelines?▼

An ephemeral testing environment is an isolated, temporary setup for running tests within CI pipelines. This Skill automates provisioning a dedicated Neon database and local application instance in GitHub Actions to execute Playwright suites without touching production data.

Do I need authenticated GitHub CLI access to automate ephemeral E2E testing?▼

Yes, you need authenticated GitHub CLI access and Neon database management capabilities to automate ephemeral E2E testing. These prerequisites ensure secure, non-destructive CI integration when provisioning isolated test environments.

Can I use a Neon database for isolated Playwright testing without affecting production?▼

Yes, you can use a Neon database for isolated Playwright testing without affecting production. The Skill automatically provisions a dedicated, ephemeral Neon test database within GitHub Actions, ensuring your automated test suites remain completely non-destructive.

How do I configure a GitHub Actions workflow for ephemeral Playwright tests?▼

To configure a GitHub Actions workflow for ephemeral Playwright tests, execute the Skill to initialize a CI test database and configure the ephemeral workflow. It automatically provisions isolated Neon infrastructure and local application execution for your current project.

Why are my CI runners blocked from accessing Cloudflare-protected deployments for testing?▼

CI runners are often blocked by network-level security restrictions like Cloudflare. This Skill solves the issue by orchestrating an isolated, ephemeral E2E testing environment that runs entirely within GitHub Actions, bypassing external network limitations.