reproduce-bug

Coordinate bug reproduction across logs, console output, and browser screenshots.

Updated Mar 3, 2026
One-click install
npx skills add https://github.com/The-Rabak/naysmith --skill reproduce-bug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reproduce-bug
Source: https://github.com/The-Rabak/naysmith/tree/main/.github/skills/reproduce-bug
Command: npx skills add https://github.com/The-Rabak/naysmith --skill reproduce-bug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often struggle to reproduce and verify bugs across logs, UI, and console. This skill coordinates cross-cutting investigation steps to capture evidence and verify fixes.

Core Features & Use Cases

  • Guided reproduction flow: collect logs, inspect console, and reproduce UI steps.
  • Evidence capture: screenshots, logs, and console traces stored in a structured report.
  • Reproducibility checks: validate reproducible steps and track fixes across environments.

Quick Start

Describe the bug in a GitHub issue and run the repro workflow to collect logs, inspect the console, and capture browser screenshots.

Frequently Asked Questions about reproduce-bug

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

FAQPage Schema
How do I reproduce bugs using logs and console output?

Bug reproduction for web projects coordinates cross-cutting investigation by collecting logs, inspecting console output, and capturing browser screenshots to verify defects across UI and backend components.

What is the best way to capture evidence for issue triage?

Capturing evidence for issue triage involves running a structured reproduction flow that stores visual screenshots, console traces, and application logs together in a comprehensive report.

How do I verify reproducibility checks across different environments?

Verifying reproducibility checks involves validating the collected reproduction steps and tracking fix behavior across environments using the structured report generated from logs, console traces, and browser screenshots.

Does this bug reproduction workflow work for backend defects or only UI issues?

This bug reproduction workflow handles both UI and backend defects in web projects, guiding teams through end-to-end steps that coordinate log collection, console inspection, and visual browser screenshots.

How do I start bug reproduction from a GitHub issue?

Start bug reproduction from a GitHub issue by describing the defect and running the repro workflow to automatically collect logs, inspect the browser console, and capture visual screenshots for evidence.