debug-e2e
Orchestrates E2E test debugging sessions by delegating log analysis to subagents, keeping the primary conversation focused.
Install
mkdir -p .claude/skills/debug-e2e && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/4310" && unzip -o skill.zip -d .claude/skills/debug-e2e && rm skill.zipInstalls to .claude/skills/debug-e2e
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Interactive debugging for failed e2e tests. Orchestrates the debugging session but delegates log reading to subagents to keep the main conversation clean. Use for ping-pong debugging sessions where you want to form and test hypotheses together with the user.Key capabilities
- →Orchestrate debugging sessions for failed E2E tests
- →Delegate log analysis to subagents to maintain context cleanliness
- →Compare logs from failed and successful test runs
- →Formulate and test multiple hypotheses based on log evidence
- →Identify failure patterns like timeouts and race conditions
How it works
The skill acts as a coordinator that spawns specialized subagents to identify failures and analyze logs, preventing large log files from polluting the main conversation.
Inputs & outputs
When to use debug-e2e
- →Investigate failing CI pipeline test runs
- →Debug flaky E2E tests collaboratively
- →Compare logs from failed and successful runs
- →Analyze stack traces from PR test failures
About debug-e2e
Streamlines E2E testing failures by guiding the user through hypothesis testing. It uses subagents to perform heavy log analysis and identifies failures without cluttering the main chat session.
Interactive debugging for failed e2e tests. Orchestrates the debugging session but delegates log reading to subagents to keep the main conversation clean. Use for ping-pong debugging sessions where you want to form and test hypotheses together with the user.
When not to use it
- →Obvious assertion failures where code investigation is sufficient
- →Build or compilation errors
- →Simple configuration issues like missing environment variables
Prerequisites
Limitations
- →Cannot read logs directly in the main conversation
- →Requires access to CI history and log download tools
How it compares
It avoids reading massive logs directly in the chat, instead using subagents to summarize findings and guide the user through a structured hypothesis-testing workflow.
Compared to similar skills
debug-e2e side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| debug-e2e (this skill) | 1 | 7mo | Review | Advanced |
| python-testing-patterns | 77 | 4mo | Review | Intermediate |
| chrome-devtools | 41 | 8mo | Review | Intermediate |
| bats | 9 | 9mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by AztecProtocol
View all by AztecProtocol →You might also like
python-testing-patterns
wshobson
Implement comprehensive testing strategies with pytest, fixtures, mocking, and test-driven development. Use when writing Python tests, setting up test suites, or implementing testing best practices.
chrome-devtools
mrgoonie
Browser automation, debugging, and performance analysis using Puppeteer CLI scripts. Use for automating browsers, taking screenshots, analyzing performance, monitoring network traffic, web scraping, form automation, and JavaScript debugging.
bats
OleksandrKucherenko
Bash Automated Testing System (BATS) for TDD-style testing of shell scripts. Use when: (1) Writing unit or integration tests for Bash scripts, (2) Testing CLI tools or shell functions, (3) Setting up test infrastructure with setup/teardown hooks, (4) Mocking external commands (curl, git, docker), (5) Generating JUnit reports for CI/CD, (6) Debugging test failures or flaky tests, (7) Implementing test-driven development for shell scripts.
browser-daemon
noiv
Persistent browser automation via Playwright daemon. Keep a browser window open and send it commands (navigate, execute JS, inspect console). Perfect for interactive debugging, development, and testing web applications. Use when you need to interact with a browser repeatedly without opening/closing it.
performance-profiling
davila7
Performance profiling principles. Measurement, analysis, and optimization techniques.
obsidian-local-dev-loop
jeremylongshore
Configure Obsidian plugin development with hot-reload and fast iteration. Use when setting up development workflow, configuring test vaults, or establishing a rapid development cycle. Trigger with phrases like "obsidian dev loop", "obsidian hot reload", "obsidian development workflow", "develop obsidian plugin".