skills.rest
aizhimou
aizhimouCOMMUNITY
Explore all skills by this author →
Website𝕏@aizhimougGitHub

bug-analysis

Guide structured bug analysis for PigeonPod with reproduction and root-cause assessment.

1.2k|95|Updated Aug 23, 2025
Search Tags:#diagnostics#root-cause#reproduction#bug-analysis#bug-report#pigeonpod
One-click install
npx skills add https://github.com/aizhimou/pigeon-pod --skill bug-analysis-aizhimou
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bug-analysis
Source: https://github.com/aizhimou/pigeon-pod/tree/main/.agent/skills/bug-analysis
Command: npx skills add https://github.com/aizhimou/pigeon-pod --skill bug-analysis-aizhimou

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bug reports and regressions slow down development; this skill provides a rigorous, reproducible workflow to diagnose, triage, and plan fixes for PigeonPod issues.

Core Features & Use Cases

  • Structured bug intake and classification into frontend, backend, integration, data, performance, security, ops, or unknown.
  • Repro analysis, root-cause hypotheses, and risk assessment with a clear fix strategy and verification plan.
  • Documentation-first approach that reads repository docs and code before proposing changes.

Quick Start

Describe the bug in one paragraph, classify it, propose a fix plan, and outline verification steps.

Frequently Asked Questions about bug-analysis

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

FAQPage Schema
How do I analyze a bug report to find the root cause and plan a fix?▼

Bug analysis involves classifying the issue by category, formulating root-cause hypotheses, assessing regression risk, and outputting a formal bugfix recommendation with a structured verification plan.

What's the best way to reproduce an integration or backend bug in a repository?▼

Reproducing an integration or backend bug requires a documentation-first approach that reads current repository docs and code before proposing changes, ensuring accurate issue discovery and severity assessment.

How does root-cause assessment work for performance or security regressions?▼

Root-cause assessment for performance or security regressions works by guiding issue discovery and reproduction, then evaluating severity and regression-risk to propose a clear fix strategy and verification plan.

Can I diagnose frontend or ops bugs without manually checking external API documentation?▼

Yes, you can diagnose frontend or ops bugs efficiently because the workflow reads repository docs and code first, and uses MCP tools like Context7 only when framework, library, or external-service behavior must be verified.

Do I need to classify a bug before starting the reproduction and root-cause workflow?▼

Yes, classifying the bug into frontend, backend, integration, data, performance, security, ops, or unknown categories is a prerequisite step that structures the subsequent reproduction analysis and fix strategy.

Related Skills

Explore More Software Engineering Skills→
nuoyanruoshuinuoyanruoshui
47

bug-report

Generate structured bug reports from issue descriptions or code analysis findings.

Community
Advanced
avav25avav25
2

bugfix

Coordinate a traceable bugfix workflow with root-cause analysis and regression tests.

Community
Advanced
Ilenburg1993Ilenburg1993
3

context7-docs-ops

Retrieve external library documentation via Context7 MCP with version-specific details.

Community
Intermediate
darelabs-techdarelabs-tech

dare-bugfix-design

Analyze codebases to identify bug root causes and generate DARE/DESIGN-Bugfix plans.

Official
Advanced