[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M751PSEHSCNDRF7MVFVNE5JQ":3,"skill-same:01M751PSEHSCNDRF7MVFVNE5JQ":56},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":28,"commitSha":29,"skillDirectory":30,"forksCount":31,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":34,"ownerDescription":35,"updatedAt":36,"install":37,"resources":49},"01M751PSEHSCNDRF7MVFVNE5JQ","x-troubleshoot-operations",null,"Diagnoses errors, stacktraces, build failures, and unexpected behavior. Systematic approach: reproduce, locate, understand, fix, verify. Use whenever something fails: compilation errors, test failures, runtime exceptions, coverage gaps, or performance issues.","review-bench\u002Federcnj_ia-dev-environment","review-bench","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F286778065?v=4","01M7517F9NTEPDZDAXJBR30FWT","ReviewBench","01M7517FAC9F4P7TGWCNJ8VYVW",0,"MIT","https:\u002F\u002Fgithub.com\u002Freview-bench\u002Federcnj_ia-dev-environment\u002Fblob\u002Fmain\u002Fsrc\u002Fmain\u002Fresources\u002Ftargets\u002Fclaude\u002Fskills\u002Fcore\u002Fops\u002Fx-troubleshoot-operations\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: x-troubleshoot-operations\ndescription: \"Diagnoses errors, stacktraces, build failures, and unexpected behavior. Systematic approach: reproduce, locate, understand, fix, verify. Use whenever something fails: compilation errors, test failures, runtime exceptions, coverage gaps, or performance issues.\"\nuser-invocable: true\nallowed-tools: Read, Bash, Grep, Glob\nargument-hint: \"[error-description or test-name]\"\nrequires-capabilities: []\n---\n\n## Global Output Policy\n\n- **Language**: English ONLY.\n- **Tone**: Technical, Direct, and Concise.\n- **Efficiency**: Remove all conversational fillers and greetings to save tokens.\n\n# Skill: Troubleshoot\n\n## Purpose\n\nProvides a systematic approach to diagnose and fix issues in {{PROJECT_NAME}}. Covers compilation errors, test failures, build failures, runtime exceptions, and domain-specific bugs.\n\n## Triggers\n\n- `\u002Fx-troubleshoot-operations` — diagnose issues using the full debug workflow\n- `\u002Fx-troubleshoot-operations \"NullPointerException in PaymentService\"` — diagnose a specific error\n- `\u002Fx-troubleshoot-operations testMethodName` — diagnose a specific test failure\n\n## Workflow\n\n```\n1. REPRODUCE  -> Get the exact error (stacktrace, build log, test output)\n2. LOCATE     -> Find where the error originates\n3. UNDERSTAND -> Why is it failing? Expected vs actual behavior?\n4. FIX        -> Write a test that reproduces the bug, then fix the code\n5. VERIFY     -> Run the full test suite to ensure no regressions\n```\n\nAlways follow this order. Never skip step 4's \"write a test first\" — the bug-reproducing test prevents regressions.\n\n### Step 1 — Reproduce\n\nGet the exact error output. Run the relevant command and capture the full stacktrace, build log, or test output.\n\n```bash\n{{COMPILE_COMMAND}}\n```\n\n### Step 2 — Locate\n\nFind where the error originates using the error patterns below.\n\n#### 2.1 — Compilation Errors\n\nThe error patterns below are {{LANGUAGE}}-specific. Adapt to the actual compiler\u002Finterpreter messages for the project:\n\n| Error Category | Likely Cause | Fix |\n|----------------|--------------|-----|\n| Missing symbol\u002Ftype | Missing import, typo in class name | Check package structure, verify imports |\n| Type mismatch | Wrong type in assignment\u002Freturn | Check type inference, explicit cast if needed |\n| Sealed type error | Missing permits\u002Fimplementations | Add implementing class to sealed hierarchy |\n| Missing package\u002Fmodule | Wrong package or missing dependency | Verify directory matches package, check deps |\n| Interface mismatch | Signature mismatch with interface | Compare method signature with interface def |\n\n#### 2.2 — Test Failures\n\n```bash\n{{TEST_COMMAND}}\n```\n\n| Failure Type | Diagnosis | Fix |\n|--------------|-----------|-----|\n| Assertion error (expected X got Y) | Logic bug in production code | Compare expected vs actual, trace the logic |\n| NullPointerException in test | Missing setup | Initialize all objects test needs |\n| Test passes alone, fails in suite | Shared mutable state | Ensure fresh objects per test |\n| Timeout in test | Async issue or infinite loop | Check for blocking calls, add timeouts |\n\n#### 2.3 — Build Failures\n\n```bash\n{{BUILD_COMMAND}}\n```\n\n| Error | Cause | Fix |\n|-------|-------|-----|\n| Coverage threshold failure | Coverage below threshold | Write more tests, check coverage report |\n| Dependency resolution failure | Missing or conflicting dep | Check build file, resolve conflicts |\n| Out of memory | Memory issue in test\u002Fbuild | Increase memory limits, check for leaks |\n\n#### 2.4 — Runtime Errors\n\nThe error patterns below are {{LANGUAGE}}-specific. Adapt to the actual runtime error messages for the project:\n\n| Error Category | Likely Cause | Fix |\n|----------------|--------------|-----|\n| Missing class\u002Fmodule at runtime | Missing dependency at runtime | Check classpath\u002Fmodule path, add dependency |\n| Method\u002Ffunction not found | Version mismatch | Align dependency versions |\n| Connection refused | Service not running | Start required services, check ports |\n| Circuit breaker open | Downstream service failure | Check downstream health, wait for recovery |\n\n#### 2.5 — Performance Issues\n\n| Symptom | Likely Cause | Fix |\n|---------|--------------|-----|\n| Slow response | N+1 queries, missing indexes | Add indexes, optimize queries |\n| Memory growing | Object leak, missing cleanup | Profile memory, fix resource management |\n| Thread starvation | Blocking on event loop | Use async patterns, offload to workers |\n\n### Step 3 — Understand\n\nAnalyze why the error occurs. Compare expected vs actual behavior. Trace the data flow from input to the failure point.\n\n### Step 4 — Fix (Test-First)\n\nFor every bug found:\n\n1. Write a test that reproduces the bug (it MUST FAIL)\n2. Fix the code\n3. Verify the test PASSES\n4. Run full test suite for regressions\n\n```\n\u002F\u002F This test was added for bug #NNN\n\u002F\u002F Previously [describe the bug]\n```\n\n### Step 5 — Verify\n\nRun the full test suite. Confirm zero regressions. Check coverage thresholds.\n\n## Quick Diagnosis Checklist\n\nWhen something fails, check in this order:\n\n1. **Compilation error?** — Read the error message carefully\n2. **Test failure?** — Read expected vs actual, run test in isolation\n3. **Coverage failure?** — Check coverage report, find uncovered branches\n4. **Dependency issue?** — Check build file, verify versions\n5. **Configuration issue?** — Check properties, environment variables\n6. **Intermittent?** — Suspect shared mutable state, race conditions\n\n## Error Classification for Group Verifier\n\nWhen troubleshooting within the feature lifecycle, classify errors for `x-lib-verify-group`:\n\n| Classification | When | Action |\n|----------------|------|--------|\n| TASK_ERROR | Error in current group's code | Retry same tier |\n| MISSING_DEPENDENCY | Missing type from previous group | Halt, flag regression |\n| BUILD_ERROR | Missing external dependency | Halt, fix build file |\n| UNKNOWN | Unrecognized error pattern | Escalate tier |\n\n## Error Handling\n\n| Scenario | Action |\n|----------|--------|\n| Stacktrace not available | Request the user to provide the full error output |\n| Error in third-party library | Verify dependency versions, check for known issues upstream |\n| Non-reproducible failure | Investigate shared mutable state, race conditions, or environment differences |\n| Fix introduces new failures | Revert the fix, re-analyze root cause with broader context |\n\n## Integration Notes\n\n| Skill | Relationship | Context |\n|-------|-------------|---------|\n| x-lib-verify-group | Referenced by | Invokes troubleshoot when compilation fails during group verification |\n| x-implement-story | Referenced by | Used during Phase 4 (fixes) for diagnosing test and build failures |\n| x-execute-tests | Complements | Troubleshoot diagnoses failures that x-execute-tests reports |\n","## Global Output Policy\n\n- **Language**: English ONLY.\n- **Tone**: Technical, Direct, and Concise.\n- **Efficiency**: Remove all conversational fillers and greetings to save tokens.\n\n# Skill: Troubleshoot\n\n## Purpose\n\nProvides a systematic approach to diagnose and fix issues in {{PROJECT_NAME}}. Covers compilation errors, test failures, build failures, runtime exceptions, and domain-specific bugs.\n\n## Triggers\n\n- `\u002Fx-troubleshoot-operations` — diagnose issues using the full debug workflow\n- `\u002Fx-troubleshoot-operations \"NullPointerException in PaymentService\"` — diagnose a specific error\n- `\u002Fx-troubleshoot-operations testMethodName` — diagnose a specific test failure\n\n## Workflow\n\n```\n1. REPRODUCE  -> Get the exact error (stacktrace, build log, test output)\n2. LOCATE     -> Find where the error originates\n3. UNDERSTAND -> Why is it failing? Expected vs actual behavior?\n4. FIX        -> Write a test that reproduces the bug, then fix the code\n5. VERIFY     -> Run the full test suite to ensure no regressions\n```\n\nAlways follow this order. Never skip step 4's \"write a test first\" — the bug-reproducing test prevents regressions.\n\n### Step 1 — Reproduce\n\nGet the exact error output. Run the relevant command and capture the full stacktrace, build log, or test output.\n\n```bash\n{{COMPILE_COMMAND}}\n```\n\n### Step 2 — Locate\n\nFind where the error originates using the error patterns below.\n\n#### 2.1 — Compilation Errors\n\nThe error patterns below are {{LANGUAGE}}-specific. Adapt to the actual compiler\u002Finterpreter messages for the project:\n\n| Error Category | Likely Cause | Fix |\n|----------------|--------------|-----|\n| Missing symbol\u002Ftype | Missing import, typo in class name | Check package structure, verify imports |\n| Type mismatch | Wrong type in assignment\u002Freturn | Check type inference, explicit cast if needed |\n| Sealed type error | Missing permits\u002Fimplementations | Add implementing class to sealed hierarchy |\n| Missing package\u002Fmodule | Wrong package or missing dependency | Verify directory matches package, check deps |\n| Interface mismatch | Signature mismatch with interface | Compare method signature with interface def |\n\n#### 2.2 — Test Failures\n\n```bash\n{{TEST_COMMAND}}\n```\n\n| Failure Type | Diagnosis | Fix |\n|--------------|-----------|-----|\n| Assertion error (expected X got Y) | Logic bug in production code | Compare expected vs actual, trace the logic |\n| NullPointerException in test | Missing setup | Initialize all objects test needs |\n| Test passes alone, fails in suite | Shared mutable state | Ensure fresh objects per test |\n| Timeout in test | Async issue or infinite loop | Check for blocking calls, add timeouts |\n\n#### 2.3 — Build Failures\n\n```bash\n{{BUILD_COMMAND}}\n```\n\n| Error | Cause | Fix |\n|-------|-------|-----|\n| Coverage threshold failure | Coverage below threshold | Write more tests, check coverage report |\n| Dependency resolution failure | Missing or conflicting dep | Check build file, resolve conflicts |\n| Out of memory | Memory issue in test\u002Fbuild | Increase memory limits, check for leaks |\n\n#### 2.4 — Runtime Errors\n\nThe error patterns below are {{LANGUAGE}}-specific. Adapt to the actual runtime error messages for the project:\n\n| Error Category | Likely Cause | Fix |\n|----------------|--------------|-----|\n| Missing class\u002Fmodule at runtime | Missing dependency at runtime | Check classpath\u002Fmodule path, add dependency |\n| Method\u002Ffunction not found | Version mismatch | Align dependency versions |\n| Connection refused | Service not running | Start required services, check ports |\n| Circuit breaker open | Downstream service failure | Check downstream health, wait for recovery |\n\n#### 2.5 — Performance Issues\n\n| Symptom | Likely Cause | Fix |\n|---------|--------------|-----|\n| Slow response | N+1 queries, missing indexes | Add indexes, optimize queries |\n| Memory growing | Object leak, missing cleanup | Profile memory, fix resource management |\n| Thread starvation | Blocking on event loop | Use async patterns, offload to workers |\n\n### Step 3 — Understand\n\nAnalyze why the error occurs. Compare expected vs actual behavior. Trace the data flow from input to the failure point.\n\n### Step 4 — Fix (Test-First)\n\nFor every bug found:\n\n1. Write a test that reproduces the bug (it MUST FAIL)\n2. Fix the code\n3. Verify the test PASSES\n4. Run full test suite for regressions\n\n```\n\u002F\u002F This test was added for bug #NNN\n\u002F\u002F Previously [describe the bug]\n```\n\n### Step 5 — Verify\n\nRun the full test suite. Confirm zero regressions. Check coverage thresholds.\n\n## Quick Diagnosis Checklist\n\nWhen something fails, check in this order:\n\n1. **Compilation error?** — Read the error message carefully\n2. **Test failure?** — Read expected vs actual, run test in isolation\n3. **Coverage failure?** — Check coverage report, find uncovered branches\n4. **Dependency issue?** — Check build file, verify versions\n5. **Configuration issue?** — Check properties, environment variables\n6. **Intermittent?** — Suspect shared mutable state, race conditions\n\n## Error Classification for Group Verifier\n\nWhen troubleshooting within the feature lifecycle, classify errors for `x-lib-verify-group`:\n\n| Classification | When | Action |\n|----------------|------|--------|\n| TASK_ERROR | Error in current group's code | Retry same tier |\n| MISSING_DEPENDENCY | Missing type from previous group | Halt, flag regression |\n| BUILD_ERROR | Missing external dependency | Halt, fix build file |\n| UNKNOWN | Unrecognized error pattern | Escalate tier |\n\n## Error Handling\n\n| Scenario | Action |\n|----------|--------|\n| Stacktrace not available | Request the user to provide the full error output |\n| Error in third-party library | Verify dependency versions, check for known issues upstream |\n| Non-reproducible failure | Investigate shared mutable state, race conditions, or environment differences |\n| Fix introduces new failures | Revert the fix, re-analyze root cause with broader context |\n\n## Integration Notes\n\n| Skill | Relationship | Context |\n|-------|-------------|---------|\n| x-lib-verify-group | Referenced by | Invokes troubleshoot when compilation fails during group verification |\n| x-implement-story | Referenced by | Used during Phase 4 (fixes) for diagnosing test and build failures |\n| x-execute-tests | Complements | Troubleshoot diagnoses failures that x-execute-tests reports |\n",{"name":5,"description":7,"allowed-tools":24,"argument-hint":25,"user-invocable":26,"requires-capabilities":27},"Read, Bash, Grep, Glob","[error-description or test-name]",true,[],"main","952a630c6f38d193a349d86fa18db1de8843e837","src\u002Fmain\u002Fresources\u002Ftargets\u002Fclaude\u002Fskills\u002Fcore\u002Fops\u002Fx-troubleshoot-operations",1,"https:\u002F\u002Fgithub.com\u002Freview-bench\u002Federcnj_ia-dev-environment","https:\u002F\u002Fgithub.com\u002Freview-bench","https:\u002F\u002Freview-bench.ai","An open benchmark for AI code review.","2026-10-27 06:56:37",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":26},[39,42,45],{"tool":40,"command":41},"npx","npx skills add review-bench\u002Federcnj_ia-dev-environment --skill x-troubleshoot-operations",{"tool":43,"command":44},"bunx","bunx skills add review-bench\u002Federcnj_ia-dev-environment --skill x-troubleshoot-operations",{"tool":46,"command":47},"pnpm","pnpm dlx skills add review-bench\u002Federcnj_ia-dev-environment --skill x-troubleshoot-operations","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Freview-bench\u002Federcnj_ia-dev-environment\u002Fblob\u002Fmain\u002Fsrc\u002Fmain\u002Fresources\u002Ftargets\u002Fclaude\u002Fskills\u002Fcore\u002Fops\u002Fx-troubleshoot-operations\u002FSKILL.md",[50],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"README.md","REFERENCE","参考文档",1710,"https:\u002F\u002Fgithub.com\u002Freview-bench\u002Federcnj_ia-dev-environment\u002Fblob\u002Fmain\u002Fsrc\u002Fmain\u002Fresources\u002Ftargets\u002Fclaude\u002Fskills\u002Fcore\u002Fops\u002Fx-troubleshoot-operations\u002FREADME.md",[57,64,71,78,85,92],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M757M8J48TQ1Y3X25GSJBXAS","x-parallel-eval","Detects and classifies file-collision risks between work units (tasks, stories, or epic phases) before parallel execution. Reads ## File Footprint blocks produced by x-task-plan \u002F x-story-plan, applies the parallelism-heuristics knowledge pack (hard \u002F regen \u002F soft categories + hotspot overrides), and emits a collision matrix + serialization recommendation in Markdown (default) or JSON.","https:\u002F\u002Fgithub.com\u002Freview-bench\u002Federcnj_ia-dev-environment\u002Fblob\u002Fmain\u002Fsrc\u002Ftest\u002Fresources\u002Fgolden\u002Fx-parallel-eval\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M757M57XMR9546S69466HDWT","parallelism-heuristics","Canonical catalog of file-collision heuristics for parallel task, story, and epic execution. Defines the File Footprint block format, the three Conflict Categories (hard \u002F regen \u002F soft), a hotspot list of high-contention paths, and the degrade-with-warning policy. Consumed by x-task-plan, x-story-plan, x-epic-map, x-parallel-eval, and x-dev-*-implement.","https:\u002F\u002Fgithub.com\u002Freview-bench\u002Federcnj_ia-dev-environment\u002Fblob\u002Fmain\u002Fsrc\u002Ftest\u002Fresources\u002Fgolden\u002Fparallelism-heuristics\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M757M11SZ8P1VCQABT08QVYA","x-watch-pr-ci","Polls a PR's CI checks and Copilot review status, blocking until checks complete or timeout. Returns one of 8 stable exit codes (SUCCESS=0, CI_PENDING_PROCEED=10, CI_FAILED=20, TIMEOUT=30, PR_ALREADY_MERGED=40, NO_CI_CONFIGURED=50, PR_CLOSED=60, PR_NOT_FOUND=70). Writes a versioned state-file for session resume.","https:\u002F\u002Fgithub.com\u002Freview-bench\u002Federcnj_ia-dev-environment\u002Fblob\u002Fmain\u002Fsrc\u002Ftest\u002Fresources\u002Fgolden\u002Fjava-spring\u002Fplatform-claude-code\u002F.claude\u002Fskills\u002Fx-watch-pr-ci\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M757KW53K8KFPGADFB4PH949","x-validate-docs","Documentation freshness gate: validates 6 dimensions (readme, api-specs, grpc-proto, adr, skill-docs, system-architecture) against code changes in a PR. Stack-aware — only validates targets declared\u002Fauto-detected from ProjectConfig.documentation.targets. Returns exit non-zero on staleness; produces structured report.","https:\u002F\u002Fgithub.com\u002Freview-bench\u002Federcnj_ia-dev-environment\u002Fblob\u002Fmain\u002Fsrc\u002Ftest\u002Fresources\u002Fgolden\u002Fjava-spring\u002Fplatform-claude-code\u002F.claude\u002Fskills\u002Fx-validate-docs\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M757KQZHSA10MKC0CR571D60","x-update-system-architecture","Incrementally updates docs\u002Farchitecture\u002Fsystem.md after an epic completes. Appends new entries to the Decision Log (§11) using x-internal-write-report --append (dedup by ## ID: marker) and surgically inserts component\u002Fintegration changes into sections 1-10 via Edit. Idempotent: re-running with the same epic produces a byte-identical system.md.","https:\u002F\u002Fgithub.com\u002Freview-bench\u002Federcnj_ia-dev-environment\u002Fblob\u002Fmain\u002Fsrc\u002Ftest\u002Fresources\u002Fgolden\u002Fjava-spring\u002Fplatform-claude-code\u002F.claude\u002Fskills\u002Fx-update-system-architecture\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M757KKBT5Q1SVF8DMJBVF46M","x-update-architecture","Incrementally updates the service architecture document with changes from architecture plans. Adds new components, integrations, flows, and ADR references without rewriting existing content. Use after implementation to keep architecture documentation current.","https:\u002F\u002Fgithub.com\u002Freview-bench\u002Federcnj_ia-dev-environment\u002Fblob\u002Fmain\u002Fsrc\u002Ftest\u002Fresources\u002Fgolden\u002Fjava-spring\u002Fplatform-claude-code\u002F.claude\u002Fskills\u002Fx-update-architecture\u002FSKILL.md",[],[]]