debug-e2e

Coordinates interactive debugging sessions for failed end-to-end CI tests via subagents.

449|615|Updated Feb 20, 2023

Search Tags:#debugging #logs #e2e #subagents #ci #hypotheses

Ready to run

npx skills add https://github.com/AztecProtocol/aztec-packages --skill debug-e2e

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debug-e2e
Source: https://github.com/AztecProtocol/aztec-packages/tree/main/yarn-project/.claude/skills/debug-e2e
Command: npx skills add https://github.com/AztecProtocol/aztec-packages --skill debug-e2e

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill orchestrates interactive debugging for failed end-to-end tests, delegating log reading to subagents to keep the main conversation clean and collaborative for hypothesis testing.

Core Features & Use Cases

Orchestrated Debug Sessions: Run ping-pong debugging workflows without cluttering the main chat.
Subagent Delegation: Use specialized subagents to identify failures, analyze logs, and inspect code paths.
Use Case: When a CI job fails intermittently, start a debugging session with this skill to pair with the user and form hypotheses.

Quick Start

Use the /debug-e2e command to begin a debugging session and specify a CI hash, PR number, or test name.

Frequently Asked Questions about debug-e2e

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

FAQPage Schema

How do I debug flaky E2E tests in CI without cluttering the chat?▼

Debug flaky E2E tests interactively by orchestrating subagents to analyze CI logs and form hypotheses, keeping the main conversation clean. The skill delegates log reading to subagents and guides you through hypothesis-driven investigation.

What is the best way to analyze CI failures across multiple PRs and test runs?▼

The best way to analyze CI failures is using an interactive debugging session that coordinates subagents to identify failures, analyze logs, and form hypotheses across CI runs, PRs, and test names.

How do I start an interactive E2E debugging session for a specific test failure?▼

Start an E2E debugging session by using the /debug-e2e command and specifying a CI hash, PR number, or test name. The skill then orchestrates the workflow by delegating tasks to identify failures and analyze logs.

Does this debugging approach read logs directly in the main conversation?▼

No, this debugging approach never reads logs directly in the main conversation. It delegates log reading to specialized subagents to keep the chat clean and collaborative for hypothesis testing.

Can I use subagents to identify intermittent CI test failures and inspect code paths?▼

Yes, you can use specialized subagents to identify intermittent CI test failures, analyze logs, and inspect code paths. The skill coordinates these subagents to run collaborative debugging workflows.

When should I use an interactive E2E test debugging skill instead of manual log inspection?▼

Use an interactive E2E test debugging skill when a CI job fails intermittently and you need to pair with an agent to form hypotheses. It prevents chat clutter by delegating log analysis to subagents.