{"enrichment":{"faq":[{"a":"vc-debug guides you through structured investigation before implementing any fix. Start by isolating the failure\u2014reproduce 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.","q":"How do I debug this error systematically with vc-debug?"},{"a":"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.","q":"What does vc-debug offer for root cause analysis of test failures?"},{"a":"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\u2014re-run the pipeline, confirm the specific failure no longer occurs, and validate downstream stages pass.","q":"How does vc-debug help with CI/CD pipeline failures?"},{"a":"Yes. vc-debug guides performance diagnostics by establishing baseline metrics, then isolating the degraded component\u2014slow 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.","q":"Can vc-debug help diagnose performance degradation?"},{"a":"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.","q":"What verification protocols does vc-debug recommend before claiming a fix is complete?"},{"a":"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.","q":"How does vc-debug help analyze logs and traces in multi-component systems?"}],"shadow_tags":["systematic-investigation","root-cause-identification","error-tracing","ci-cd-troubleshooting","performance-bottleneck","verification-workflow","multi-layer-validation","incident-response"],"summary_rewrite":"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\u2014from call stack analysis to log inspection to frontend verification."},"files":[{"bytes":5869,"path":".claude/skills/vc-debug/SKILL.md","sha256":"acb05feab1a8e7662286e5f9d63eedf5dd3515a55ea91449c1d5b0251071b809","url":"https://skillfed.io/files/withkynam/vibecode-pro-max-kit/vc-debug/efeb36b3/SKILL.md"}],"id":"withkynam/vibecode-pro-max-kit/vc-debug","links":{"html":"https://skillfed.io/withkynam/vibecode-pro-max-kit/vc-debug","md":"https://skillfed.io/withkynam/vibecode-pro-max-kit/vc-debug.md","repo":"https://github.com/withkynam/vibecode-pro-max-kit"},"meta":{"agents_supported":["claude-code"],"first_seen":"2026-07-28","forks":219,"language":"JavaScript","last_updated":"2026-06-21","license":"MIT","name":"vc-debug","publisher":"withkynam","stars":1058},"relations":{"categories":["debugging","devops","qa-testing"],"similar":[{"id":"samhvw8/dotfiles/code-quality"},{"id":"samhvw8/dot-claude/debugging"},{"id":"Delphine-L/claude_global/systematic-debugging"},{"id":"withkynam/vibecode-pro-max-kit/vc-agent-browser"},{"id":"jnMetaCode/superpowers-zh/systematic-debugging"},{"id":"withkynam/vibecode-pro-max-kit/vc-scout"},{"id":"Ibrahim-3d/orchestrator-supaconductor/systematic-debugging"},{"id":"xintaofei/codeg/systematic-debugging"},{"id":"guanyang/open-agent-hub/systematic-debugging"},{"id":"obra/superpowers/systematic-debugging"}]},"slug":{"owner":"withkynam","repo":"vibecode-pro-max-kit","skill":"vc-debug"},"version":"efeb36b3"}