e2e-debug-finance-funnel

Automate end-to-end finance funnel debugging with Playwright CLI.

Updated Aug 6, 2025

Search Tags:#automation #debugging #e2e #staging #finance #playwright #bug-fix

Ready to run

npx skills add https://github.com/fabiano001/claude-config --skill e2e-debug-finance-funnel

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: e2e-debug-finance-funnel
Source: https://github.com/fabiano001/claude-config/tree/main/skills/e2e-debug-finance-funnel
Command: npx skills add https://github.com/fabiano001/claude-config --skill e2e-debug-finance-funnel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates end-to-end debugging of issues in the finance funnel by orchestrating browser-based checks with Playwright CLI, so engineers can reproduce bugs, validate fixes, and verify deployments without manual toil.

Core Features & Use Cases

Reproduces bugs on a target finance funnel URL with an issue description, then iterates fixes through a controlled, repeatable workflow.
Deploys validated changes to staging and generates a structured debug report saved under dynamic-app/debug-reports for traceability.
Supports strict safety rules and automated verification loops to ensure secure, deterministic debugging sessions.

Quick Start

Run the e2e-debug-finance-funnel workflow with a URL and an issue description to start debugging.

Frequently Asked Questions about e2e-debug-finance-funnel

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

FAQPage Schema

How do I automate E2E debugging for a finance funnel using Playwright?▼

Automate E2E debugging for a finance funnel by running a Playwright CLI workflow with a target URL and an issue description to reproduce bugs and iterate fixes. The session uses a headed browser to interact with the staging environment and writes findings to structured debug reports for traceability.

Can I reproduce staging bugs in a finance checkout flow without manual browser testing?▼

Reproduce staging bugs in a finance checkout flow without manual testing by orchestrating browser-based checks with Playwright. You provide the target URL and issue description, and the automated workflow loops through controlled verification iterations to validate fixes deterministically.

What do I need to run an autonomous E2E debug session on my staging deployment?▼

Run an autonomous E2E debug session on staging by providing a target finance funnel URL and a description of the issue. You can optionally specify a maximum iteration count to control the automated verification loops, ensuring the Playwright CLI debug workflow remains bounded and safe.

Where are the findings stored when debugging finance funnel issues with automated Playwright workflows?▼

Debug findings for finance funnel issues are stored as structured debug reports saved under the dynamic-app/debug-reports directory. This ensures full traceability for reproduced bugs, iterated fixes, and validated staging deployments after the automated Playwright workflow completes.

What is the best way to validate finance funnel fixes before deploying to production?▼

Validate finance funnel fixes before production by using an autonomous E2E debugging workflow that iterates fixes through automated verification loops. The Playwright CLI session applies strict safety rules to ensure deterministic debugging, generating traceable reports under dynamic-app/debug-reports upon successful validation.