[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M758GR1HBCQXCCQJENDFZT6G":3,"skill-same:01M758GR1HBCQXCCQJENDFZT6G":44},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M758GR1HBCQXCCQJENDFZT6G","investigate",null,"系统化根因调试:历史搜索→复现→scope lock→模式匹配→假设验证→修复→验证→报告 + 修完扫同类。铁律:无根因不修。Trigger:\u002Finvestigate、调查、排查、为什么挂了、这个bug、根因分析、stack trace、昨天还好的。","AbyssCN\u002Foh-my-dag","AbyssCN","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F43731064?v=4","01M758GF48B4J35SNWQZS4T8YM","01M758GF4YQNVGCZG82Y351MWV",44,"MIT","https:\u002F\u002Fgithub.com\u002FAbyssCN\u002Foh-my-dag\u002Fblob\u002Fmain\u002Fclient-skills\u002Finvestigate\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: investigate\ndescription: 系统化根因调试:历史搜索→复现→scope lock→模式匹配→假设验证→修复→验证→报告 + 修完扫同类。铁律:无根因不修。Trigger:\u002Finvestigate、调查、排查、为什么挂了、这个bug、根因分析、stack trace、昨天还好的。\n---\n\n# \u002Finvestigate — 系统化根因调试\n\n> **铁律:无根因不修。** 修症状 = 打地鼠。找到根因再动手,诊断阶段禁提修复方案。\n\n纯方法论 skill(不封特定 MCP 工具,用 runtime 原生 Grep\u002FRead\u002Fgit;需并行跑多假设时可派多个子 agent)。\n\n## Phase 1 — 历史搜索(先查后调)\n同一消息并行发:`git log --oneline -20 -- \u003C相关文件>`(近期变更)+ Grep 既有 `docs\u002Fplan\u002F`·NOTES·error 记录搜错误关键词(有先例走 \u002Fomd-recall 先召回)。命中已知修复 → 直接引用,跳到修复。\n\n## Phase 2 — 复现\n确定性触发 + 存证据(错误信息\u002F堆栈\u002F复现步骤)。信息不足 → 逐个追问(一次一问)。不能稳定复现 → 收集更多证据再继续,别猜。\n\n## Phase 3 — Scope Lock\n从症状追到最窄受影响目录,声明范围;此后 Edit 只在范围内,越界先问 owner。危险信号立即停:「顺手修个相关的」(不顺手,记 follow-up)、「既然在改不如重构」(不重构,本 bug 修完再评估)。\n\n## Phase 4 — 模式匹配\n先 step-back 自问:这类症状(数据不一致\u002F超时\u002F类型错\u002F竞态\u002F权限泄漏\u002Fschema 漂移)在本技术栈通常由哪层引起?建宏观诊断框架再缩范围,别直接跳到最\"像\"的模式。**同文件反复修 bug = 架构问题,不是巧合**。\n\n## Phase 5 — 假设验证(最多 3 个)\n每假设三步推导:**观察**(引 file:line 我看到什么)→ **推论**(若成立还应看到什么)→ **验证**(设计能区分成立\u002F不成立的实验)。追踪表标 CONFIRMED\u002FREJECTED。先验证再修(可疑根因处加临时 log\u002F断言,跑复现看证据是否吻合)。**三振出局**:3 个假设全败 → STOP 问 owner(A 继续有新假设 \u002F B 升级人工 \u002F C 埋点观察)。危险信号:还没追数据流就提修复 = 在猜。\n\n## Phase 6 — 修复\n根因确认后最小改动:最少文件、最少行,不顺手重构相邻代码。写回归测试(不修 FAIL、修后 PASS),跑测试套件贴输出。改 >5 文件 → 问 owner(bugfix 爆炸半径偏大:继续 \u002F 拆分 \u002F 重想)。\n\n## Phase 7 — 验证闭环\n复现原始场景确认已修 + 跑变更相关验证。不说\"应该能修好\",验证并证明。\n\n## Phase 8 — 报告 + 扫同类\n报告:症状 \u002F 根因(为什么)\u002F 模式 \u002F 修复(file:line)\u002F 证据 \u002F 回归测试 \u002F 状态(DONE · DONE_WITH_CONCERNS · BLOCKED)。**修完扫一片**:用根因反推同类——Grep 同 pattern(根因是\"缺 scope 过滤\" → 全仓找所有 db 访问点;\"未校验入参\" → 找所有 untrusted 入口)。>5 处别一次全修,修 1-2 关键,其余记 NOTES 留 follow-up。\n\n## 与既有 skill 的边界\n- investigate = 某**失败**的**根因**调查。**审一批 diff 找 bug** → \u002Fomd-review;**扫安全漏洞** → \u002Fsecurity-review;**找过度工程** → \u002Fponytail-review。修复方案涉及大改前可用 \u002Fgrill 审。\n","# \u002Finvestigate — 系统化根因调试\n\n> **铁律:无根因不修。** 修症状 = 打地鼠。找到根因再动手,诊断阶段禁提修复方案。\n\n纯方法论 skill(不封特定 MCP 工具,用 runtime 原生 Grep\u002FRead\u002Fgit;需并行跑多假设时可派多个子 agent)。\n\n## Phase 1 — 历史搜索(先查后调)\n同一消息并行发:`git log --oneline -20 -- \u003C相关文件>`(近期变更)+ Grep 既有 `docs\u002Fplan\u002F`·NOTES·error 记录搜错误关键词(有先例走 \u002Fomd-recall 先召回)。命中已知修复 → 直接引用,跳到修复。\n\n## Phase 2 — 复现\n确定性触发 + 存证据(错误信息\u002F堆栈\u002F复现步骤)。信息不足 → 逐个追问(一次一问)。不能稳定复现 → 收集更多证据再继续,别猜。\n\n## Phase 3 — Scope Lock\n从症状追到最窄受影响目录,声明范围;此后 Edit 只在范围内,越界先问 owner。危险信号立即停:「顺手修个相关的」(不顺手,记 follow-up)、「既然在改不如重构」(不重构,本 bug 修完再评估)。\n\n## Phase 4 — 模式匹配\n先 step-back 自问:这类症状(数据不一致\u002F超时\u002F类型错\u002F竞态\u002F权限泄漏\u002Fschema 漂移)在本技术栈通常由哪层引起?建宏观诊断框架再缩范围,别直接跳到最\"像\"的模式。**同文件反复修 bug = 架构问题,不是巧合**。\n\n## Phase 5 — 假设验证(最多 3 个)\n每假设三步推导:**观察**(引 file:line 我看到什么)→ **推论**(若成立还应看到什么)→ **验证**(设计能区分成立\u002F不成立的实验)。追踪表标 CONFIRMED\u002FREJECTED。先验证再修(可疑根因处加临时 log\u002F断言,跑复现看证据是否吻合)。**三振出局**:3 个假设全败 → STOP 问 owner(A 继续有新假设 \u002F B 升级人工 \u002F C 埋点观察)。危险信号:还没追数据流就提修复 = 在猜。\n\n## Phase 6 — 修复\n根因确认后最小改动:最少文件、最少行,不顺手重构相邻代码。写回归测试(不修 FAIL、修后 PASS),跑测试套件贴输出。改 >5 文件 → 问 owner(bugfix 爆炸半径偏大:继续 \u002F 拆分 \u002F 重想)。\n\n## Phase 7 — 验证闭环\n复现原始场景确认已修 + 跑变更相关验证。不说\"应该能修好\",验证并证明。\n\n## Phase 8 — 报告 + 扫同类\n报告:症状 \u002F 根因(为什么)\u002F 模式 \u002F 修复(file:line)\u002F 证据 \u002F 回归测试 \u002F 状态(DONE · DONE_WITH_CONCERNS · BLOCKED)。**修完扫一片**:用根因反推同类——Grep 同 pattern(根因是\"缺 scope 过滤\" → 全仓找所有 db 访问点;\"未校验入参\" → 找所有 untrusted 入口)。>5 处别一次全修,修 1-2 关键,其余记 NOTES 留 follow-up。\n\n## 与既有 skill 的边界\n- investigate = 某**失败**的**根因**调查。**审一批 diff 找 bug** → \u002Fomd-review;**扫安全漏洞** → \u002Fsecurity-review;**找过度工程** → \u002Fponytail-review。修复方案涉及大改前可用 \u002Fgrill 审。\n",{"name":5,"description":7},"main","624a2e346a5bcd50024a70081b3b5a7f8a80c72b","client-skills\u002Finvestigate",2,"https:\u002F\u002Fgithub.com\u002FAbyssCN\u002Foh-my-dag","https:\u002F\u002Fgithub.com\u002FAbyssCN","2026-10-11 22:17:23",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add AbyssCN\u002Foh-my-dag --skill investigate",{"tool":36,"command":37},"bunx","bunx skills add AbyssCN\u002Foh-my-dag --skill investigate",{"tool":39,"command":40},"pnpm","pnpm dlx skills add AbyssCN\u002Foh-my-dag --skill investigate","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAbyssCN\u002Foh-my-dag\u002Fblob\u002Fmain\u002Fclient-skills\u002Finvestigate\u002FSKILL.md",true,[],[45,51,57,63,70,77],{"skillNo":46,"name":47,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":48,"categories":49,"keywords":50,"publishedAt":18},"01M758HVAFZ52XFKX1VP0PD97F","skill-with-check","https:\u002F\u002Fgithub.com\u002FAbyssCN\u002Foh-my-dag\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Fs1\u002Fskill-with-check\u002FSKILL.md",[],[],{"skillNo":52,"name":53,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":18},"01M758HRR8DJR96R16ZRTJZ5SC","skill-prose-bans","https:\u002F\u002Fgithub.com\u002FAbyssCN\u002Foh-my-dag\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Fs1\u002Fskill-prose-bans\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":18},"01M758HPR7948QXXHKR2BT2PMN","skill-escalation-skill","https:\u002F\u002Fgithub.com\u002FAbyssCN\u002Foh-my-dag\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Fs1\u002Fskill-escalation-skill\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":18},"01M758HM9488S9X0J803DV4XYD","bugfix-triage","修 bug 前的定位方法论 —— 最小复现、二分缩圈、区分\"测试错了\"与\"实现错了\"","https:\u002F\u002Fgithub.com\u002FAbyssCN\u002Foh-my-dag\u002Fblob\u002Fmain\u002Ftemplates\u002Fpacks\u002Ftdd-bugfix\u002Fskills\u002Fbugfix-triage\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":18},"01M758HJ9V6ZK77GVRGZ0BHENS","ui-reviewer","Review rendered UI screenshots for hierarchy, spacing, readability, states, consistency, and visual slop.","https:\u002F\u002Fgithub.com\u002FAbyssCN\u002Foh-my-dag\u002Fblob\u002Fmain\u002Fclient-skills\u002Fui-reviewer\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":18},"01M758HGQ636V2W83E7TTH3C80","sast","确定性 semgrep 静态扫描(SAST)+ 结构化报告。零 LLM 零成本,规则命中即事实。Trigger:\u002Fsast、静态扫描、semgrep、扫一下代码。","https:\u002F\u002Fgithub.com\u002FAbyssCN\u002Foh-my-dag\u002Fblob\u002Fmain\u002Fclient-skills\u002Fsast\u002FSKILL.md",[],[]]