Guide systematic diagnosis and verification of recurring task failures.
npx skills add https://github.com/zhangdszq/vk-skills --skill pua-debugging-zhangdszq
Please help me install this Agent Skill. Skill: pua-debugging Source: https://github.com/zhangdszq/vk-skills/tree/main/debugging Command: npx skills add https://github.com/zhangdszq/vk-skills --skill pua-debugging-zhangdszq
Solves debugging paralysis by providing a proactive, end-to-end problem-solving framework that ensures issues are diagnosed comprehensively and resolved with accountability.
Run the pua-debugging workflow when you encounter a recurring failure to systematically diagnose, verify, and resolve the issue end-to-end.
High-intent search queries and answers about installing and using this skill.
To fix recurring task failures, you need a systematic debugging framework that guides you through evidence gathering, hypothesis validation, and end-to-end verification. This prevents debugging paralysis by enforcing a stepwise diagnosis from failure signals to root-cause fixes with an owner mindset.
Root-cause-analysis for configuration and deployment failures requires a proactive approach that reads failure signals and searches original materials to validate hypotheses. It applies a structured checklist to ensure diagnostic steps are automated and comprehensively verify issues across code, config, and data.
Yes, an automated debugging workflow can perform cross-file consistency checks by applying structured checklists for end-to-end verification. This ensures completeness and prevents surface-level fixes by validating regression and consistency across code, configuration, and deployment scenarios.
Systematic debugging prevents surface-level fixes by enforcing end-to-end verification with structured checklists after hypothesis validation. It ensures issues in data analysis or code are resolved with accountability by checking for completeness, regression, and cross-file consistency before considering the task complete.
Debugging stalls when tasks repeatedly fail because of a lack of systematic verification and proactive evidence gathering. Applying an end-to-end problem-solving framework resolves this paralysis by automating diagnostic steps, validating hypotheses, and verifying fixes across code, config, and deployment environments.
allexcdDiagnose, reproduce, and fix code defects from bug reports or error logs.
nimadorostkarEnforce test-driven development and root-cause analysis for bug resolution.
oxieDiagnose software errors, isolate root causes, and document fixes.
mlflowAnalyze failed GitHub Action jobs in pull requests to identify root causes.
