bug

Triage bugs through eligibility checks, codebase analysis, and sprint planning.

1|1|Updated Dec 30, 2025
One-click install
npx skills add https://github.com/0xHoneyJar/loa-constructs --skill bug-0xhoneyjar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bug
Source: https://github.com/0xHoneyJar/loa-constructs/tree/main/.claude/skills/bug-triaging
Command: npx skills add https://github.com/0xHoneyJar/loa-constructs --skill bug-0xhoneyjar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Triage a reported bug through structured phases: validate eligibility, gather details, analyze the codebase, and generate a handoff contract for the implement phase. Bugs always get their own micro-sprint, and test-first is enforced.

Core Features & Use Cases

  • Phase-driven workflow: eligibility checks, information gathering, codebase analysis, and artifact creation.
  • Guardrails and safety: PII redaction, tool availability checks, and atomic state writes.
  • Output contracts: produces triage.md handoff and a sprint.md plan for /implement.

Quick Start

Describe the bug or import a GitHub issue to start triage.

Frequently Asked Questions about bug

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

FAQPage Schema
How do I automate bug triage and sprint planning from GitHub issues?

Bug triage and sprint planning are automated by importing GitHub issues or user-reported bugs, guiding eligibility checks, codebase analysis, and generating triage.md and sprint.md handoff artifacts.

What is the process for redacting PII during codebase analysis for bug triage?

PII redaction during bug triage is enforced through automated guardrails that detect potential injections and redact sensitive information before producing atomic state files and handoff contracts.

Can I use this bug triage workflow for user-reported stack traces?

Bug triage applies to user-reported bugs, stack traces, and GitHub issues, validating eligibility and gathering details through a phase-driven workflow before creating a sprint plan.

How do I generate a sprint plan after analyzing a codebase for a bug?

A sprint plan is generated by analyzing the codebase and creating an output contract that produces a sprint.md file, enforcing test-first methodologies and establishing a micro-sprint for the bug.

Does bug triage require manual eligibility checks before codebase analysis?

Eligibility checks are automated within the bug triage workflow, validating user-reported bugs and GitHub issues before proceeding to information gathering and codebase analysis phases.

What are the limitations of automated bug triage for sprint planning?

Automated bug triage requires tool availability checks and enforces guardrails, limiting execution when dependencies are missing or when potential injections are detected in the reported issue.