skills.rest
withkynam
withkynamCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

vc-debug

Trace root causes of bugs and failures through a four-phase investigation workflow.

1.1k|223|Updated May 27, 2026
Search Tags:#debugging#investigation#logs#verification#ci-cd#root-cause#systematic-debugging
One-click install
npx skills add https://github.com/withkynam/vibecode-pro-max-kit --skill vc-debug-withkynam
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vc-debug
Source: https://github.com/withkynam/vibecode-pro-max-kit/tree/main/.claude/skills/vc-debug
Command: npx skills add https://github.com/withkynam/vibecode-pro-max-kit --skill vc-debug-withkynam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The vc-debug Skill helps you systematically diagnose and root-cause bugs, failures, and performance issues before attempting fixes.

Core Features & Use Cases

  • Four-phase debugging framework: Phase 1 Root Cause Investigation, Phase 2 Pattern Analysis, Phase 3 Hypothesis Testing, Phase 4 Implementation.
  • NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST — trace data flow across components, validate at every layer, and verify outcomes.
  • Use cases include code failures, system incidents, CI/CD pipeline issues, and performance regressions with evidence-guided fixes.

Quick Start

Provide the issue description to vc-debug and initiate a four-phase root-cause investigation workflow.

Frequently Asked Questions about vc-debug

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

FAQPage Schema
How do I systematically find the root cause of a bug before applying a fix?▼

To find the root cause of a bug systematically, follow a four-phase debugging workflow: root cause investigation, pattern analysis, hypothesis testing, and implementation. This ensures no fixes proceed without tracing data flow and validating evidence.

What is the best way to debug CI/CD pipeline failures across different environments?▼

Debugging CI/CD pipeline failures requires evidence gathering and data-flow tracing across software stacks and test suites. A systematic debugging framework investigates the root cause across environments before applying fixes.

How do I investigate performance regressions using a systematic debugging approach?▼

Investigating performance regressions involves identifying the root cause through pattern analysis and hypothesis testing. You trace data flow across components and validate evidence at every layer before implementing fixes.

Why should I trace data flow across components before fixing a system incident?▼

Tracing data flow across components before fixing a system incident prevents premature patching. Root-cause investigation validates evidence at every layer, ensuring the implemented fix addresses the actual failure.

Can I use systematic debugging for code-level defects without gathering logs first?▼

Systematic debugging for code-level defects requires evidence gathering and log verification first. The workflow enforces a no-fixes-without-root-cause rule, meaning you must trace data flow and validate outcomes before implementation.

Related Skills

Explore More Software Engineering Skills→
keremtoker468-dotcomkeremtoker468-dotcom

systematic-debugging

Guide hypothesis-driven debugging through four phases for root cause analysis.

Community
Advanced
u9401066u9401066
1

bug-fix

Enforce a structured bug-fixing workflow with regression tests and root-cause analysis.

Community
Advanced
ChatAndBuildChatAndBuild
1

ci-monitor

Monitor CI pipeline health and prioritize failing jobs with remediation steps.

Official
Advanced
openeuler-mirroropeneuler-mirror
3

root-cause-analysis

Identify fundamental causes of complex system failures using causal inference and historical pattern matching.

Official
Advanced