report-bug

Collect environment details and errors into a structured bug report.

1|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/csackrider/AI-DLC --skill report-bug-csackrider
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: report-bug
Source: https://github.com/csackrider/AI-DLC/tree/main/plugins/ai-dlc-skills/skills/report-bug
Command: npx skills add https://github.com/csackrider/AI-DLC --skill report-bug-csackrider

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bug triage is slowed by incomplete reports; this Skill orchestrates a conversation-driven process to collect environment details, reproduction steps, exact error messages, and observability evidence, producing a structured draft for issue tracking.

Core Features & Use Cases

  • Structured draft generation including sections: Summary, Environment, Steps to Reproduce, Evidence, Hypothesis, and Open questions.
  • Conversation-first approach to gather needed data without forcing long templates.
  • Redaction of secrets and sensitive data to avoid leakage in reports.
  • Use Case: When a developer asks for an issue to be triaged, this Skill compiles a complete report from chat.

Quick Start

Start by asking the user to provide or confirm environment details, reproduction steps, and exact errors, then generate a structured bug report ready for GitHub.

Frequently Asked Questions about report-bug

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

FAQPage Schema
How do I create a structured bug report for faster triage?

To create a structured bug report, provide environment details, reproduction steps, exact error messages, and observability evidence. This generates a ready-to-paste draft with Summary, Environment, Evidence, and Hypothesis sections for faster triage.

What information is needed for a reproducible bug report during incident response?

A reproducible bug report requires environment details, exact reproduction steps, exact error messages, and observability evidence. This data is compiled into a structured draft to guide incident triage and review.

Can I generate GitHub-ready issue reports from a conversation without filling out a long template?

Yes, you can generate GitHub-ready issue reports from a conversation. A conversation-first approach interactively collects necessary environment and reproduction data, avoiding the need to fill out long manual templates.

Does this bug reporting process redact secrets and sensitive data before creating the issue draft?

Yes, the bug reporting process redacts secrets and sensitive data before creating the issue draft. This prevents accidental leakage of confidential information in the final structured report.

What is the best way to document reproduction steps and observability evidence for QA?

The best way to document reproduction steps and observability evidence for QA is using a structured format. This includes sections for Steps to Reproduce, Evidence, Hypothesis, and Open questions to ensure review-ready triage.