e2e-production

Automate end-to-end testing of production deployments with browser automation and Neon MCP database verification.

Updated Jan 31, 2026
One-click install
npx skills add https://github.com/JordiNodeJS/.github-config --skill e2e-production
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: e2e-production
Source: https://github.com/JordiNodeJS/.github-config/tree/main/.github/skills/e2e-production
Command: npx skills add https://github.com/JordiNodeJS/.github-config --skill e2e-production

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enables automated end-to-end testing of production deployments for The Simpsons API using browser automation with Chrome DevTools MCP and real-time database verification via Neon MCP.

Core Features & Use Cases

  • End-to-end production validation: Verify UI flows, API responses, and data consistency across production deployments.
  • Read-only discovery + explicit mutation flow: Discover routes safely and perform mutations only after explicit approval, with strong safeguards.
  • DB-UI correlation: Compare UI state with Neon-backed data to ensure mutations reflect correctly (where applicable) and to detect drift.
  • Reference-guided workflows: Use the PRODUCTION_E2E.md references to tailor tests to deployment specifics.

Quick Start

Run a production E2E test for The Simpsons API using Chrome DevTools MCP and Neon MCP, covering smoke journeys, mutation validation, and deployment sanity checks.

Frequently Asked Questions about e2e-production

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

FAQPage Schema
How do I run E2E tests in production with browser automation and database checks?▼

Production E2E testing uses Chrome DevTools MCP for browser automation and Neon MCP for real-time database verification, validating UI flows and data consistency across live deployments.

Can I verify UI mutations against my database state during production testing?▼

Yes, DB-UI correlation compares UI state with Neon-backed data to verify mutations reflect correctly, detecting data drift between the frontend interface and the live database.

How does read-only discovery work for production E2E validation?▼

Read-only discovery safely explores application routes without side effects, requiring explicit approval before executing any UI mutations to maintain deployment integrity during testing.

What's the best way to perform post-deploy sanity checks for a live API?▼

Automated deployment verification applies browser automation and database checks to execute smoke journeys and mutation validation, ensuring production deployments function correctly after release.

Do I need Chrome DevTools MCP and Neon MCP to validate live deployments?▼

Yes, Chrome DevTools MCP drives browser automation for UI verification and Neon MCP executes correlated database state checks, together providing full-stack production E2E test coverage.

When should I not use automated mutation flows in production environments?▼

Avoid automated mutations without explicit approval flows; this skill enforces safeguards requiring manual confirmation before executing data-altering actions in live production environments.