bug

Generate structured BUG.md files with repro steps and acceptance criteria.

1|Updated Jul 1, 2026
One-click install
npx skills add https://github.com/marcuskrogh/skills --skill bug-marcuskrogh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bug
Source: https://github.com/marcuskrogh/skills/tree/main/skills/bug
Command: npx skills add https://github.com/marcuskrogh/skills --skill bug-marcuskrogh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill eliminates the friction of manual bug tracking by standardizing the alignment, definition, and handoff process for software defects.

Core Features & Use Cases

  • Standardized Reporting: Automatically generates a structured BUG.md file containing repro steps, impact, and acceptance criteria.
  • Workflow Integration: Seamlessly bridges the gap between bug discovery and the implementation phase by creating tasks and delivery branches.
  • Use Case: When a regression is found in production, use this skill to quickly capture the failure, define the fix requirements, and initiate a draft PR for the engineering team.

Quick Start

Invoke the bug skill to align on the current defect and generate the necessary tracking tasks.

Frequently Asked Questions about bug

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

FAQPage Schema
How do I standardize bug reporting for software maintenance cycles?

Standardize bug reporting by generating a structured BUG.md file containing repro steps, impact assessment, and acceptance criteria to align defect definition and handoff.

Can I bridge bug discovery directly to an implementation delivery branch?

Yes, defect reporting bridges discovery to implementation by creating tasks and a delivery branch, maintaining version control continuity for the engineering team.

Do I need a project management tracker to streamline defect resolution?

Yes, integrating with a project management tracker and version control systems is required to maintain delivery branch continuity during defect resolution.

What is the best way to document a production regression for rapid handoff?

Document a production regression by generating a structured alignment artifact that captures the failure, defines fix requirements, and initiates a draft PR.

Why standardize defect tracking alignment artifacts instead of manual reports?

Standardizing defect tracking eliminates the friction of manual reports by automatically generating structured alignment artifacts for rapid definition and implementation handoff.

Does this workflow handle both task tracking and acceptance criteria for defects?

Yes, the defect workflow generates task tracking and includes acceptance criteria within the structured BUG.md file to ensure complete implementation alignment.