skills.rest
thegeronimo
thegeronimoCOMMUNITY
Explore all skills by this author →
𝕏@RyskyGeronimoGitHub

bug-flow

Diagnose unclear bugs and regressions with a structured findings-first workflow.

44|8|Updated Jul 14, 2025
Search Tags:#workflow#debugging#regression#diagnosis#bug#repro#bug-flow
One-click install
npx skills add https://github.com/thegeronimo/hyperopen --skill bug-flow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bug-flow
Source: https://github.com/thegeronimo/hyperopen/tree/main/.agents/skills/bug-flow
Command: npx skills add https://github.com/thegeronimo/hyperopen --skill bug-flow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clear, structured diagnosis for unclear bugs, regressions, or failures to produce reproducible fix paths and validated outcomes.

Core Features & Use Cases

  • Guided Diagnosis: Follows a defined workflow to isolate root cause using logs, repro steps, and evidence.
  • Regression-First Testing: Plans and captures deterministic tests to verify fixes and prevent regressions.
  • Audit Trail & Review: Documents steps, decisions, and ownership for findings-first review.

Quick Start

Start a bug-flow session to diagnose an unclear failure by following the structured workflow from reproduction to regression verification.

Frequently Asked Questions about bug-flow

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

FAQPage Schema
How do I diagnose an unclear software regression when the root cause is unknown?▼

Diagnose unclear software regressions using a structured, findings-first workflow that guides steps from reproduction to regression verification, isolating the root cause through logs and evidence.

What is a findings-first bug diagnosis workflow?▼

A findings-first bug diagnosis workflow imposes a concrete orchestration of debugger usage, automated tests, and reviewer handoffs to capture explicit reproduction steps, root cause, and change validation.

How do I structure bug reproduction steps for backend and UI integration issues?▼

Structure bug reproduction steps by following a defined workflow that isolates the root cause across UI, backend, and integration issues, documenting evidence and deterministic repro steps for review.

Can I use an automated testing workflow to verify bug fixes and prevent future regressions?▼

Yes, you can plan and capture deterministic automated tests to verify fixes and prevent regressions, ensuring validated outcomes through regression-first testing within the diagnosis workflow.

What is the best way to document an audit trail for bug diagnosis and reviewer handoffs?▼

Document an audit trail for reviewer handoffs by capturing steps, decisions, and ownership throughout the bug diagnosis workflow, ensuring a findings-first review with validated change outcomes.

When should I use a structured workflow for debugging instead of ad hoc investigation?▼

Use a structured debugging workflow when failures are not well understood, spanning UI, backend, and integration issues, to produce reproducible fix paths and validated outcomes instead of ad hoc guesses.

Related Skills

Explore More Software Engineering Skills→
karithamkaritham
2

debugging

Document failure evidence and isolate root causes with hypothesis testing.

Community
Advanced
aist-ai-sastaist-ai-sast

mcp-regression-fix

Diagnose MCP regression failures and implement durable fixes across test suites.

Official
Advanced
HomericIntelligenceHomericIntelligence
18

run-tests

Execute Mojo or Python test suites and generate validation reports.

Official
Basic
astronomerastronomer
419

debugging-dags

Diagnose Airflow DAG failures and identify root causes across pipelines.

Official
Basic