bug-management

Standardize defect tracking by maintaining a canonical BUG_LOG.md file.

Updated Feb 5, 2026
One-click install
npx skills add https://github.com/Luis-ERP/dev-agent-crew --skill bug-management
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bug-management
Source: https://github.com/Luis-ERP/dev-agent-crew/tree/main/skills/bug-management
Command: npx skills add https://github.com/Luis-ERP/dev-agent-crew --skill bug-management

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes defect reporting and auditing by maintaining a single source of truth for bugs in docs/quality/BUG_LOG.md, ensuring traceability from discovery to resolution.

Core Features & Use Cases

  • Single source of truth: All bugs must be logged in docs/quality/BUG_LOG.md to guarantee consistency.
  • Structured logging: Logs include fields like Detected date, Detected phase, Detected by, Severity, and Status to enable metrics.
  • Workflow guidance: Provides instructions on detection and injection phases and how to classify root causes.
  • Compliance & QA: Enables QA teams to track open S0/S1 issues and link them to features.

Quick Start

Create the docs/quality/BUG_LOG.md file and begin logging bugs using the table format defined in the template. Reference the BUG_LOG.md guidelines and fill in required fields for each new issue.

Frequently Asked Questions about bug-management

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

FAQPage Schema
How do I maintain a centralized bug log for software defect tracking?

Defect tracking in QA workflows requires logging all bugs in a canonical BUG_LOG.md file. This creates an auditable, centralized defect log that standardizes reporting by enforcing fields like Detected date, Severity, and Status for full traceability.

What fields are required for an auditable defect log?

An auditable defect log requires fields including Detected date, Detected phase, Detected by, Severity, and Status. These structured fields enable metrics tracking, ensure consistent reporting, and provide traceability from discovery to resolution.

When should I log bugs during QA workflows and production incident reviews?

You should log bugs during QA workflows and production incident reviews whenever a defect is discovered. Logging bugs in the BUG_LOG.md file applies to software development and ensures traceability from discovery to resolution across detection and injection phases.

How do I classify bug detection and injection phases for root cause analysis?

Classify bug detection and injection phases by following the workflow guidance provided by the defect tracking process. This ensures accurate root cause classification and consistent reporting within the BUG_LOG.md table format for traceability.

Can I track open S0 and S1 severity issues using a markdown defect log?

Yes, you can track open S0 and S1 severity issues using the BUG_LOG.md defect log. This enables QA teams to monitor critical defects and link them directly to features for compliance and incident management.

Does this defect tracking approach require any specific bug tracking dependencies?

No, this defect tracking approach requires no specific dependencies. It relies solely on maintaining a canonical BUG_LOG.md file to standardize bug reporting and auditing without external component integrations.