validate-bug

Name: validate-bug
Availability: InStock
Author: Unblocked

Validate bug reports and produce structured findings with timelines and root-cause hypotheses.

13|1|Updated Mar 24, 2026

Search Tags:#timeline #root-cause #issue-tracker #bug-triage #bug-validation #findings-template

Ready to run

npx skills add https://github.com/unblocked/cookbook --skill validate-bug

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: validate-bug
Source: https://github.com/unblocked/cookbook/tree/main/recipes/validate-bug
Command: npx skills add https://github.com/unblocked/cookbook --skill validate-bug

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Bug report validation that investigates whether a bug is real, what likely caused it, and whether it has happened before. Applies to triaging bug reports from any issue tracker (Jira, Linear, GitHub Issues, etc.), correlating symptoms with recent changes, checking prior history, and verifying against code. Presents structured findings to the user. Does not implement a fix.

Core Features & Use Cases

Structured bug validation: Correlates symptoms with recent changes and prior history to determine if a bug truly occurred.
Timeline construction: Builds a chronological narrative of events, deployments, and related issues.
Findings delivery: Outputs a structured Findings Template ready report for stakeholders.

Quick Start

Provide a bug report prompt, and let the Skill investigate, correlate changes, and output structured findings.

Frequently Asked Questions about validate-bug

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

FAQPage Schema

How do I validate a bug report from Jira or Linear to see if the issue is real?▼

To validate a bug report, provide the triage prompt to the Skill. It correlates symptoms with recent deployments and code history, then outputs a validated timeline, root-cause hypotheses, and recommended next steps in a structured report.

What is the best way to triage bug reports and correlate symptoms with recent deployments?▼

The best way to triage bug reports is to correlate reported symptoms with recent deployments and prior history. This process constructs a chronological timeline of events and related issues, verifying the bug against code to produce structured findings.

Does bug validation work with GitHub Issues and other issue trackers?▼

Yes, bug validation works with GitHub Issues and other issue trackers like Jira and Linear. It processes triage prompts from any tracker by investigating the bug report context and code history to output structured findings.

How do I generate a root-cause hypothesis for a validated bug?▼

You generate a root-cause hypothesis by investigating the bug report context and correlating symptoms with recent code history. The validation process surfaces root-cause hypotheses and recommended next steps within a structured findings template.

What are the limitations of using automated bug validation for issue triage?▼

The main limitation of automated bug validation is that it does not implement a fix. It only investigates the bug report, validates the timeline, surfaces root-cause hypotheses, and outputs a structured findings template for stakeholders to act upon.