vc-debug
vc-debug guides you through structured investigation before any fix, combining root cause tracing, defense-in-depth validation, and verification protocols. Handle code bugs, system failures, CI/CD issues, and performance degradation with frameworks for each scenario—from call stack analysis to log inspection to frontend verification.
vc-debug systematically traces root causes of bugs and system issues before implementing fixes.
AI-generated summary based on this skill's SKILL.md
Install
withkynam/vibecode-pro-max-kit/vc-debug · repository language: JavaScript
git clone https://github.com/withkynam/vibecode-pro-max-kit
cp -r vibecode-pro-max-kit/.claude/skills/vc-debug ~/.claude/skills/vc-debugnpx skillfed install withkynam/vibecode-pro-max-kit/vc-debugFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I debug this error systematically with vc-debug?
vc-debug guides you through structured investigation before implementing any fix. Start by isolating the failure—reproduce it consistently, capture logs and stack traces, and identify the component where symptoms first appear. Then trace backward through call stacks, dependencies, and system state to find root cause. vc-debug provides frameworks for code bugs, CI/CD failures, performance issues, and multi-component system failures, ensuring you understand *why* before you change anything.
What does vc-debug offer for root cause analysis of test failures?
vc-debug provides structured methodology for test failure investigation. Identify whether the failure is deterministic or flaky; if flaky, use bisection scripts to narrow down test pollution or environmental factors. Examine test setup, teardown, and isolation. Analyze logs across test runs and correlate timing with system state changes. vc-debug's defense-in-depth validation ensures you verify the actual root cause, not just a symptom, before claiming resolution.
How does vc-debug help with CI/CD pipeline failures?
vc-debug applies systematic investigation to pipeline failures by breaking down multi-stage workflows. Isolate which stage fails, gather logs from that stage and upstream dependencies, and trace the failure chain. Check environment variables, secrets, resource constraints, and timing issues. vc-debug emphasizes verification before claiming the fix works—re-run the pipeline, confirm the specific failure no longer occurs, and validate downstream stages pass.
Can vc-debug help diagnose performance degradation?
Yes. vc-debug guides performance diagnostics by establishing baseline metrics, then isolating the degraded component—slow queries, high CPU, memory leaks, or frontend rendering delays. Analyze logs and traces to correlate timing of degradation with code changes, load patterns, or infrastructure shifts. vc-debug's framework helps you identify bottlenecks, measure impact, and verify optimizations actually resolve the issue before deployment.
What verification protocols does vc-debug recommend before claiming a fix is complete?
vc-debug emphasizes defense-in-depth validation: reproduce the original failure to confirm it still occurs without your fix, apply the fix, then verify the failure no longer appears. Run related tests and integration checks. Monitor logs for side effects. Test edge cases and boundary conditions. Document what you changed and why. vc-debug ensures you don't claim resolution until multi-step verification confirms the bug is actually gone and no new issues emerged.
How does vc-debug help analyze logs and traces in multi-component systems?
vc-debug provides log analysis and correlation frameworks for distributed failures. Collect logs from all affected components and correlate by timestamp, request ID, or transaction ID. Trace the failure path across service boundaries. Identify where latency increases, errors originate, or state diverges. vc-debug's methodology helps you reconstruct the sequence of events, spot cascading failures, and pinpoint which component's behavior triggered the chain reaction.
SKILL.md
rendered from the published skill — quoted content, verbatim
Debugging & System Investigation
> Output style: Follow process/development-protocols/communication-standards.md — answer-first, plain language, no unexplained jargon, TL;DR on long responses.
Comprehensive framework combining systematic debugging, root cause tracing, defense-in-depth validation, verification protocols, and system-level investigation (logs, CI/CD, databases, performance).
Core Principle
NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST
Random fixes waste time and create new bugs. Find root cause, fix at source, validate at every layer, verify before claiming success.
When to Use
Code-level: Test failures, bugs, unexpected behavior, build failures, integration problems System-level: Server errors, CI/CD pipeline failures, performance degradation,
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 13 files
.claude/skills/vc-debug/SKILL.md
.claude/skills/vc-debug/references/defense-in-depth.md
.claude/skills/vc-debug/references/frontend-verification.md
.claude/skills/vc-debug/references/investigation-methodology.md
.claude/skills/vc-debug/references/log-and-ci-analysis.md
.claude/skills/vc-debug/references/performance-diagnostics.md
.claude/skills/vc-debug/references/reporting-standards.md
.claude/skills/vc-debug/references/root-cause-tracing.md
.claude/skills/vc-debug/references/systematic-debugging.md
.claude/skills/vc-debug/references/task-management-debugging.md
.claude/skills/vc-debug/references/verification.md
.claude/skills/vc-debug/scripts/find-polluter.sh
.claude/skills/vc-debug/scripts/find-polluter.test.md