bug-triage-analysis

Triage bug reports against the current codebase without modifying files.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate and triage bug reports against the current codebase without modifying files, determining if issues are real, missing inputs, or contradictions.

Core Features & Use Cases

  • Parse bug reports to extract expected vs observed behavior, scope, environment, and reproduction steps.
  • Locate entrypoints, configs, tests, fixtures, and docs related to the reported behavior using code search that is bounded to the affected surface.
  • Validate against the current implementation, reproduce when feasible, and identify falsification or confirmation evidence.
  • Classify the bug surface, identify the invariant, and propose bounded, testable fix options with tradeoffs.
  • Produce a compact, plan-ready handoff including source of truth, affected tests, first failing conditions, and documentation updates.

Quick Start

Provide a bug report payload and let the skill triage it without changing any source files.

Frequently Asked Questions about bug-triage-analysis

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

FAQPage Schema
How do I triage bug reports against my codebase without modifying source files?

Bug triage analysis validates bug reports against the current codebase without modifying files. It identifies bug validity, reproduces the minimal surface, and classifies the issue as Confirmed, Not reproducible, or Needs info before proposing bounded fix options.

What is the best way to analyze a bug report and classify it for developer handoff?

Bug report analysis locates affected entrypoints and configs, validates the implementation, and classifies the bug surface. It produces a compact, plan-ready handoff detailing the invariant, source of truth, dependent tests, and required documentation updates.

Can I reproduce a minimal bug surface and identify falsification evidence during code review?

Yes, bug triage analysis can reproduce a minimal bug surface during code review. It searches bounded affected areas for tests and fixtures, validates the current implementation, and identifies falsification or confirmation evidence without changing any source files.

How do I validate a bug and propose bounded, testable fix options with tradeoffs?

You validate a bug and propose bounded fix options by classifying the bug surface and identifying the invariant. This generates testable fixes with clear tradeoffs, resulting in a plan-ready handoff specifying the source of truth and first failing conditions.

Does bug triage analysis work without dependencies or specific test frameworks?

Bug triage analysis works without dependencies. It uses code search bounded to the affected surface to locate existing entrypoints, tests, and fixtures, meaning it adapts to your current codebase setup without requiring specific external test frameworks.

When should I not use an automated bug triage workflow for issue reproduction?

Avoid automated bug triage when a bug report lacks clear reproduction steps or environment details. The workflow requires parsing expected versus observed behavior, so missing inputs or contradictions will halt the validation and classification process.