skills.rest
JZKK720
JZKK720COMMUNITY
Explore all skills by this author →
GitHub

po-diagnose

Diagnose hard-to-reproduce bugs through systematic analysis and reproduction loops.

Updated Jun 8, 2026
Search Tags:#bug diagnosis#systematic debugging#debugging tool#bug reproducibility#bug hypothesis generation
One-click install
npx skills add https://github.com/JZKK720/cubecloud-agentic-os --skill po-diagnose
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: po-diagnose
Source: https://github.com/JZKK720/cubecloud-agentic-os/tree/main/.agents/skills/po-diagnose
Command: npx skills add https://github.com/JZKK720/cubecloud-agentic-os --skill po-diagnose

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The 'po-diagnose' Skill provides a systematic approach to diagnosing hard bugs, helping developers quickly identify and resolve issues.

Core Features & Use Cases

  • Bug Diagnostics: Offers a structured approach to identifying and addressing hard bugs.
  • Reproduction Loop: Facilitates the construction of loops to determine if the bug can be reliably replicated.
  • Hypothesis Generation: Aids in generating multiple hypotheses for the cause of the bug before testing them.
  • Instrumentation: Assists with instrumenting the system to observe the effects of the bug.

Quick Start

Use the 'po-diagnose' skill to diagnose the issue in your project by constructing a reproduction loop.

Frequently Asked Questions about po-diagnose

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

FAQPage Schema
How do I diagnose hard-to-reproduce bugs systematically?▼

Systematic debugging of hard bugs involves creating a reproduction loop to reliably replicate the issue, generating multiple hypotheses for the cause, and instrumenting the system to observe effects.

What is a reproduction loop and how does it help with bug diagnosis?▼

A reproduction loop is a structured method to reliably replicate a bug, helping bug diagnosis by providing a consistent environment to test hypotheses and instrument the system for observable effects.

What's the best way to find the cause of a bug when the cause is unclear?▼

The best way to find the cause of an unclear bug is generating multiple hypotheses for the cause before testing them, then instrumenting the system to observe effects and validate each hypothesis.

Does systematic debugging work for non-reproducible bugs?▼

Systematic debugging works for non-reproducible bugs by applying structured methods to hypothesize causes and instrument the system, effectively analyzing scenarios where the cause is unclear or non-reproducible.

When should I use a systematic debugging tool for software engineering workflows?▼

Use a systematic debugging tool for software engineering workflows when encountering scenarios where the cause of a bug is unclear or non-reproducible, requiring structured analysis and instrumentation to resolve.

Related Skills

Explore More Software Engineering Skills→
kynoptickynoptic
1

Debugging Runtime Errors

Analyze stack traces and error logs to identify root causes and propose fixes.

Community
Advanced
arvindbattulaarvindbattula

debugging

Diagnose root-cause failures with a structured triage workflow.

Community
Advanced
RakameNouyaRakameNouya

profiler-save-data

Capture Unity profiler statistics into a JSON file using built-in APIs.

Community
Basic
airoweairowe
14

Accessibility Audit Skill

Audit web projects for WCAG 2.1 violations using axe-core and eslint-plugin-jsx-a11y.

Community
Advanced