[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6EYFQQPECSDHV7WN6T4X1JS":3,"skill-same:01M6EYFQQPECSDHV7WN6T4X1JS":69},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":28,"publishedAt":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":40,"commitSha":41,"skillDirectory":42,"forksCount":43,"repositoryHtmlUrl":44,"repositoryHomepageUrl":45,"ownerHtmlUrl":46,"ownerBlogUrl":6,"ownerDescription":47,"updatedAt":48,"install":49,"resources":62},"01M6EYFQQPECSDHV7WN6T4X1JS","error-diagnostics-smart-debug",null,"Use when working with error diagnostics smart debug","ComeOnOliver\u002Fskillshub","ComeOnOliver","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F43215937?v=4","01M6E5JNFECJAAVFE0W7SMWWD2","Haoran Shu","01M6E5JNNDQS7AJZDYFQ8TPZCK",66,"MIT","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fsickn33\u002Ferror-diagnostics-smart-debug\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[29,30,31,32,33,34],"debug","diagnostics","error diagnostics smart debug","error","use","with","2026-11-10 10:12:30",false,"---\nname: error-diagnostics-smart-debug\ndescription: \"Use when working with error diagnostics smart debug\"\n---\n\n## Use this skill when\n\n- Working on error diagnostics smart debug tasks or workflows\n- Needing guidance, best practices, or checklists for error diagnostics smart debug\n\n## Do not use this skill when\n\n- The task is unrelated to error diagnostics smart debug\n- You need a different domain or tool outside this scope\n\n## Instructions\n\n- Clarify goals, constraints, and required inputs.\n- Apply relevant best practices and validate outcomes.\n- Provide actionable steps and verification.\n- If detailed examples are required, open `resources\u002Fimplementation-playbook.md`.\n\nYou are an expert AI-assisted debugging specialist with deep knowledge of modern debugging tools, observability platforms, and automated root cause analysis.\n\n## Context\n\nProcess issue from: $ARGUMENTS\n\nParse for:\n- Error messages\u002Fstack traces\n- Reproduction steps\n- Affected components\u002Fservices\n- Performance characteristics\n- Environment (dev\u002Fstaging\u002Fproduction)\n- Failure patterns (intermittent\u002Fconsistent)\n\n## Workflow\n\n### 1. Initial Triage\nUse Task tool (subagent_type=\"debugger\") for AI-powered analysis:\n- Error pattern recognition\n- Stack trace analysis with probable causes\n- Component dependency analysis\n- Severity assessment\n- Generate 3-5 ranked hypotheses\n- Recommend debugging strategy\n\n### 2. Observability Data Collection\nFor production\u002Fstaging issues, gather:\n- Error tracking (Sentry, Rollbar, Bugsnag)\n- APM metrics (DataDog, New Relic, Dynatrace)\n- Distributed traces (Jaeger, Zipkin, Honeycomb)\n- Log aggregation (ELK, Splunk, Loki)\n- Session replays (LogRocket, FullStory)\n\nQuery for:\n- Error frequency\u002Ftrends\n- Affected user cohorts\n- Environment-specific patterns\n- Related errors\u002Fwarnings\n- Performance degradation correlation\n- Deployment timeline correlation\n\n### 3. Hypothesis Generation\nFor each hypothesis include:\n- Probability score (0-100%)\n- Supporting evidence from logs\u002Ftraces\u002Fcode\n- Falsification criteria\n- Testing approach\n- Expected symptoms if true\n\nCommon categories:\n- Logic errors (race conditions, null handling)\n- State management (stale cache, incorrect transitions)\n- Integration failures (API changes, timeouts, auth)\n- Resource exhaustion (memory leaks, connection pools)\n- Configuration drift (env vars, feature flags)\n- Data corruption (schema mismatches, encoding)\n\n### 4. Strategy Selection\nSelect based on issue characteristics:\n\n**Interactive Debugging**: Reproducible locally → VS Code\u002FChrome DevTools, step-through\n**Observability-Driven**: Production issues → Sentry\u002FDataDog\u002FHoneycomb, trace analysis\n**Time-Travel**: Complex state issues → rr\u002FRedux DevTools, record & replay\n**Chaos Engineering**: Intermittent under load → Chaos Monkey\u002FGremlin, inject failures\n**Statistical**: Small % of cases → Delta debugging, compare success vs failure\n\n### 5. Intelligent Instrumentation\nAI suggests optimal breakpoint\u002Flogpoint locations:\n- Entry points to affected functionality\n- Decision nodes where behavior diverges\n- State mutation points\n- External integration boundaries\n- Error handling paths\n\nUse conditional breakpoints and logpoints for production-like environments.\n\n### 6. Production-Safe Techniques\n**Dynamic Instrumentation**: OpenTelemetry spans, non-invasive attributes\n**Feature-Flagged Debug Logging**: Conditional logging for specific users\n**Sampling-Based Profiling**: Continuous profiling with minimal overhead (Pyroscope)\n**Read-Only Debug Endpoints**: Protected by auth, rate-limited state inspection\n**Gradual Traffic Shifting**: Canary deploy debug version to 10% traffic\n\n### 7. Root Cause Analysis\nAI-powered code flow analysis:\n- Full execution path reconstruction\n- Variable state tracking at decision points\n- External dependency interaction analysis\n- Timing\u002Fsequence diagram generation\n- Code smell detection\n- Similar bug pattern identification\n- Fix complexity estimation\n\n### 8. Fix Implementation\nAI generates fix with:\n- Code changes required\n- Impact assessment\n- Risk level\n- Test coverage needs\n- Rollback strategy\n\n### 9. Validation\nPost-fix verification:\n- Run test suite\n- Performance comparison (baseline vs fix)\n- Canary deployment (monitor error rate)\n- AI code review of fix\n\nSuccess criteria:\n- Tests pass\n- No performance regression\n- Error rate unchanged or decreased\n- No new edge cases introduced\n\n### 10. Prevention\n- Generate regression tests using AI\n- Update knowledge base with root cause\n- Add monitoring\u002Falerts for similar issues\n- Document troubleshooting steps in runbook\n\n## Example: Minimal Debug Session\n\n```typescript\n\u002F\u002F Issue: \"Checkout timeout errors (intermittent)\"\n\n\u002F\u002F 1. Initial analysis\nconst analysis = await aiAnalyze({\n  error: \"Payment processing timeout\",\n  frequency: \"5% of checkouts\",\n  environment: \"production\"\n});\n\u002F\u002F AI suggests: \"Likely N+1 query or external API timeout\"\n\n\u002F\u002F 2. Gather observability data\nconst sentryData = await getSentryIssue(\"CHECKOUT_TIMEOUT\");\nconst ddTraces = await getDataDogTraces({\n  service: \"checkout\",\n  operation: \"process_payment\",\n  duration: \">5000ms\"\n});\n\n\u002F\u002F 3. Analyze traces\n\u002F\u002F AI identifies: 15+ sequential DB queries per checkout\n\u002F\u002F Hypothesis: N+1 query in payment method loading\n\n\u002F\u002F 4. Add instrumentation\nspan.setAttribute('debug.queryCount', queryCount);\nspan.setAttribute('debug.paymentMethodId', methodId);\n\n\u002F\u002F 5. Deploy to 10% traffic, monitor\n\u002F\u002F Confirmed: N+1 pattern in payment verification\n\n\u002F\u002F 6. AI generates fix\n\u002F\u002F Replace sequential queries with batch query\n\n\u002F\u002F 7. Validate\n\u002F\u002F - Tests pass\n\u002F\u002F - Latency reduced 70%\n\u002F\u002F - Query count: 15 → 1\n```\n\n## Output Format\n\nProvide structured report:\n1. **Issue Summary**: Error, frequency, impact\n2. **Root Cause**: Detailed diagnosis with evidence\n3. **Fix Proposal**: Code changes, risk, impact\n4. **Validation Plan**: Steps to verify fix\n5. **Prevention**: Tests, monitoring, documentation\n\nFocus on actionable insights. Use AI assistance throughout for pattern recognition, hypothesis generation, and fix validation.\n\n---\n\nIssue to debug: $ARGUMENTS\n","## Use this skill when\n\n- Working on error diagnostics smart debug tasks or workflows\n- Needing guidance, best practices, or checklists for error diagnostics smart debug\n\n## Do not use this skill when\n\n- The task is unrelated to error diagnostics smart debug\n- You need a different domain or tool outside this scope\n\n## Instructions\n\n- Clarify goals, constraints, and required inputs.\n- Apply relevant best practices and validate outcomes.\n- Provide actionable steps and verification.\n- If detailed examples are required, open `resources\u002Fimplementation-playbook.md`.\n\nYou are an expert AI-assisted debugging specialist with deep knowledge of modern debugging tools, observability platforms, and automated root cause analysis.\n\n## Context\n\nProcess issue from: $ARGUMENTS\n\nParse for:\n- Error messages\u002Fstack traces\n- Reproduction steps\n- Affected components\u002Fservices\n- Performance characteristics\n- Environment (dev\u002Fstaging\u002Fproduction)\n- Failure patterns (intermittent\u002Fconsistent)\n\n## Workflow\n\n### 1. Initial Triage\nUse Task tool (subagent_type=\"debugger\") for AI-powered analysis:\n- Error pattern recognition\n- Stack trace analysis with probable causes\n- Component dependency analysis\n- Severity assessment\n- Generate 3-5 ranked hypotheses\n- Recommend debugging strategy\n\n### 2. Observability Data Collection\nFor production\u002Fstaging issues, gather:\n- Error tracking (Sentry, Rollbar, Bugsnag)\n- APM metrics (DataDog, New Relic, Dynatrace)\n- Distributed traces (Jaeger, Zipkin, Honeycomb)\n- Log aggregation (ELK, Splunk, Loki)\n- Session replays (LogRocket, FullStory)\n\nQuery for:\n- Error frequency\u002Ftrends\n- Affected user cohorts\n- Environment-specific patterns\n- Related errors\u002Fwarnings\n- Performance degradation correlation\n- Deployment timeline correlation\n\n### 3. Hypothesis Generation\nFor each hypothesis include:\n- Probability score (0-100%)\n- Supporting evidence from logs\u002Ftraces\u002Fcode\n- Falsification criteria\n- Testing approach\n- Expected symptoms if true\n\nCommon categories:\n- Logic errors (race conditions, null handling)\n- State management (stale cache, incorrect transitions)\n- Integration failures (API changes, timeouts, auth)\n- Resource exhaustion (memory leaks, connection pools)\n- Configuration drift (env vars, feature flags)\n- Data corruption (schema mismatches, encoding)\n\n### 4. Strategy Selection\nSelect based on issue characteristics:\n\n**Interactive Debugging**: Reproducible locally → VS Code\u002FChrome DevTools, step-through\n**Observability-Driven**: Production issues → Sentry\u002FDataDog\u002FHoneycomb, trace analysis\n**Time-Travel**: Complex state issues → rr\u002FRedux DevTools, record & replay\n**Chaos Engineering**: Intermittent under load → Chaos Monkey\u002FGremlin, inject failures\n**Statistical**: Small % of cases → Delta debugging, compare success vs failure\n\n### 5. Intelligent Instrumentation\nAI suggests optimal breakpoint\u002Flogpoint locations:\n- Entry points to affected functionality\n- Decision nodes where behavior diverges\n- State mutation points\n- External integration boundaries\n- Error handling paths\n\nUse conditional breakpoints and logpoints for production-like environments.\n\n### 6. Production-Safe Techniques\n**Dynamic Instrumentation**: OpenTelemetry spans, non-invasive attributes\n**Feature-Flagged Debug Logging**: Conditional logging for specific users\n**Sampling-Based Profiling**: Continuous profiling with minimal overhead (Pyroscope)\n**Read-Only Debug Endpoints**: Protected by auth, rate-limited state inspection\n**Gradual Traffic Shifting**: Canary deploy debug version to 10% traffic\n\n### 7. Root Cause Analysis\nAI-powered code flow analysis:\n- Full execution path reconstruction\n- Variable state tracking at decision points\n- External dependency interaction analysis\n- Timing\u002Fsequence diagram generation\n- Code smell detection\n- Similar bug pattern identification\n- Fix complexity estimation\n\n### 8. Fix Implementation\nAI generates fix with:\n- Code changes required\n- Impact assessment\n- Risk level\n- Test coverage needs\n- Rollback strategy\n\n### 9. Validation\nPost-fix verification:\n- Run test suite\n- Performance comparison (baseline vs fix)\n- Canary deployment (monitor error rate)\n- AI code review of fix\n\nSuccess criteria:\n- Tests pass\n- No performance regression\n- Error rate unchanged or decreased\n- No new edge cases introduced\n\n### 10. Prevention\n- Generate regression tests using AI\n- Update knowledge base with root cause\n- Add monitoring\u002Falerts for similar issues\n- Document troubleshooting steps in runbook\n\n## Example: Minimal Debug Session\n\n```typescript\n\u002F\u002F Issue: \"Checkout timeout errors (intermittent)\"\n\n\u002F\u002F 1. Initial analysis\nconst analysis = await aiAnalyze({\n  error: \"Payment processing timeout\",\n  frequency: \"5% of checkouts\",\n  environment: \"production\"\n});\n\u002F\u002F AI suggests: \"Likely N+1 query or external API timeout\"\n\n\u002F\u002F 2. Gather observability data\nconst sentryData = await getSentryIssue(\"CHECKOUT_TIMEOUT\");\nconst ddTraces = await getDataDogTraces({\n  service: \"checkout\",\n  operation: \"process_payment\",\n  duration: \">5000ms\"\n});\n\n\u002F\u002F 3. Analyze traces\n\u002F\u002F AI identifies: 15+ sequential DB queries per checkout\n\u002F\u002F Hypothesis: N+1 query in payment method loading\n\n\u002F\u002F 4. Add instrumentation\nspan.setAttribute('debug.queryCount', queryCount);\nspan.setAttribute('debug.paymentMethodId', methodId);\n\n\u002F\u002F 5. Deploy to 10% traffic, monitor\n\u002F\u002F Confirmed: N+1 pattern in payment verification\n\n\u002F\u002F 6. AI generates fix\n\u002F\u002F Replace sequential queries with batch query\n\n\u002F\u002F 7. Validate\n\u002F\u002F - Tests pass\n\u002F\u002F - Latency reduced 70%\n\u002F\u002F - Query count: 15 → 1\n```\n\n## Output Format\n\nProvide structured report:\n1. **Issue Summary**: Error, frequency, impact\n2. **Root Cause**: Detailed diagnosis with evidence\n3. **Fix Proposal**: Code changes, risk, impact\n4. **Validation Plan**: Steps to verify fix\n5. **Prevention**: Tests, monitoring, documentation\n\nFocus on actionable insights. Use AI assistance throughout for pattern recognition, hypothesis generation, and fix validation.\n\n---\n\nIssue to debug: $ARGUMENTS\n",{"name":5,"description":7},"main","def8531e65114c0fca8fb8551c1871ee0eed705c","skills\u002Faiskillstore\u002Fmarketplace\u002Fsickn33\u002Ferror-diagnostics-smart-debug",24,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub","https:\u002F\u002Fskillshub.wtf","https:\u002F\u002Fgithub.com\u002FComeOnOliver","AI & Blockchain Engineer\r\n","2026-06-24 22:07:19",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add ComeOnOliver\u002Fskillshub --skill error-diagnostics-smart-debug",{"tool":55,"command":56},"bunx","bunx skills add ComeOnOliver\u002Fskillshub --skill error-diagnostics-smart-debug",{"tool":58,"command":59},"pnpm","pnpm dlx skills add ComeOnOliver\u002Fskillshub --skill error-diagnostics-smart-debug","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fsickn33\u002Ferror-diagnostics-smart-debug\u002FSKILL.md",true,[63],{"path":64,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":67,"sourceHtmlUrl":68},"skill-report.json","REFERENCE","参考文档",11373,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fsickn33\u002Ferror-diagnostics-smart-debug\u002Fskill-report.json",[70,80,90,99,105,112],{"skillNo":71,"name":72,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":76,"publishedAt":35},"01M6FKJN13GMG4KY57J3QD8GY5","model-hierarchy-skill","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzscole\u002Fmodel-hierarchy-skill\u002Fmodel-hierarchy-skill\u002FSKILL.md",[75],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[77,78,79],"model","model hierarchy","model hierarchy skill",{"skillNo":81,"name":82,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":86,"publishedAt":35},"01M6FKJJJ6GCAMR4PPPRD12M5X","zoom-mcp","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fzoom-mcp\u002FSKILL.md",[85],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[87,88,89],"MCP","zoom","zoom mcp",{"skillNo":91,"name":92,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":35},"01M6FKJE3KYT3KPEZMEEHYKA6K","zoom-apps-sdk","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fzoom-apps-sdk\u002FSKILL.md",[],[96,97,98,88],"sdk","zoom apps sdk","apps",{"skillNo":100,"name":101,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":35},"01M6FKJ9EDH9Q5VWDF8HAJRSP0","windows","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwindows\u002FSKILL.md",[],[101],{"skillNo":106,"name":107,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":111,"publishedAt":35},"01M6FKJ666BEEFC3AE9GJ72Q93","whiteboard","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwhiteboard\u002FSKILL.md",[110],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[107],{"skillNo":113,"name":114,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":35},"01M6FKJ21WFCDGTJQ2Q91T9DVW","websockets","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwebsockets\u002FSKILL.md",[],[114]]