skills.rest
adhi-jp
adhi-jpCOMMUNITY
Explore all skills by this author →
GitHub

vibe-debug-fix

Translate user-reported symptoms into observable behavior, proof paths, and closure criteria.

Updated Mar 1, 2026
Search Tags:#workflow#debugging#traceability#root-cause-analysis#bug-fix#vibe-coding
One-click install
npx skills add https://github.com/adhi-jp/agent-skills --skill vibe-debug-fix
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vibe-debug-fix
Source: https://github.com/adhi-jp/agent-skills/tree/main/skills/vibe-debug-fix
Command: npx skills add https://github.com/adhi-jp/agent-skills --skill vibe-debug-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translates vague runtime issues and user reports into observable symptoms, proof paths, and closure criteria to guide safe repairs.

Core Features & Use Cases

  • Structured debugging ledger to track symptoms, hypotheses, and verification steps.
  • Guided workflow with source routing, bounded probes, and explicit closure criteria.
  • Evidence-driven repairs with artifact freshness and user retest contracts.

Quick Start

Record the current symptom and relevant logs, then start the debug ledger.

Frequently Asked Questions about vibe-debug-fix

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

FAQPage Schema
How do I trace a vague bug report to its root cause before applying a fix?▼

A structured debugging workflow tracks vague bug reports by translating symptoms into observable behavior, proof paths, and closure criteria, ensuring repairs are traced to root cause before changes.

What is the best way to structure a debugging workflow for regression repairs?▼

The best way to structure a debugging workflow for regression repairs is to maintain a debug ledger that logs symptoms, hypotheses, source routing, bounded probes, and explicit closure criteria for verifiable fixes.

How do I verify a bug fix closure with artifact freshness in vibe-coding?▼

To verify bug fix closure in vibe-coding, you produce verifiable closure criteria with artifact freshness and establish a user retest contract, ensuring the evidence-driven repair satisfies the debug workflow requirements.

Can I use source routing and bounded probes for environment-specific failures?▼

Yes, source routing and bounded probes can diagnose environment-specific failures by guiding the debug workflow, allowing you to isolate observable symptoms and record proof paths within a structured debug ledger.

When do I need a debug ledger for bug fixing?▼

You need a debug ledger for bug fixing when translating user-reported symptoms into observable behavior and proof paths, ensuring repairs are traced to root cause before changes are applied.

Related Skills

Explore More Software Engineering Skills→
Pryma-TechPryma-Tech

debug

Diagnose OMC session or repository failures from logs and traces.

Community
Intermediate
korchasakorchasa

fix-tests

Diagnose and correct root causes of test failures by executing scripts in a controlled environment.

Community
Advanced
zhengxuyuzhengxuyu

Pol Probe

Defines and documents Proof of Life probes for validating product hypotheses.

Community
Intermediate
distribucionesfayosmoreno-sysdistribucionesfayosmoreno-sys

ui-visual-validator

Validate UI modifications for visual regression, compliance, and accessibility.

Community
Advanced