skills.rest
DuongMQuang
DuongMQuangCOMMUNITY
Explore all skills by this author →
GitHub

5-maintain

Guide systematic debugging, log analysis, and bug triage with BUGLOG.md.

6|Updated Mar 9, 2026
Search Tags:#debugging#logs#release-management#hotfix#maintain#bug-triage
One-click install
npx skills add https://github.com/DuongMQuang/quangflow --skill 5-maintain
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: 5-maintain
Source: https://github.com/DuongMQuang/quangflow/tree/main/plugins/quangflow/skills/5-maintain
Command: npx skills add https://github.com/DuongMQuang/quangflow --skill 5-maintain

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After a release, teams need a structured, repeatable process to identify, triage, and fix production bugs while managing evidence and risk.

Core Features & Use Cases

  • Systematic debugging protocol guides root-cause investigation using logs, events, and source context.
  • Bug tracking & triage maintains a live BUGLOG.md with status, ownership, and evidence.
  • Hotfix coordination supports scoped fixes, test guidance, and phased verification for releases.

Quick Start

Enter maintain mode by running /qf:5-maintain to begin the post-ship maintenance workflow.

Frequently Asked Questions about 5-maintain

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

FAQPage Schema
How do I perform systematic bug triage for shipped software projects?▼

Systematic bug triage for shipped projects requires a structured post-ship maintenance protocol that guides root-cause investigation using logs, events, and source context while maintaining a live tracking document like BUGLOG.md for status and ownership.

What is the best way to coordinate a hotfix across multiple components after a release?▼

Coordinating a hotfix across multiple components requires a structured protocol that supports scoped fixes, provides test guidance, and enforces phased verification to manage release risk effectively after shipping a milestone.

How do I analyze logs for evidence-based debugging during post-release maintenance?▼

Evidence-based debugging during post-release maintenance involves analyzing logs and events through a systematic protocol that traces evidence back to source context, ensuring root-cause investigation is documented and repeatable.

Do I need a specific bug tracking format to manage production issues after shipping?▼

Managing production issues after shipping benefits from a documented bug tracking format like BUGLOG.md, which records status, ownership, and evidence traces to maintain a live history of triaged issues and escalation decisions.

When should I escalate a production bug during issue triage?▼

You should escalate a production bug during issue triage when the systematic debugging protocol detects a shipped milestone impact that exceeds scoped hotfix thresholds, requiring coordinated investigation across multiple components.

Related Skills

Explore More Software Engineering Skills→
haJ1thaJ1t

forensic-investigator

Analyze memory dumps and system logs to construct event timelines and identify root causes.

Community
Advanced
zillafan80-Maxzillazillafan80-Maxzilla

archon-test-release

Automate end-to-end smoke testing for released Archon binaries across install paths.

Community
Advanced
yknothingyknothing
1

release-management

Generate a release plan with scope, go/no-go decisions, and ownership.

Community
Advanced
christianhellechristianhelle
413

docs-bug-triage

Classify issue reports as documentation gaps or product bugs.

Community
Intermediate