reproduce-bug

Reproduce GitHub-reported bugs via logs, code inspection, and Playwright.

12|2|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/jikig-ai/soleur --skill reproduce-bug-jikig-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reproduce-bug
Source: https://github.com/jikig-ai/soleur/tree/main/plugins/soleur/skills/reproduce-bug
Command: npx skills add https://github.com/jikig-ai/soleur --skill reproduce-bug-jikig-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reproducing and investigating intermittent or reported bugs is time-consuming and error-prone; this Skill guides a systematic investigation by combining log analysis, code inspection, and visual reproduction to produce verifiable evidence and a clear issue report.

Core Features & Use Cases

  • Log Investigation: Search application logs, error trackers, and recent commits to find error messages, stack traces, and likely failure points.
  • Visual Reproduction with Playwright: Navigate the app on a running local server, reproduce user flows, capture screenshots, and collect console errors for UI-related bugs.
  • Documentation & Reporting: Consolidate file paths, reproduction steps, screenshots, and suggested fixes and post a summarized comment to the GitHub issue.
  • Cleanup: Remove local artifacts created during reproduction to keep the workspace tidy.

Quick Start

Provide the GitHub issue number and run reproduce-bug to analyze logs, attempt a Playwright reproduction on your localhost, capture screenshots, and prepare a findings comment for the issue.

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-reported bug automatically?

To reproduce a GitHub-reported bug, provide the issue number to analyze logs, inspect recent commits, replay user interactions with Playwright, and capture screenshots as evidence.

What is the best way to investigate intermittent UI regressions in a web application?

Investigate UI regressions by searching application logs and error traces, tracing recent commits, and using Playwright to navigate the local development server and capture browser snapshots of the failure.

Do I need a local development server running to use Playwright for bug reproduction?

Yes, reproducing bugs and capturing visual evidence requires a running local development server, repository code access, application logs, and Playwright automation capabilities installed in your environment.

Can I automate posting bug reproduction steps and screenshots back to a GitHub issue?

Yes, you can automate posting to a GitHub issue by consolidating file paths, reproduction steps, screenshots, and suggested fixes into a summarized comment directly on the issue thread.

How does log investigation work for tracing application errors?

Log investigation works by searching application logs and error trackers to find error messages and stack traces, then tracing recent commits to identify likely failure points in the codebase.

What are the limitations of using Playwright to reproduce user-flow issues?

Limitations include dependency on local server access and Playwright automation capabilities; it may not reproduce intermittent bugs without specific error traces or if the issue requires external third-party service interactions.