skills.rest
leeovery
leeoveryCOMMUNITY
Explore all skills by this author →
𝕏@leeoveryGitHub

workflow-log-bug

Capture user-reported bug symptoms and context into Markdown inbox entries.

27|1|Updated Nov 23, 2025
Search Tags:#workflow#markdown#logging#reporting#inbox#triage#bug
One-click install
npx skills add https://github.com/leeovery/agentic-workflows --skill workflow-log-bug
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: workflow-log-bug
Source: https://github.com/leeovery/agentic-workflows/tree/main/skills/workflow-log-bug
Command: npx skills add https://github.com/leeovery/agentic-workflows --skill workflow-log-bug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill captures bug reports and stores them in the workflow inbox, ensuring they are documented for later triage.

Core Features & Use Cases

  • Automatically capture user-reported symptoms and context into a Markdown file in .workflows/.inbox/bugs.
  • Handle cold starts by prompting for essential details and synthesize them into a coherent entry.
  • Write structured bug reports that can be referenced later by the team.

Quick Start

Provide a concise symptom and impact for the bug to generate a new inbox entry.

Frequently Asked Questions about workflow-log-bug

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

FAQPage Schema
How do I log a bug report into a Markdown inbox for later triage?▼

You can log a bug report by providing the symptom and impact details. The skill synthesizes this context into a single Markdown entry and writes it directly to your local inbox directory for later triage.

Can I capture bug reports in Markdown during an ongoing conversation?▼

Yes, capturing bug reports works during ongoing conversations. It automatically extracts symptoms, context, and impact from your interactions to synthesize a structured Markdown entry for your workflow inbox.

What is the best way to document a bug from a cold start without prior context?▼

Documenting a bug from a cold start prompts you for essential details like symptoms and impact. It then synthesizes your responses into a coherent Markdown entry stored in the designated inbox.

Do I need external dependencies to write bug reports to a local workflow inbox?▼

No external dependencies are required to write bug reports. The skill operates entirely within your local workspace environment, creating Markdown files in the designated inbox directory without needing external tools.

How does synthesizing symptoms and impact improve bug triage?▼

Synthesizing symptoms and impact consolidates scattered details into a single Markdown entry. This structured format ensures bug reports are clearly documented and easily referenced by your team during later triage.

Are there limitations to capturing bugs with a local Markdown workflow?▼

A limitation of this local Markdown workflow is that captured bugs are written to a local directory for manual triage. It focuses on documentation and synthesis rather than automated issue tracking or external system integration.

Related Skills

Explore More Software Engineering Skills→
jinglemansweepjinglemansweep

jp-setup

Create a .plans directory with a .gitkeep file at the repository root.

Community
Basic
officebeatsofficebeats
8

bug-chaser

Triage bug reports into engineering tickets with validated reproduction steps.

Community
Advanced
kraftvaerkkraftvaerk

umbraco-collection-action

Create custom collection actions in the Umbraco backoffice using TypeScript.

Official
Intermediate
Covcloud-LLCCovcloud-LLC

defect

Creates structured markdown bug reports with severity and branch context.

Official
Intermediate