reproduce-bug

Reproduces GitHub issues by analyzing logs, console errors, and Playwright screenshots.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Andreicr1/Netz-Private-Credit-OS --skill reproduce-bug-andreicr1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reproduce-bug
Source: https://github.com/Andreicr1/Netz-Private-Credit-OS/tree/main/.github/skills/reproduce-bug
Command: npx skills add https://github.com/Andreicr1/Netz-Private-Credit-OS --skill reproduce-bug-andreicr1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reproduce and investigate bugs reported in an issue by combining log analysis, console inspection, and Playwright screenshots so developers can validate, document, and communicate the root cause.

Core Features & Use Cases

  • Parallel log investigation: Run targeted agents to find relevant log entries and surface probable failure points.
  • Visual reproduction: Use Playwright to navigate the application, execute user flows, capture screenshots, and record console errors for UI-related bugs.
  • Issue reporting: Collect file paths, console logs, screenshots, and exact reproduction steps to attach as a detailed comment on the GitHub issue.
  • Use Case: When a user reports a UI glitch or server-side error, the Skill helps a developer reproduce the behavior locally, gather evidence, and prepare an actionable issue comment.

Quick Start

Open the referenced GitHub issue number and run the reproduce-bug workflow to collect logs, attempt a Playwright reproduction, capture screenshots, and summarize findings.

Frequently Asked Questions about reproduce-bug

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

FAQPage Schema
How do I reproduce a GitHub issue locally using logs and screenshots?▼

You can reproduce a GitHub issue by running a workflow that investigates server logs, navigates the application with Playwright to capture screenshots, records console errors, and summarizes the findings as a comment on the issue.

How do I capture console errors and screenshots for a reported UI glitch?▼

To capture console errors and screenshots for a UI glitch, you use Playwright browser automation to navigate the application, execute user flows, and record console errors alongside visual evidence.

Can I use Playwright to investigate server-side errors from AppSignal logs?▼

Yes, you can investigate server-side errors by analyzing AppSignal or file logs alongside Playwright browser automation to capture backend failure points and frontend visual evidence for the same issue.

What do I need to reproduce bugs from GitHub issues on my local repository?▼

To reproduce bugs from GitHub issues, you need local repository access with the server running, application logs from AppSignal or files, Playwright-compatible browser automation, and GitHub permissions to comment and upload artifacts.

Does bug reproduction require access to application logs and local server setup?▼

Yes, bug reproduction requires access to application logs such as AppSignal or file logs, a running local server environment, and Playwright browser automation to validate reproduction steps and capture frontend evidence.

What is the best way to document reproduction steps for an issue tracker?▼

To document reproduction steps for an issue tracker, collect file paths, console logs, Playwright screenshots, and exact user flows, then attach them as a detailed, actionable comment on the GitHub issue.