barkleesanders

Reproduce Bug — Development skill for Claude Code

Development community

Reproduce and investigate a bug using logs, console inspection, and browser screenshots.

How to install Reproduce Bug

Installs to ~/.claude/skills/barkleesanders-claude-code-starter-reproduce-bug/SKILL.md

Terminal
mkdir -p ~/.claude/skills/barkleesanders-claude-code-starter-reproduce-bug && curl -fsSL https://raw.githubusercontent.com/barkleesanders/claude-code-starter/HEAD/commands/reproduce-bug.md -o ~/.claude/skills/barkleesanders-claude-code-starter-reproduce-bug/SKILL.md

Restart Claude Code, or start a new session, for it to be picked up.

What Reproduce Bug does


name: reproduce-bug description: Reproduce and investigate a bug using logs, console inspection, and browser screenshots argument-hint: "[GitHub issue number]"

Reproduce Bug Command

Look at github issue #$ARGUMENTS and read the issue description and comments.

Phase 1: Log Investigation

Run the following agents in parallel to investigate the bug:

  1. Task rails-console-explorer(issue_description)
  2. Task appsignal-log-investigator(issue_description)

Think about the places it cou

Alternatives in Development

  • Browser Tools MCP — Monitor browser logs directly from Cursor and other MCP compatible IDEs 7.2k ★
  • Investigate — Investigation Skill 1.9k ★
  • Investigate Performance — Investigate a Nimbalyst performance problem (freeze, lag, idle CPU, slow op, memory growth) with measured evid 1.6k ★

Full documentation available on GitHub

View Source Repository