[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EXG3YSZJ5BD1K801YVSWBR":3,"skill-same:01M7EXG3YSZJ5BD1K801YVSWBR":58},{"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":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":6,"ownerDescription":36,"updatedAt":37,"install":38,"resources":51},"01M7EXG3YSZJ5BD1K801YVSWBR","bug-hunt-swarm",null,"Parallel read-only multi-agent root-cause investigation for bugs, regressions, crashes, flaky behavior, or unexplained failures.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fbug-hunt-swarm\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: bug-hunt-swarm\ndescription: \"Parallel read-only multi-agent root-cause investigation for bugs, regressions, crashes, flaky behavior, or unexplained failures.\"\nrisk: safe\nsource: https:\u002F\u002Fgithub.com\u002FDimillian\u002FSkills\u002Ftree\u002Fmain\u002Fbug-hunt-swarm\nsource_repo: Dimillian\u002FSkills\nsource_type: community\ndate_added: 2026-07-01\nlicense: MIT\nlicense_source: https:\u002F\u002Fgithub.com\u002FDimillian\u002FSkills\u002Fblob\u002Fmain\u002FLICENSE\n---\n\n# Bug Hunt Swarm\n## When to Use\n\nUse this skill when you need parallel read-only multi-agent root-cause investigation for bugs, regressions, crashes, flaky behavior, or unexplained failures. Use when the user asks to investigate a bug, find the root cause, trace a regression, understand why something broke, or wants a ranked diagnosis with the...\n\n\nInvestigate a bug with four read-only sub-agents in parallel, then have the main agent rank the likely causes and recommend the fastest path to prove or fix the issue. This skill is diagnosis-first: do not edit files or implement fixes as part of this workflow.\n\n## Step 1: Build the Bug Packet\n\nStart by collecting the smallest useful investigation packet:\n\n1. Symptom\n2. Expected behavior\n3. Actual behavior\n4. Reproduction steps, if known\n5. Scope of impact\n6. Relevant evidence, such as logs, stack traces, failing tests, screenshots, recent diffs, or environment details\n\nPrefer this source order:\n\n1. Direct user description\n2. Explicit files, stack traces, logs, tests, or screenshots provided by the user\n3. Current git changes or recent repo history when the bug appears regression-like\n4. The smallest relevant code path or subsystem surrounding the failure\n\nIf the bug report is underspecified, infer a minimal problem statement and say what is still unknown.\n\nBefore launching sub-agents, read the closest project instructions and relevant docs for the touched area, such as:\n\n- `AGENTS.md`\n- repo workflow docs\n- architecture, state, routing, schema, or runtime docs for the affected subsystem\n\n## Step 2: Bound the Investigation\n\nWrite a short investigation brief for the swarm:\n\n1. What appears broken\n2. What is not yet proven\n3. What part of the system is most likely involved\n4. What evidence already exists\n5. What kind of proof would count as confirmation\n\nUse read-only evidence gathering where useful:\n\n- `rg`, `git diff`, `git log`, `git show`\n- reading logs, crash traces, and config\n- existing test runs or the smallest safe reproduction command\n\nDo not edit files, inject new instrumentation, or implement fixes as part of this skill.\n\n## Step 3: Launch Four Read-Only Investigators in Parallel\n\nLaunch four sub-agents when the problem is large or ambiguous enough that parallel investigation helps. For a tiny and obvious issue, it is acceptable to investigate locally instead.\n\nFor every sub-agent:\n\n- give the same bug packet and investigation brief\n- state that the sub-agent is read-only\n- do not let the sub-agent edit files, run `apply_patch`, stage changes, commit, or perform any other state-mutating action\n- ask for concise investigation output only\n- ask for: hypothesis, supporting evidence, missing evidence, smallest proof step, and confidence\n- tell the sub-agent to avoid generic code quality feedback, nits, or speculative guesses without evidence\n- tell the sub-agent to send findings back to the main agent only\n\nUse these four investigation roles.\n\n### Sub-Agent 1: Reproduction and Scope Investigation\n\nClarify the exact failure shape and its boundaries.\n\nCheck for:\n\n1. The narrowest reliable trigger\n2. Conditions that make the bug appear or disappear\n3. Expected versus actual behavior at the failure boundary\n4. Whether the impact is local, cross-cutting, deterministic, or flaky\n\nThis sub-agent is read-only. It must not edit files, apply patches, or make any other workspace changes.\n\nRecommended sub-agent role: `reviewer`\n\n### Sub-Agent 2: Code Path and Failure Seam Investigation\n\nTrace the most likely execution path and identify the seam where behavior diverges.\n\nCheck for:\n\n1. State transitions, lifecycle edges, or ordering problems\n2. Mismatched assumptions between caller and callee\n3. Data-flow or control-flow breaks\n4. The smallest code region most likely responsible for the failure\n\nThis sub-agent is read-only. It must not edit files, apply patches, or make any other workspace changes.\n\nRecommended sub-agent role: `explorer` for broad tracing, or `reviewer` when a stronger local reasoning pass is more useful\n\n### Sub-Agent 3: Recent Change and Regression Investigation\n\nLook for likely regressors in nearby history or changed contracts.\n\nCheck for:\n\n1. Recent diffs that correlate with the symptom\n2. Config, flag, dependency, schema, or migration drift\n3. Partial updates where several entry points should have changed together\n4. Behavior changes that fit the timing of the bug report\n\nThis sub-agent is read-only. It must not edit files, apply patches, or make any other workspace changes.\n\nRecommended sub-agent role: `reviewer`\n\n### Sub-Agent 4: Proof Plan and Observability Investigation\n\nDetermine the fastest way to confirm or reject the leading hypotheses.\n\nCheck for:\n\n1. The smallest existing test or reproduction that should fail\n2. The most useful current logs, traces, metrics, or assertions\n3. A minimal non-mutating command that could raise confidence quickly\n4. What evidence is missing and how to collect it without broad churn\n\nThis sub-agent is read-only. It must not edit files, apply patches, or make any other workspace changes.\n\nRecommended sub-agent role: `reviewer`\n\nReport only hypotheses that materially improve the odds of finding the real cause. It is better to return two evidence-backed theories than six vague guesses.\n\n## Step 4: Synthesize Ranked Hypotheses\n\nThe main agent owns synthesis. Treat sub-agent output as raw investigation input, not final output.\n\nMerge and rank the hypotheses:\n\n- combine duplicates\n- discard weak speculation\n- prefer evidence over elegance\n- separate likely root causes from mere contributing factors\n- keep alternate theories only when they remain plausible\n\nNormalize the surviving hypotheses into this shape:\n\n1. Hypothesis\n2. Supporting evidence\n3. Missing or conflicting evidence\n4. Smallest proof step\n5. Confidence: high, medium, or low\n\nIf the evidence is too weak for a real ranking, say so directly and present the leading open questions instead.\n\n## Step 5: Output a Clear Diagnosis Path\n\nPresent the result in this order:\n\n1. Most likely root cause\n2. Plausible alternate causes, if any\n3. Fastest proof step\n4. Recommended fix path\n5. Open questions or blockers\n\nWhen the fix is not yet clear, recommend the next proving step instead of pretending the diagnosis is complete.\n\nWhen helpful, group actions into:\n\n- `prove now`\n- `fix next`\n- `follow up later`\n\nDo not implement fixes as part of this skill. The output is a read-only diagnosis with a prioritized path forward.\n\n## Example\n\n**User request:**\n\n> Investigate this failure with @bug-hunt-swarm, prove the root cause, implement the smallest safe fix, and verify it.\n\n## Limitations\n\n- Use this skill only when the task clearly matches its upstream source and local project context.\n- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.\n- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.\n","# Bug Hunt Swarm\n## When to Use\n\nUse this skill when you need parallel read-only multi-agent root-cause investigation for bugs, regressions, crashes, flaky behavior, or unexplained failures. Use when the user asks to investigate a bug, find the root cause, trace a regression, understand why something broke, or wants a ranked diagnosis with the...\n\n\nInvestigate a bug with four read-only sub-agents in parallel, then have the main agent rank the likely causes and recommend the fastest path to prove or fix the issue. This skill is diagnosis-first: do not edit files or implement fixes as part of this workflow.\n\n## Step 1: Build the Bug Packet\n\nStart by collecting the smallest useful investigation packet:\n\n1. Symptom\n2. Expected behavior\n3. Actual behavior\n4. Reproduction steps, if known\n5. Scope of impact\n6. Relevant evidence, such as logs, stack traces, failing tests, screenshots, recent diffs, or environment details\n\nPrefer this source order:\n\n1. Direct user description\n2. Explicit files, stack traces, logs, tests, or screenshots provided by the user\n3. Current git changes or recent repo history when the bug appears regression-like\n4. The smallest relevant code path or subsystem surrounding the failure\n\nIf the bug report is underspecified, infer a minimal problem statement and say what is still unknown.\n\nBefore launching sub-agents, read the closest project instructions and relevant docs for the touched area, such as:\n\n- `AGENTS.md`\n- repo workflow docs\n- architecture, state, routing, schema, or runtime docs for the affected subsystem\n\n## Step 2: Bound the Investigation\n\nWrite a short investigation brief for the swarm:\n\n1. What appears broken\n2. What is not yet proven\n3. What part of the system is most likely involved\n4. What evidence already exists\n5. What kind of proof would count as confirmation\n\nUse read-only evidence gathering where useful:\n\n- `rg`, `git diff`, `git log`, `git show`\n- reading logs, crash traces, and config\n- existing test runs or the smallest safe reproduction command\n\nDo not edit files, inject new instrumentation, or implement fixes as part of this skill.\n\n## Step 3: Launch Four Read-Only Investigators in Parallel\n\nLaunch four sub-agents when the problem is large or ambiguous enough that parallel investigation helps. For a tiny and obvious issue, it is acceptable to investigate locally instead.\n\nFor every sub-agent:\n\n- give the same bug packet and investigation brief\n- state that the sub-agent is read-only\n- do not let the sub-agent edit files, run `apply_patch`, stage changes, commit, or perform any other state-mutating action\n- ask for concise investigation output only\n- ask for: hypothesis, supporting evidence, missing evidence, smallest proof step, and confidence\n- tell the sub-agent to avoid generic code quality feedback, nits, or speculative guesses without evidence\n- tell the sub-agent to send findings back to the main agent only\n\nUse these four investigation roles.\n\n### Sub-Agent 1: Reproduction and Scope Investigation\n\nClarify the exact failure shape and its boundaries.\n\nCheck for:\n\n1. The narrowest reliable trigger\n2. Conditions that make the bug appear or disappear\n3. Expected versus actual behavior at the failure boundary\n4. Whether the impact is local, cross-cutting, deterministic, or flaky\n\nThis sub-agent is read-only. It must not edit files, apply patches, or make any other workspace changes.\n\nRecommended sub-agent role: `reviewer`\n\n### Sub-Agent 2: Code Path and Failure Seam Investigation\n\nTrace the most likely execution path and identify the seam where behavior diverges.\n\nCheck for:\n\n1. State transitions, lifecycle edges, or ordering problems\n2. Mismatched assumptions between caller and callee\n3. Data-flow or control-flow breaks\n4. The smallest code region most likely responsible for the failure\n\nThis sub-agent is read-only. It must not edit files, apply patches, or make any other workspace changes.\n\nRecommended sub-agent role: `explorer` for broad tracing, or `reviewer` when a stronger local reasoning pass is more useful\n\n### Sub-Agent 3: Recent Change and Regression Investigation\n\nLook for likely regressors in nearby history or changed contracts.\n\nCheck for:\n\n1. Recent diffs that correlate with the symptom\n2. Config, flag, dependency, schema, or migration drift\n3. Partial updates where several entry points should have changed together\n4. Behavior changes that fit the timing of the bug report\n\nThis sub-agent is read-only. It must not edit files, apply patches, or make any other workspace changes.\n\nRecommended sub-agent role: `reviewer`\n\n### Sub-Agent 4: Proof Plan and Observability Investigation\n\nDetermine the fastest way to confirm or reject the leading hypotheses.\n\nCheck for:\n\n1. The smallest existing test or reproduction that should fail\n2. The most useful current logs, traces, metrics, or assertions\n3. A minimal non-mutating command that could raise confidence quickly\n4. What evidence is missing and how to collect it without broad churn\n\nThis sub-agent is read-only. It must not edit files, apply patches, or make any other workspace changes.\n\nRecommended sub-agent role: `reviewer`\n\nReport only hypotheses that materially improve the odds of finding the real cause. It is better to return two evidence-backed theories than six vague guesses.\n\n## Step 4: Synthesize Ranked Hypotheses\n\nThe main agent owns synthesis. Treat sub-agent output as raw investigation input, not final output.\n\nMerge and rank the hypotheses:\n\n- combine duplicates\n- discard weak speculation\n- prefer evidence over elegance\n- separate likely root causes from mere contributing factors\n- keep alternate theories only when they remain plausible\n\nNormalize the surviving hypotheses into this shape:\n\n1. Hypothesis\n2. Supporting evidence\n3. Missing or conflicting evidence\n4. Smallest proof step\n5. Confidence: high, medium, or low\n\nIf the evidence is too weak for a real ranking, say so directly and present the leading open questions instead.\n\n## Step 5: Output a Clear Diagnosis Path\n\nPresent the result in this order:\n\n1. Most likely root cause\n2. Plausible alternate causes, if any\n3. Fastest proof step\n4. Recommended fix path\n5. Open questions or blockers\n\nWhen the fix is not yet clear, recommend the next proving step instead of pretending the diagnosis is complete.\n\nWhen helpful, group actions into:\n\n- `prove now`\n- `fix next`\n- `follow up later`\n\nDo not implement fixes as part of this skill. The output is a read-only diagnosis with a prioritized path forward.\n\n## Example\n\n**User request:**\n\n> Investigate this failure with @bug-hunt-swarm, prove the root cause, implement the smallest safe fix, and verify it.\n\n## Limitations\n\n- Use this skill only when the task clearly matches its upstream source and local project context.\n- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.\n- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.\n",{"name":5,"risk":24,"source":25,"license":15,"date_added":26,"description":7,"source_repo":27,"source_type":28,"license_source":29},"safe","https:\u002F\u002Fgithub.com\u002FDimillian\u002FSkills\u002Ftree\u002Fmain\u002Fbug-hunt-swarm",1782864000000,"Dimillian\u002FSkills","community","https:\u002F\u002Fgithub.com\u002FDimillian\u002FSkills\u002Fblob\u002Fmain\u002FLICENSE","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","05-技能与代理开发\u002Fbug-hunt-swarm",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill bug-hunt-swarm",{"tool":44,"command":45},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill bug-hunt-swarm",{"tool":47,"command":48},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill bug-hunt-swarm","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fbug-hunt-swarm\u002FSKILL.md",true,[52],{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},"agents\u002Fopenai.yaml","REFERENCE","参考文档",261,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fbug-hunt-swarm\u002Fagents\u002Fopenai.yaml",[59,67,72,79,86,93],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":66},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":68,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":66},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":66},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"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":66},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":66},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":66},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]