skills.rest
pcortes
pcortesCOMMUNITY
Explore all skills by this author →
GitHub

bug-researcher

Reproduce bugs and collect stack traces, logs, and affected files.

Updated Aug 27, 2026
Search Tags:#debugging#evidence#reproduction#bug#tests#stack-trace
One-click install
npx skills add https://github.com/pcortes/swarm-attack --skill bug-researcher
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bug-researcher
Source: https://github.com/pcortes/swarm-attack/tree/main/default-skills/bug-researcher
Command: npx skills add https://github.com/pcortes/swarm-attack --skill bug-researcher

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Speed up bug investigations by systematically reproducing the issue and collecting evidence to guide debugging.

Core Features & Use Cases

  • Reproduction workflow: steps to reproduce and capture outputs.
  • Evidence collection: stack traces, logs, and failing outputs.
  • Affected areas map: identifies files involved.

Quick Start

Provide the bug report and tests path; the skill will attempt reproduction and return evidence artifacts and file map.

Frequently Asked Questions about bug-researcher

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

FAQPage Schema
How do I reproduce a bug and collect evidence for debugging?▼

Reproducing bugs involves systematically executing steps from a bug report, capturing test outputs, error messages, and stack traces to confirm the issue. This skill automates that workflow by running reproduction steps, extracting logs, and mapping affected files to guide root-cause analysis.

What evidence should I gather when investigating a bug report?▼

Effective bug investigation requires stack traces, error logs, failing test outputs, and identification of affected code files. This skill collects that evidence systematically by executing reproduction steps and extracting diagnostic artifacts needed to pinpoint the bug's source.

How do I identify which files are involved in a bug?▼

Identifying affected areas requires executing the reproduction workflow and analyzing test outputs, logs, and error messages to map involved files and code snippets. This skill automates that mapping by running reproduction steps and documenting which components are implicated.

Can I automate bug reproduction and log extraction?▼

Yes. Automated bug reproduction executes steps from a bug report, runs tests, and extracts stack traces and logs without manual re-testing. This skill handles the full workflow—reproduction, evidence collection, and affected-file mapping—given a bug description and test path.

What do I need to provide to start a bug investigation?▼

To begin investigation, provide a bug report description and optionally a test path. The skill uses Read, Glob, Grep, and Bash tools to execute reproduction, extract logs and error messages, and return evidence artifacts and a file map for analysis.

Why is systematic bug reproduction important?▼

Systematic reproduction confirms an issue is real, captures consistent outputs and stack traces, and identifies the exact conditions triggering the bug. This structured approach accelerates debugging by providing verified evidence rather than relying on incomplete problem descriptions.

Related Skills

Explore More Software Engineering Skills→
openshift-engopenshift-eng
112

Create Jira Bug

Create Jira bug reports with reproduction steps and environment details.

Community
Basic
mi179mi179
1

gstack-openclaw-investigate

Analyze software bugs through a five-phase root-cause investigation workflow.

Community
Advanced
kynoptickynoptic
1

Debugging Runtime Errors

Analyze stack traces and error logs to identify root causes and propose fixes.

Community
Advanced
DevattomDevattom

debug

Debug code errors through analysis, reproduction, solution proposal, and multi-layer verification.

Community
Advanced