[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DF53FYY7REKEEY0X7MVSEA":3,"skill-same:01M7DF53FYY7REKEEY0X7MVSEA":51},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7DF53FYY7REKEEY0X7MVSEA","root-cause-analysis",null,"Identify and confirm the cause of a defect from errors, logs, failing checks or reproduction evidence without implementing a fix. Use when the user asks why a failure happens or the cause is still uncertain; use bug-investigation when a verified fix is expected.","andersonmrodrigues\u002Fpaved","andersonmrodrigues","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F13907380?v=4","01M7DEV3FP2VMQZ3FP2FP1TK1C","Anderson Rodrigues","01M7DEV3GC2QAQBW4FMNT98H48",1,"MIT","https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved\u002Fblob\u002Fmain\u002Fplugins\u002Fpaved\u002Fruntime\u002Fpaved-core\u002Fcore\u002Fskills\u002Fdebugging\u002Froot-cause-analysis\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: root-cause-analysis\ndescription: >-\n  Identify and confirm the cause of a defect from errors, logs, failing checks or reproduction evidence without implementing a fix. Use when the user asks why a failure happens or the cause is still uncertain; use bug-investigation when a verified fix is expected.\n---\n\n# Root cause analysis\n\n## When to use\n\nWhenever something behaves differently from what is expected and the cause is not yet\nproven. Use it before writing a fix, not after the first fix fails. It is the reasoning\nstep inside `bug-investigation` and incident work.\n\n## Required context\n\nThe raw failure: error messages, stack traces, logs, the failing test output, or exact\nreproduction steps. If none is available, ask for it before theorizing.\n\n## Preconditions\n\nThe expected behavior is known. If it is ambiguous, confirm it with a human first;\notherwise the \"bug\" may be a requirements question.\n\n## Procedure\n\n1. **Reproduce.** Turn the report into the smallest reliable reproduction: ideally a\n   failing automated test, otherwise exact steps with observed output.\n2. **Read the evidence literally.** Start from the actual error and location, not from a\n   guess about what is probably wrong.\n3. **Trace backwards** from the symptom to the first point where state diverges from\n   expectation. Read the code on that path.\n4. **Form one hypothesis at a time** and test it with an observation (a log line, a\n   debugger, an assertion). Discard hypotheses the observation contradicts. When the\n   observation must come from a running system, use `runtime-debugging`.\n5. **Confirm the cause** by showing that changing only that cause changes the outcome.\n6. **Check whether the same cause** affects other places with the same pattern.\n7. Report the cause, the confirming observation and the reproduction. The fix and its\n   regression test belong to the calling skill.\n\n## Tools\n\n`core.repository.diff` against the last known-good revision when the defect is a regression;\n`core.repository.history`, when available, to narrow down which change introduced it.\n\n## Rules\n\n`core.quality.unknowns-stay-unknown`: say \"not yet known\" rather than presenting a\nhypothesis as the cause.\n\n## Verification\n\nRequired: `unit` — the reproduction as a failing test, where the cause allows it.\nRecommended: `integration` or `runtime` when the defect only appears there.\n\n## Evidence\n\nThe reproduction (test or steps) and the observations that confirmed the cause.\n\n## Completion criteria\n\n- A reliable reproduction exists.\n- The cause is explained in terms of the code, with the observation that confirms it.\n- Other occurrences of the same cause are listed or ruled out.\n\n## Failure modes\n\n| Failure | Signal | Response |\n|---|---|---|\n| Fixing the symptom | The explanation does not say why the state diverged | Keep tracing upstream |\n| Theory without data | Hypotheses are not tied to an observation | Collect raw output first |\n| Two failed fixes | A second fix attempt failed | Stop; re-read the code path top-down and restate the mental model |\n\n## References\n\nNone.\n","# Root cause analysis\n\n## When to use\n\nWhenever something behaves differently from what is expected and the cause is not yet\nproven. Use it before writing a fix, not after the first fix fails. It is the reasoning\nstep inside `bug-investigation` and incident work.\n\n## Required context\n\nThe raw failure: error messages, stack traces, logs, the failing test output, or exact\nreproduction steps. If none is available, ask for it before theorizing.\n\n## Preconditions\n\nThe expected behavior is known. If it is ambiguous, confirm it with a human first;\notherwise the \"bug\" may be a requirements question.\n\n## Procedure\n\n1. **Reproduce.** Turn the report into the smallest reliable reproduction: ideally a\n   failing automated test, otherwise exact steps with observed output.\n2. **Read the evidence literally.** Start from the actual error and location, not from a\n   guess about what is probably wrong.\n3. **Trace backwards** from the symptom to the first point where state diverges from\n   expectation. Read the code on that path.\n4. **Form one hypothesis at a time** and test it with an observation (a log line, a\n   debugger, an assertion). Discard hypotheses the observation contradicts. When the\n   observation must come from a running system, use `runtime-debugging`.\n5. **Confirm the cause** by showing that changing only that cause changes the outcome.\n6. **Check whether the same cause** affects other places with the same pattern.\n7. Report the cause, the confirming observation and the reproduction. The fix and its\n   regression test belong to the calling skill.\n\n## Tools\n\n`core.repository.diff` against the last known-good revision when the defect is a regression;\n`core.repository.history`, when available, to narrow down which change introduced it.\n\n## Rules\n\n`core.quality.unknowns-stay-unknown`: say \"not yet known\" rather than presenting a\nhypothesis as the cause.\n\n## Verification\n\nRequired: `unit` — the reproduction as a failing test, where the cause allows it.\nRecommended: `integration` or `runtime` when the defect only appears there.\n\n## Evidence\n\nThe reproduction (test or steps) and the observations that confirmed the cause.\n\n## Completion criteria\n\n- A reliable reproduction exists.\n- The cause is explained in terms of the code, with the observation that confirms it.\n- Other occurrences of the same cause are listed or ruled out.\n\n## Failure modes\n\n| Failure | Signal | Response |\n|---|---|---|\n| Fixing the symptom | The explanation does not say why the state diverged | Keep tracing upstream |\n| Theory without data | Hypotheses are not tied to an observation | Collect raw output first |\n| Two failed fixes | A second fix attempt failed | Stop; re-read the code path top-down and restate the mental model |\n\n## References\n\nNone.\n",{"name":5,"description":7},"main","1cd80f05aff924ea609012e864fa5c22c16c7d2d","plugins\u002Fpaved\u002Fruntime\u002Fpaved-core\u002Fcore\u002Fskills\u002Fdebugging\u002Froot-cause-analysis",0,"https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved","https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues","2026-11-14 20:09:28",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add andersonmrodrigues\u002Fpaved --skill root-cause-analysis",{"tool":37,"command":38},"bunx","bunx skills add andersonmrodrigues\u002Fpaved --skill root-cause-analysis",{"tool":40,"command":41},"pnpm","pnpm dlx skills add andersonmrodrigues\u002Fpaved --skill root-cause-analysis","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved\u002Fblob\u002Fmain\u002Fplugins\u002Fpaved\u002Fruntime\u002Fpaved-core\u002Fcore\u002Fskills\u002Fdebugging\u002Froot-cause-analysis\u002FSKILL.md",true,[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"skill.yaml","REFERENCE","参考文档",443,"https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved\u002Fblob\u002Fmain\u002Fplugins\u002Fpaved\u002Fruntime\u002Fpaved-core\u002Fcore\u002Fskills\u002Fdebugging\u002Froot-cause-analysis\u002Fskill.yaml",[52,59,65,71,77,83],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7DFBWJT4T1MPBHTWT19PBEK","sample-skill","Does a sample task. Use when a sample is needed.","https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Fvalid\u002Fsample-skill\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7DFBS6WTK30PBSW4ZS0NPWT","unexplained-contract","https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Finvalid\u002Funexplained-contract\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":55,"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},"01M7DFBPJGG170V9WTMFWY73R4","shell-block","https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Finvalid\u002Fshell-block\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7DFBMZYR20JPTXNE5A8EFG6","project-identifier","https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Finvalid\u002Fproject-identifier\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7DFBJ8J533DAKA3FTF54SX3","oversized","https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Finvalid\u002Foversized\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7DFBFAD0RYCRHTZ2JW4RX7E","no-activation","Does a sample task.","https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Finvalid\u002Fno-activation\u002FSKILL.md",[],[]]