Enforce root-cause analysis and verification for debugging failures.
npx skills add https://github.com/zjh08177/agent-harness --skill pua-debugging-zjh08177
Please help me install this Agent Skill. Skill: pua-debugging Source: https://github.com/zjh08177/agent-harness/tree/main/skills/pua-debugging Command: npx skills add https://github.com/zjh08177/agent-harness --skill pua-debugging-zjh08177
This Skill helps teams and individuals overcome repeated debugging failures by enforcing proactive ownership, methodical diagnosis, and verifiable resolutions.
Validate a failing task by performing an end-to-end debugging cycle and reporting a verified resolution.
High-intent search queries and answers about installing and using this skill.
Systematic debugging requires enforcing proactive ownership and root-cause analysis. You must gather evidence, create minimal reproductions, and perform cross-checks to uncover the true source of failures rather than addressing surface symptoms.
To ensure a verified fix, apply end-to-end ownership throughout your debugging workflow. This means validating resolutions through thorough verification and checking for related issues across code, configuration, and deployment workflows before declaring completion.
Root-cause analysis for deployment failures involves proactive discovery and expanding investigations beyond the initial error. You must gather evidence, establish a minimal reproduction, and perform cross-checks across data workflows to isolate the origin.
Yes, you can apply a repeatable five-step debugging workflow to both code and data pipeline issues. This systematic approach enforces evidence gathering and proactive verification across diverse environments to achieve verifiable resolutions.
Debugging fixes fail when teams lack end-to-end ownership and declare completion prematurely. Resolving this requires thorough validation, cross-checks, and verifying the fix against a minimal reproduction before deployment to ensure the root cause is eliminated.
Yes, systematic debugging requires checking for related issues after finding a root cause. Proactive discovery means expanding investigations beyond the first error to ensure comprehensive diagnosis and verifying that related configurations or data workflows are unaffected.
AdemKaoDiagnose and fix codebase bugs through structured root-cause analysis.
Terryc21Coordinate end-to-end debugging workflows to reproduce, isolate, and verify fixes.
burgebjAutomate testing, code review, pull request creation, and deployment workflows.
LuminaVaultMonitor log files and metrics, detect anomalies, and generate deduplicated context-aware alerts.
