[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72SQJXXWPJZJSFV7PJMCF0G":3,"skill-same:01M72SQJXXWPJZJSFV7PJMCF0G":66},{"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":45,"commitSha":46,"skillDirectory":47,"forksCount":14,"repositoryHtmlUrl":48,"repositoryHomepageUrl":48,"ownerHtmlUrl":49,"ownerBlogUrl":6,"ownerDescription":50,"updatedAt":51,"install":52,"resources":65},"01M72SQJXXWPJZJSFV7PJMCF0G","bug-triage",null,"Use when diagnosing a bug in code. Five steps: understand the symptom, form hypotheses, test each with the smallest experiment, isolate the root cause, then fix with a regression test. For issue-tracker states and roles, use issue-triage.","iberi22\u002Fskills","iberi22","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F10615454?v=4","01M72SQ2NXAA3GW0FSH053A5ES","Brahyan Belalcazar","01M72SQ2PYCH0SSA1K61NGEHDV",0,"MIT","https:\u002F\u002Fgithub.com\u002Fiberi22\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdebugging\u002Fbug-triage\u002FSKILL.md",[],[],"2026-11-10 22:39:42",false,"---\nname: bug-triage\nslug: bug-triage\nversion: 1.0.0\ndescription: 'Use when diagnosing a bug in code. Five steps: understand the symptom, form hypotheses, test each with the smallest experiment, isolate the root cause, then fix with a regression test. For issue-tracker states and roles, use issue-triage.'\nlicense: MIT\noriginal_source: https:\u002F\u002Fgithub.com\u002Fmattpocock\u002Fskills\ncategory: debugging\ntags: [triage, debugging, bug, diagnosis, root-cause, workflow]\ngoals:\n  - Diagnose bugs systematically, not at random\n  - Shorten the time from symptom to root cause\n  - Test hypotheses with the smallest possible experiment\n  - Document findings to avoid similar bugs\ncontext:\n  when: A bug, error, or unexpected behavior is reported\n  who: Any coding agent\n  prerequisites: Access to the code and system logs\nauthors:\n  - mattpocock (original repo)\n  - Brahyan Belalcazar (structured version)\n---\n\n# Bug triage — bug diagnosis workflow\n\nThis skill sets a systematic 5-step process for diagnosing bugs without changing code at random. Each step produces information that feeds the next.\n\n## Principles\n\n1. **Do not touch code without a hypothesis.** If you do not know what you are testing, you are guessing.\n2. **The smallest experiment wins.** Narrow the scope until the answer is yes or no.\n3. **Reproduce before diagnosing.** If you cannot reproduce it, you cannot confirm the fix.\n4. **Document at each step.** A bug unresolved today is useful information tomorrow.\n\n---\n\n## Step 1: Understand the symptom\n\nBefore touching code, characterize the problem:\n\n- What is expected vs. what happens?\n- Is it consistent or intermittent?\n- Which environment? (local, staging, production)\n- When did it start? What changed just before?\n- Are there stack traces, logs, or error messages?\n\n**Deliverable:** A 2–3 line paragraph describing the symptom without naming causes.\n\n---\n\n## Step 2: Form hypotheses\n\nGenerate 2–4 plausible explanations, ordered by likelihood. Use your knowledge of the system, not vague intuitions.\n\nFormat of each hypothesis:\n\n```\nH1: \u003Cwhat is failing> → \u003Cwhy you think so> → \u003Cwhich experiment confirms or rejects it>\n```\n\nExample:\n\n```\nH1: The auth service returns 401 because the token expires earlier than expected.\n    → The bug occurs only after 15 min of inactivity.\n    → Experiment: log the token TTL at the moment of the 401.\n```\n\n---\n\n## Step 3: Test with the smallest possible experiment\n\nFor each hypothesis, design an experiment that is:\n\n- **Fast:** under 10 minutes of setup.\n- **Isolated:** does not depend on other systems where possible.\n- **Binary:** produces a result that confirms or rejects the hypothesis.\n\nUseful techniques:\n\n| Technique | When to use it |\n|---|---|\n| **Log points** | You need variable values at runtime without stopping the flow. |\n| **Binary search in git** | The bug appeared in some recent commit. Use `git bisect`. |\n| **Minimal reproduction** | Remove dependencies, code, and data until the bug still occurs in the smallest possible setup. |\n| **Temporary monkey-patch** | Force a value or bypass to confirm whether a dependency is the culprit. |\n| **State diff** | Compare system state (DB, cache, config) between a working and a failing environment. |\n\n**Rule:** If an experiment does not halve the search space, it is too big.\n\n---\n\n## Step 4: Isolate the root cause\n\nWhen a hypothesis is confirmed, keep digging until you find the root cause, not just the symptom.\n\nGuiding questions:\n\n- Is it a bug in my code or in a dependency?\n- Is it a logic, configuration, or data error?\n- Why does this input produce this output? Follow the data flow.\n- Is an invariant being broken? Where should it have been validated?\n\n**Deliverable:** One sentence explaining the root cause, linking the defect to the observable effect.\n\n---\n\n## Step 5: Fix + regression test\n\n1. **Fix the minimum necessary.** A large fix is suspicious.\n2. **Verify the fix works.** Reproduce the bug with the Step 1 steps; it must disappear.\n3. **Add a regression test.** If possible, write a test that fails before the fix and passes after.\n4. **Document briefly.** Note in the commit or a doc why it happened and how to avoid it.\n\n---\n\n## Anti-patterns to avoid\n\n- **Changing code and seeing what happens.** This destroys information.\n- **Debugging without reproducing first.** You lose confirmation of success.\n- **Assuming the bug is \"obvious\".** The root cause is usually 2–3 levels below the symptom.\n- **Jumping to a fix without a confirmed hypothesis.** You fix the symptom, not the bug.\n\n---\n\n## Quick checklist\n\n- [ ] Symptom clearly described\n- [ ] Hypotheses written and ordered\n- [ ] Minimal experiment run\n- [ ] Root cause identified\n- [ ] Fix applied and verified\n- [ ] Regression test added\n- [ ] Findings documented\n","# Bug triage — bug diagnosis workflow\n\nThis skill sets a systematic 5-step process for diagnosing bugs without changing code at random. Each step produces information that feeds the next.\n\n## Principles\n\n1. **Do not touch code without a hypothesis.** If you do not know what you are testing, you are guessing.\n2. **The smallest experiment wins.** Narrow the scope until the answer is yes or no.\n3. **Reproduce before diagnosing.** If you cannot reproduce it, you cannot confirm the fix.\n4. **Document at each step.** A bug unresolved today is useful information tomorrow.\n\n---\n\n## Step 1: Understand the symptom\n\nBefore touching code, characterize the problem:\n\n- What is expected vs. what happens?\n- Is it consistent or intermittent?\n- Which environment? (local, staging, production)\n- When did it start? What changed just before?\n- Are there stack traces, logs, or error messages?\n\n**Deliverable:** A 2–3 line paragraph describing the symptom without naming causes.\n\n---\n\n## Step 2: Form hypotheses\n\nGenerate 2–4 plausible explanations, ordered by likelihood. Use your knowledge of the system, not vague intuitions.\n\nFormat of each hypothesis:\n\n```\nH1: \u003Cwhat is failing> → \u003Cwhy you think so> → \u003Cwhich experiment confirms or rejects it>\n```\n\nExample:\n\n```\nH1: The auth service returns 401 because the token expires earlier than expected.\n    → The bug occurs only after 15 min of inactivity.\n    → Experiment: log the token TTL at the moment of the 401.\n```\n\n---\n\n## Step 3: Test with the smallest possible experiment\n\nFor each hypothesis, design an experiment that is:\n\n- **Fast:** under 10 minutes of setup.\n- **Isolated:** does not depend on other systems where possible.\n- **Binary:** produces a result that confirms or rejects the hypothesis.\n\nUseful techniques:\n\n| Technique | When to use it |\n|---|---|\n| **Log points** | You need variable values at runtime without stopping the flow. |\n| **Binary search in git** | The bug appeared in some recent commit. Use `git bisect`. |\n| **Minimal reproduction** | Remove dependencies, code, and data until the bug still occurs in the smallest possible setup. |\n| **Temporary monkey-patch** | Force a value or bypass to confirm whether a dependency is the culprit. |\n| **State diff** | Compare system state (DB, cache, config) between a working and a failing environment. |\n\n**Rule:** If an experiment does not halve the search space, it is too big.\n\n---\n\n## Step 4: Isolate the root cause\n\nWhen a hypothesis is confirmed, keep digging until you find the root cause, not just the symptom.\n\nGuiding questions:\n\n- Is it a bug in my code or in a dependency?\n- Is it a logic, configuration, or data error?\n- Why does this input produce this output? Follow the data flow.\n- Is an invariant being broken? Where should it have been validated?\n\n**Deliverable:** One sentence explaining the root cause, linking the defect to the observable effect.\n\n---\n\n## Step 5: Fix + regression test\n\n1. **Fix the minimum necessary.** A large fix is suspicious.\n2. **Verify the fix works.** Reproduce the bug with the Step 1 steps; it must disappear.\n3. **Add a regression test.** If possible, write a test that fails before the fix and passes after.\n4. **Document briefly.** Note in the commit or a doc why it happened and how to avoid it.\n\n---\n\n## Anti-patterns to avoid\n\n- **Changing code and seeing what happens.** This destroys information.\n- **Debugging without reproducing first.** You lose confirmation of success.\n- **Assuming the bug is \"obvious\".** The root cause is usually 2–3 levels below the symptom.\n- **Jumping to a fix without a confirmed hypothesis.** You fix the symptom, not the bug.\n\n---\n\n## Quick checklist\n\n- [ ] Symptom clearly described\n- [ ] Hypotheses written and ordered\n- [ ] Minimal experiment run\n- [ ] Root cause identified\n- [ ] Fix applied and verified\n- [ ] Regression test added\n- [ ] Findings documented\n",{"name":5,"slug":5,"tags":24,"goals":31,"authors":36,"context":39,"license":15,"version":43,"category":26,"description":7,"original_source":44},[25,26,27,28,29,30],"triage","debugging","bug","diagnosis","root-cause","workflow",[32,33,34,35],"Diagnose bugs systematically, not at random","Shorten the time from symptom to root cause","Test hypotheses with the smallest possible experiment","Document findings to avoid similar bugs",[37,38],"mattpocock (original repo)","Brahyan Belalcazar (structured version)",{"who":40,"when":41,"prerequisites":42},"Any coding agent","A bug, error, or unexpected behavior is reported","Access to the code and system logs","1.0.0","https:\u002F\u002Fgithub.com\u002Fmattpocock\u002Fskills","main","688810f2886d212632acf81e532b24e483dd8b98","skills\u002Fdebugging\u002Fbug-triage","https:\u002F\u002Fgithub.com\u002Fiberi22\u002Fskills","https:\u002F\u002Fgithub.com\u002Fiberi22","Senior WEB Full-Stack","2026-10-12 02:46:21",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add iberi22\u002Fskills --skill bug-triage",{"tool":58,"command":59},"bunx","bunx skills add iberi22\u002Fskills --skill bug-triage",{"tool":61,"command":62},"pnpm","pnpm dlx skills add iberi22\u002Fskills --skill bug-triage","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fiberi22\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdebugging\u002Fbug-triage\u002FSKILL.md",true,[],[67,73,80,86,92,98],{"skillNo":68,"name":69,"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":70,"categories":71,"keywords":72,"publishedAt":19},"01M72TWQEQD46ZC9TRBAABF78P","web-design-guidelines","https:\u002F\u002Fgithub.com\u002Fiberi22\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fweb\u002Fweb-design-guidelines\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M72TWMQFTYD08DGXVAXRPPEB","blocked-page-recovery","Use when a fetch fails: 403\u002F429, paywall, WAF, bot wall. Recovers the page via archives and provenance-checked fallbacks.","https:\u002F\u002Fgithub.com\u002Fiberi22\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fweb\u002Fblocked-page-recovery\u002FSKILL.md",[],[],{"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":85,"publishedAt":19},"01M72TVQMS3HCTX18C8T97WTQQ","studio-coach","https:\u002F\u002Fgithub.com\u002Fiberi22\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Ftools\u002Fstudio-coach\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"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":89,"categories":90,"keywords":91,"publishedAt":19},"01M72TVNA2PR9RZW0ZAXYP1G6J","src-generator","https:\u002F\u002Fgithub.com\u002Fiberi22\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Ftools\u002Fsrc-generator\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"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":95,"categories":96,"keywords":97,"publishedAt":19},"01M72TVEJHHB6SAT3R3TY9MJKS","sqlite-pro","https:\u002F\u002Fgithub.com\u002Fiberi22\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Ftools\u002Fsqlite-pro\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"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":19},"01M72TVC2EVBHQHCX96VTTYKB8","rigor-evaluator","Use when you need a quick heuristic rigor score (10 criteria, 0-2 each) for the features in a .gitcore\u002Ffeatures.json file, to decide which features are ready to ship.","https:\u002F\u002Fgithub.com\u002Fiberi22\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Ftools\u002Frigor-evaluator\u002FSKILL.md",[],[]]