bugfest

Automates bug triage and ticketing workflows from symptom to resolution.

6|2|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/skillsets-cc/main --skill bugfest
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bugfest
Source: https://github.com/skillsets-cc/main/tree/main/skillsets/%40supercollectible/Valence/content/.claude/skills/bugfest
Command: npx skills add https://github.com/skillsets-cc/main --skill bugfest

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debugging protocol that standardizes triage, root-cause analysis, and ticket-based tracking to accelerate bug resolution.

Core Features & Use Cases

  • Structured phase workflow from symptom to resolution, including ticket creation and manifest tracking.
  • Supports SEC-ticket paths and a centralized PROCESS_DOCS ticket registry for traceability.
  • Provides guidance for establishing context, root-cause analysis, escalation gates, and post-resolution follow-ups.

Quick Start

Describe the bug in detail to initiate the protocol and let Bugfest guide you through triage and ticket creation.

Frequently Asked Questions about bugfest

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

FAQPage Schema
What is a structured bug triage workflow and when do I need it for software debugging?

A structured bug triage workflow standardizes the process from symptom detection to resolution logging, applying formal root-cause analysis and ticket creation. You need it to accelerate bug resolution and ensure traceability across multiple software modules.

How do I automate end-to-end bug triage and ticket creation from a bug symptom?

To automate bug triage, describe the bug symptom in detail to initiate the protocol. The workflow then guides you through context establishment, root-cause analysis, task creation, and manifest tracking until the resolution is logged.

Does this debugging protocol support tracking SEC-tickets and centralized ticket registries?

Yes, the debugging protocol explicitly supports SEC-ticket handling paths and utilizes a centralized PROCESS_DOCS ticket registry to maintain full traceability throughout the bug resolution lifecycle.

What is the best way to standardize root-cause analysis and escalation gating during software debugging?

The best way to standardize root-cause analysis is to follow a structured phase workflow that includes explicit escalation gates. This ensures bugs are properly analyzed and verified before fixes are planned and implemented.

Can I use this triage protocol for fixing bugs across multiple software modules simultaneously?

Yes, this triage protocol is designed for software development teams managing multiple modules. It establishes a formal audit pipeline with task creation and resolution logging to track fixes across different parts of the software.

What steps are required to verify a software fix and log the resolution after root-cause analysis?

After root-cause analysis and escalation gating, you proceed to fixes planning, implementation, and verification. Once verified, the final step is resolution logging within the centralized ticket registry to close the workflow.