skills.rest
Teng-bio
Teng-bioCOMMUNITY
Explore all skills by this author →
GitHub

bug-repro-plan

Generates a bug reproduction plan with environment details, steps, and evidence checklist.

2|Updated May 7, 2026
Search Tags:#checklist#issue tracking#developer communication#bug reproduction#software troubleshooting
One-click install
npx skills add https://github.com/Teng-bio/codex-skills-hub --skill bug-repro-plan-teng-bio
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bug-repro-plan
Source: https://github.com/Teng-bio/codex-skills-hub/tree/main/skills/global/bug-repro-plan
Command: npx skills add https://github.com/Teng-bio/codex-skills-hub --skill bug-repro-plan-teng-bio

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of creating a detailed bug reproduction plan, making it easier to identify and diagnose issues.

Core Features & Use Cases

  • Minimal Reproducible Bug Plan: Generate a structured bug reproduction plan with minimal steps.
  • Environment & Behavior Documentation: Capture environment details, steps, expected vs. actual behavior, and evidence checklist.
  • Use Case: When users need to communicate a bug to developers with a clear, step-by-step plan that includes all necessary details.

Quick Start

Create a reproducible bug plan for the reported issue by running the bug-repro-plan skill.

Frequently Asked Questions about bug-repro-plan

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

FAQPage Schema
How do I create a minimal reproducible example for a software bug?▼

To create a minimal reproducible example, you structure environment details, isolate step-by-step instructions, and define expected versus actual behavior to communicate the issue clearly to developers.

What is a bug reproduction plan in software troubleshooting?▼

A bug reproduction plan is a structured document outlining environment details, step-by-step instructions, and an evidence checklist to consistently replicate and diagnose software issues.

How do I document environment details for developer communication?▼

You document environment details by capturing system configurations, software versions, and specific conditions alongside step-by-step instructions and an evidence checklist for clear developer communication.

What is the best way to track issue reproduction steps and evidence?▼

The best way to track issue reproduction steps is using a structured checklist that captures environment details, sequential actions, expected outcomes, actual behavior, and supporting evidence.

Can I use a bug reproduction checklist for issue tracking?▼

Yes, you can use a bug reproduction checklist for issue tracking. It structures environment details, step-by-step instructions, and evidence to streamline troubleshooting and developer communication.

What information do I need to generate a bug reproduction plan?▼

You need structured information about the bug, including environment details, specific step-by-step instructions, and expected versus actual behavior, to generate a minimal reproduction plan.

Related Skills

Explore More Software Engineering Skills→
simonwjacksonsimonwjackson

se-report-bug

Collect structured bug information and create GitHub issues via the gh CLI.

Community
Advanced
latestaiagentslatestaiagents
5

bug-reporting

Generates structured bug reports with reproduction steps and evidence templates for developers.

Official
Basic
mediar-aimediar-ai
1.6k

Terminator Issue Reporter

Generate structured GitHub issues for Terminator failures with logs and reproduction steps.

Official
Advanced
nntan90nntan90
4

bug-report

Generate standardized bug reports for Jira, GitHub Issues, and Linear.

Community
Advanced