[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DEW5VBTPCPRHEASQJ28KHB":3,"skill-same:01M7DEW5VBTPCPRHEASQJ28KHB":55},{"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},"01M7DEW5VBTPCPRHEASQJ28KHB","bug-investigation",null,"Reproduce a reported defect, find its cause, implement a fix and verify the behavior. Use when the user reports something that should work but does not and expects a fix; use root-cause-analysis when they only want the cause.","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\u002Fcore\u002Fskills\u002Fdebugging\u002Fbug-investigation\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: bug-investigation\ndescription: >-\n  Reproduce a reported defect, find its cause, implement a fix and verify the behavior. Use when the user reports something that should work but does not and expects a fix; use root-cause-analysis when they only want the cause.\n---\n\n# Bug investigation\n\n## When to use\n\nIn the bug workflow, from `discovery` through `implementation`. For live production\nbehavior, start with `runtime-debugging`; for the reasoning that finds the cause, this\nskill hands off to `root-cause-analysis`.\n\n## Required context\n\nThe report itself: symptom, where it was seen, raw error output, reproduction steps if\nany. Useful: the feature map entry and the verification profile.\n\n## Preconditions\n\n- The expected behavior is stated by the report, the code's tests or a human. Without\n  it, the report is a requirements question, not a bug; ask.\n- The raw failure output is available, or a human was asked for it.\n\n## Procedure\n\n1. **Understand the symptom.** Separate what was observed from what the reporter\n   concluded. Note the environment, input and time.\n2. **Reproduce** in the smallest setting that shows the defect. If you cannot reproduce\n   it, record every attempt and ask for more data before touching code. When the defect\n   appears only in a running environment, use `runtime-debugging` to observe it there.\n3. **Isolate.** Narrow the input and the code path until the defect's location is small.\n   When the defect is a regression, compare against the last good revision with\n   `core.repository.diff`, and use `core.repository.history` to find the changes in between.\n4. **Find the cause** with `root-cause-analysis`. Do not write a fix before the cause is\n   confirmed.\n5. **Write the regression test** with `regression-testing`, and see it fail.\n6. **Fix** the cause, not the symptom, in the smallest change the cause allows.\n7. **Verify**: the regression test passes, the surrounding suite passes, and the original\n   reproduction no longer shows the defect.\n8. **Look sideways.** Search for the same cause elsewhere and list each occurrence as\n   fixed, ruled out or left for a human to decide.\n\nKeep a running log while investigating; the synthetic example in\n[examples\u002Finvestigation-log.md](examples\u002Finvestigation-log.md) shows the level of detail.\nFor a Paved workflow, keep durable investigation notes under\n`.paved\u002Fdocuments\u002Fresearch\u002F\u003Crun-id>.md` and the implementation plan under\n`.paved\u002Fdocuments\u002Fplans\u002F\u003Crun-id>.md`; use the same workflow run id for both.\n\n## Tools\n\n`core.repository.diff` to compare with a known-good revision; `core.repository.history`, when available, to\nlist the changes between that revision and the failing one.\n\n## Rules\n\n`core.testing.regression-test-for-bug-fix` makes step 5 non-negotiable, and\n`core.quality.unknowns-stay-unknown` applies to the report: a reporter's explanation is a\nhypothesis until the code confirms it.\n\n## Verification\n\nRequired: `unit`. Recommended: `integration` or `e2e` when the defect lives at that\nlevel, and `runtime` when it was observed in a running system.\n\n## Evidence\n\nThe reproduction, check results for the regression test before and after the fix and for\nthe surrounding suite, and the diff.\n\n## Completion criteria\n\n- The regression test failed before the fix and passes after it.\n- The original reproduction no longer shows the defect.\n- The cause is explained in the evidence, with the observation that confirmed it.\n\n## Failure modes\n\n| Failure | Signal | Response |\n|---|---|---|\n| Cannot reproduce | Several attempts show no defect | Record the attempts; ask for data; do not guess a fix |\n| Fix before cause | A change is proposed with no confirmed cause | Return to step 4 |\n| Intermittent defect | Reproduction fails only sometimes | Treat timing, ordering and shared state as suspects; measure the rate |\n| Symptom masked | The error disappears but the state is still wrong | Keep tracing; assert on the state, not on the error |\n\n## References\n\n- [examples\u002Finvestigation-log.md](examples\u002Finvestigation-log.md): a synthetic\n  investigation log.\n","# Bug investigation\n\n## When to use\n\nIn the bug workflow, from `discovery` through `implementation`. For live production\nbehavior, start with `runtime-debugging`; for the reasoning that finds the cause, this\nskill hands off to `root-cause-analysis`.\n\n## Required context\n\nThe report itself: symptom, where it was seen, raw error output, reproduction steps if\nany. Useful: the feature map entry and the verification profile.\n\n## Preconditions\n\n- The expected behavior is stated by the report, the code's tests or a human. Without\n  it, the report is a requirements question, not a bug; ask.\n- The raw failure output is available, or a human was asked for it.\n\n## Procedure\n\n1. **Understand the symptom.** Separate what was observed from what the reporter\n   concluded. Note the environment, input and time.\n2. **Reproduce** in the smallest setting that shows the defect. If you cannot reproduce\n   it, record every attempt and ask for more data before touching code. When the defect\n   appears only in a running environment, use `runtime-debugging` to observe it there.\n3. **Isolate.** Narrow the input and the code path until the defect's location is small.\n   When the defect is a regression, compare against the last good revision with\n   `core.repository.diff`, and use `core.repository.history` to find the changes in between.\n4. **Find the cause** with `root-cause-analysis`. Do not write a fix before the cause is\n   confirmed.\n5. **Write the regression test** with `regression-testing`, and see it fail.\n6. **Fix** the cause, not the symptom, in the smallest change the cause allows.\n7. **Verify**: the regression test passes, the surrounding suite passes, and the original\n   reproduction no longer shows the defect.\n8. **Look sideways.** Search for the same cause elsewhere and list each occurrence as\n   fixed, ruled out or left for a human to decide.\n\nKeep a running log while investigating; the synthetic example in\n[examples\u002Finvestigation-log.md](examples\u002Finvestigation-log.md) shows the level of detail.\nFor a Paved workflow, keep durable investigation notes under\n`.paved\u002Fdocuments\u002Fresearch\u002F\u003Crun-id>.md` and the implementation plan under\n`.paved\u002Fdocuments\u002Fplans\u002F\u003Crun-id>.md`; use the same workflow run id for both.\n\n## Tools\n\n`core.repository.diff` to compare with a known-good revision; `core.repository.history`, when available, to\nlist the changes between that revision and the failing one.\n\n## Rules\n\n`core.testing.regression-test-for-bug-fix` makes step 5 non-negotiable, and\n`core.quality.unknowns-stay-unknown` applies to the report: a reporter's explanation is a\nhypothesis until the code confirms it.\n\n## Verification\n\nRequired: `unit`. Recommended: `integration` or `e2e` when the defect lives at that\nlevel, and `runtime` when it was observed in a running system.\n\n## Evidence\n\nThe reproduction, check results for the regression test before and after the fix and for\nthe surrounding suite, and the diff.\n\n## Completion criteria\n\n- The regression test failed before the fix and passes after it.\n- The original reproduction no longer shows the defect.\n- The cause is explained in the evidence, with the observation that confirmed it.\n\n## Failure modes\n\n| Failure | Signal | Response |\n|---|---|---|\n| Cannot reproduce | Several attempts show no defect | Record the attempts; ask for data; do not guess a fix |\n| Fix before cause | A change is proposed with no confirmed cause | Return to step 4 |\n| Intermittent defect | Reproduction fails only sometimes | Treat timing, ordering and shared state as suspects; measure the rate |\n| Symptom masked | The error disappears but the state is still wrong | Keep tracing; assert on the state, not on the error |\n\n## References\n\n- [examples\u002Finvestigation-log.md](examples\u002Finvestigation-log.md): a synthetic\n  investigation log.\n",{"name":5,"description":7},"main","1cd80f05aff924ea609012e864fa5c22c16c7d2d","core\u002Fskills\u002Fdebugging\u002Fbug-investigation",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 bug-investigation",{"tool":37,"command":38},"bunx","bunx skills add andersonmrodrigues\u002Fpaved --skill bug-investigation",{"tool":40,"command":41},"pnpm","pnpm dlx skills add andersonmrodrigues\u002Fpaved --skill bug-investigation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdebugging\u002Fbug-investigation\u002FSKILL.md",true,[45,51],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"examples\u002Finvestigation-log.md","REFERENCE","参考文档",1227,"https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdebugging\u002Fbug-investigation\u002Fexamples\u002Finvestigation-log.md",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"skill.yaml",679,"https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdebugging\u002Fbug-investigation\u002Fskill.yaml",[56,63,69,75,81,87],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"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":64,"name":65,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7DFBS6WTK30PBSW4ZS0NPWT","unexplained-contract","https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Finvalid\u002Funexplained-contract\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7DFBPJGG170V9WTMFWY73R4","shell-block","https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Finvalid\u002Fshell-block\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7DFBMZYR20JPTXNE5A8EFG6","project-identifier","https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Finvalid\u002Fproject-identifier\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7DFBJ8J533DAKA3FTF54SX3","oversized","https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Finvalid\u002Foversized\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"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",[],[]]