skills.rest
heyu-ai
heyu-aiOFFICIAL
Explore all skills by this author →
WebsiteGitHub

mycelium-debug-report

Generate Markdown debug reports and clean up temporary files after bug resolution.

Updated May 15, 2026
Search Tags:#development workflow#cleanup#code organization#bug resolution#debug report
One-click install
npx skills add https://github.com/heyu-ai/yibi-stack --skill mycelium-debug-report
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mycelium-debug-report
Source: https://github.com/heyu-ai/yibi-stack/tree/main/plugins/growth/skills/mycelium/debug-report
Command: npx skills add https://github.com/heyu-ai/yibi-stack --skill mycelium-debug-report

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of generating a detailed debug report and cleaning up temporary files after resolving a bug, ensuring a clean and organized development environment.

Core Features & Use Cases

  • Debug Report Generation: Automatically generates a Markdown report containing all relevant information about the bug resolution process.
  • Cleanup: Removes temporary files and code snippets created during debugging.
  • Use Case: After resolving a complex bug, use this Skill to generate a comprehensive report and clean up the workspace to maintain a tidy development environment.

Quick Start

Run the command '/debug_report' to generate a debug report after resolving a bug.

Frequently Asked Questions about mycelium-debug-report

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

FAQPage Schema
How do I generate a debug report after resolving a bug?▼

To generate a debug report after resolving a bug, use an automated script to produce a Markdown file containing symptoms, attempted solutions, and the final root cause. This ensures the bug resolution process is properly documented.

How do I clean up temporary files and code snippets after debugging?▼

You can clean up temporary files and code snippets after debugging by automating workspace cleanup. This removes leftover debugging artifacts from your local git repository, ensuring a tidy and organized development environment.

What is included in an automated debug report for a resolved bug?▼

An automated debug report includes comprehensive details of the bug resolution process, specifically documenting the initial symptoms, attempted solutions, and the final root cause. It is generated as a Markdown file for easy reading.

Do I need a local git repository to generate a debug report?▼

Yes, generating a debug report and cleaning up the workspace requires access to a local git repository. It also requires your knowledge of the bug resolution process to accurately document the symptoms and root cause.

What is the best way to document a bug resolution process in Markdown?▼

The best way to document a bug resolution process in Markdown is to automate report generation after the bug is fixed. This automatically captures symptoms, attempted solutions, and the final root cause into a structured file.

Related Skills

Explore More Software Engineering Skills→
GenEducationGenEducation

bmad-os-root-cause-analysis

Analyze bug-fix commits to produce structured root cause analysis reports.

Official
Advanced
f1shermanf1sherman
2

_create-handoff

Generate structured handoff markdown files with context, changes, and action items.

Community
Basic
stoodderstoodder
1

report-bug

Generate bug reports from raw descriptions using project context and defaults.

Community
Advanced
ntaksh42ntaksh42

ai-response-refiner

Refine rough AI outputs into fluent, structured prose with headings and bullet points.

Community
Advanced