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
Decision gist · record as of 2026-06-21
vc-debug systematically traces root causes of bugs and system issues before implementing fixes. 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.
Use it when
- vc-debug provides structured methodology for test failure investigation.
- vc-debug applies systematic investigation to pipeline failures by breaking down multi-stage workflows.
Verify before relying
Read SKILL.md below before installing (13 files). Open directory: indexed for reading, not audited.
Install
withkynam/vibecode-pro-max-kit/vc-debug · repository language: JavaScript
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
Frequently 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)
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
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Systematically investigate and trace root cause of bugs before implementing fixes”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
Debugging provides a four-phase framework for investigating issues methodically rather than applying random fixes. It combines root cause tracing through call stacks, defense-in-depth validation across system layers, and verification protocols to confirm fixes work before claiming success.
vc-scout finds files across your codebase using shell search patterns and optional parallel research agents to divide large search spaces. Use it when you need to locate specific files, understand project structure, or gather context before starting work on features spanning multiple directories.
Systematic Debugging teaches a disciplined 4-phase approach: root cause investigation, pattern analysis, hypothesis testing, and implementation. Rather than attempting quick fixes, this skill enforces tracing issues back to their source through careful error analysis, data flow tracking, and minimal testing before any code change.
vc-generate-plan transforms feature ideas and product requirements into structured implementation plan artifacts saved to your repo. It handles both straightforward single-phase work and large multi-phase programs, organizing plans with required sections for touchpoints, contracts, blast radius, and verification gates. The skill enforces answer-first communication and ensures execution handoff clarity through explicit resume notes.
This skill teaches the red-green-refactor cycle: write a failing test, verify it fails for the right reason, implement just enough code to pass, then refactor. Follow the iron law—no production code without a failing test first—and use this approach for all features, bug fixes, and refactoring work.
vc-autopilot is a contract skill that owns the provisional goal block artifact for Autopilot Mode. It emits the structured 9-field block after clarification, detects resume scenarios from pasted blocks, and validates artifacts against the D1 spec. The skill also handles V7 UPDATE variants when validation completes.
More skills systematic-debugging (MIT) · team-frontend-debug (MIT) · vc-generate-spec (MIT) · vc-generate-phase-program (MIT) · vc-setup (MIT) · vc-audit-context (MIT)