vibe-debugger

Automate bug investigation workflows with human review phases and generate BUG_REPORT.md files.

Updated Feb 5, 2026
One-click install
npx skills add https://github.com/thongpham95/ai-meeting-summary --skill vibe-debugger
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vibe-debugger
Source: https://github.com/thongpham95/ai-meeting-summary/tree/main/.claude/skills/vibe-debugger
Command: npx skills add https://github.com/thongpham95/ai-meeting-summary --skill vibe-debugger

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a repeatable, collaborative workflow to research, document, analyze, fix, and verify bugs with human oversight, producing clear artifacts to guide resolution.

Core Features & Use Cases

  • Structured Phases: Research, Bug Report generation, Human review, Implement fix, and Verification in a disciplined sequence.
  • Artifact Creation: Automatically creates or updates a BUG_REPORT.md containing root-cause analysis, proposed fixes, and verification steps.
  • Human-in-the-Loop: Explicit human review phase ensures accurate validation and approval before changes are applied.

Quick Start

Provide bug context (error messages, logs, screenshots, and environment details) and trigger the vibe-debugger workflow to produce a BUG_REPORT.md for review.

Frequently Asked Questions about vibe-debugger

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

FAQPage Schema
How do I structure a bug investigation workflow with human review?

A structured bug investigation workflow automates research, root-cause analysis, and human-in-the-loop review. It processes error messages and environment details, requiring explicit human approval before applying fixes and generating a BUG_REPORT.md artifact.

What is the best way to document root-cause analysis for a bug report?

Documenting root-cause analysis is best handled by generating a structured BUG_REPORT.md file. This artifact captures the bug status, environment details, proposed fixes, and verification steps to guide collaborative resolution.

How do I create a bug triage process that requires human approval before fixing?

To create a bug triage process with human approval, you implement a phased workflow where research and documentation precede a mandatory human review phase. This ensures validation occurs before any proposed fixes are applied.

Can I use a human-in-the-loop debugging workflow for logs and environment details?

Yes, a human-in-the-loop debugging workflow specifically targets bug reports featuring error messages, logs, screenshots, and environment details. It processes these inputs to produce a structured report for human validation.

What are the steps to automate bug documentation while keeping human oversight?

Automating bug documentation with human oversight involves five sequential phases: research, bug report generation, human review, implementing the fix, and verification. This disciplined sequence ensures artifacts are validated before changes are applied.

When do I need a structured debugging workflow instead of directly fixing bugs?

You need a structured debugging workflow when bugs require collaborative investigation and disciplined documentation across projects. It ensures a human review phase validates the root-cause analysis and proposed fixes before resolution.