debug-replay

Extracts reproduction steps from Amplitude Session Replay timelines for reported bugs.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/amplitude/amplitude-copilot-plugin --skill debug-replay-amplitude
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug-replay
Source: https://github.com/amplitude/amplitude-copilot-plugin/tree/main/skills/plugins/amplitude/debug-replay
Command: npx skills add https://github.com/amplitude/amplitude-copilot-plugin --skill debug-replay-amplitude

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Bug reports often lack the detail engineers need to reproduce failures. This Skill turns vague reports like "the export button doesn't work" into numbered, engineer-ready reproduction steps by finding the actual sessions where the error occurred in Amplitude Session Replay and analyzing what users did before the failure. ## Core Features & Use Cases - Error Session Discovery: Finds sessions matching error events, specific users, or error message patterns using Amplitude Session Replay filters. - Interaction Timeline Extraction: Decodes session replays into navigations, clicks, and inputs, then compares multiple sessions to identify the common action sequence preceding the error. - Engineering-Ready Bug Reports: Produces structured output with reproduction steps, expected vs. actual behavior, replay links, confidence levels, and deployment context. - Use Case: A customer reports that checkout fails. The Skill finds their recent sessions, extracts timelines from 3-5 error sessions, identifies the shared click path before the failure, checks if a recent deploy aligns with the error spike, and delivers copy-paste-ready repro steps. ## Quick Start Ask the assistant to find reproduction steps for a reported bug by analyzing Amplitude session replays where the error occurred.

Frequently Asked Questions about debug-replay

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

FAQPage Schema
How do I get reproduction steps from a bug report using session replay?

Provide the error event name, user identifier, or error message, and the Skill finds matching sessions via Amplitude Session Replay, extracts interaction timelines, and distills the common action sequence into numbered reproduction steps with replay links.

How to find sessions where a specific error occurred in Amplitude?

Use the get_session_replays tool with event count filters targeting the error event, such as [Amplitude] Error Logged, optionally filtered by user email or error message content. Request 3-5 sessions for reliable pattern extraction.

Does session replay debugging work without a specific user identifier?

Yes, you can filter sessions by error event type or error message content alone. The Skill searches for sessions containing the error across all users, then compares timelines to find the shared failure path.

Why are no replay events returned for some sessions?

Some sessions lack rrweb data due to replay being disabled, ad blockers, or privacy settings. The Skill skips those sessions, notes the gap, and moves to the next available session with valid replay data.

What are the limitations of session replay element identification?

Replay events return DOM node IDs rather than element names, so interactions are described by position, page context, and sequence. Steps use phrasing like "click in the upper-right area of the form" unless element identity can be inferred.