[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6QJBJ0YPVEWGEXZH3PJRRTT":3,"skill-same:01M6QJBJ0YPVEWGEXZH3PJRRTT":89},{"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":33,"publishedAt":54,"linkOnly":55,"markdownContent":56,"markdownBody":57,"frontMatter":58,"refName":59,"commitSha":60,"skillDirectory":61,"forksCount":13,"repositoryHtmlUrl":62,"repositoryHomepageUrl":6,"ownerHtmlUrl":63,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":64,"install":65,"resources":78},"01M6QJBJ0YPVEWGEXZH3PJRRTT","code-review-workflow",null,"Executes comprehensive 4-phase code review: basic review, quality check, bundle analysis, and test coverage. Should be used when the user mentions comprehensive code review, checking code quality, or reviewing staged changes with multi-phase analysis. This is the comprehensive review workflow, distinct from focused skills like frontend-code-review, staged-code-review, or code-change-test-designer.","ImaginerLabs\u002Fskill-manager","ImaginerLabs","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F214277308?v=4","01M6QGGDPNF15RMMT1RCFDH9FN","01M6QGGDTH5BY64DQ123NR8M33",0,"MIT","https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager\u002Fblob\u002Fmain\u002Fskills\u002Ftesting\u002Fcode-review-workflow\u002FSKILL.md",[17,22,25,28],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":26,"categoryName":27,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":29,"categoryName":30,"taxonomyType":31,"taxonomyTypeDesc":32},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53],"review","workflow","code review workflow","code","code review","analysis","phase","with","comprehensive code review","multi","basic","quality check","coverage","check","code-review","code quality","change","test","frontend","testing","2026-11-10 10:12:30",false,"---\nname: code-review-workflow\ndescription: >-\n  Executes comprehensive 4-phase code review: basic review, quality check, bundle analysis, and test coverage.\n  Should be used when the user mentions comprehensive code review, checking code quality, or reviewing\n  staged changes with multi-phase analysis.\n  This is the comprehensive review workflow, distinct from focused skills like frontend-code-review,\n  staged-code-review, or code-change-test-designer.\ncategory: testing\n---\n\n# 代码综合审查工作流\n\n执行四阶段审查，产出结构化 Markdown 报告。每个阶段独立完成，前置阶段的阻断性问题不阻塞后续阶段。\n\n## 阶段概览\n\n| 阶段 | 名称 | 核心目标 | 输入 | 输出 |\n| ---- | ---- | -------- | ---- | ---- |\n| 1 | 基础代码审查 | 发现阻断性问题（安全、错误处理、边界） | 代码\u002Fdiff | 问题清单（阻断\u002F建议） |\n| 2 | 代码质量检查 | 深度分析（Lint、健壮性、性能） | 代码 + Stage 1 结果 | 质量问题清单 |\n| 3 | 体积优化分析 | 评估 Bundle Size 影响 | 代码 + 依赖声明 | 优化建议清单 |\n| 4 | 测试覆盖与验证 | 设计用例 + 静态验证 | 代码 + diff | 测试用例 + 验证结论 |\n\n## 审查目标识别\n\n按优先级判断审查模式：\n\n1. `--commit=\u003Chash>` → 读取该 commit 的 diff\n2. `--staged` → 读取暂存区变更\n3. `--path=\u003Cpath>` 或 `--file=\u003Cfile>` → 读取指定文件\u002F目录的完整代码\n4. `--focus=\u003Carea>` → 可选，仅执行指定维度（quality \u002F bundle \u002F test）\n5. 无参数 → 询问用户选择模式\n\n### 代码获取方式\n\n| 模式      | 获取方式                                              | 审查重点      |\n| --------- | ----------------------------------------------------- | ------------- |\n| Commit    | `git show \u003Chash> --stat` + `git show \u003Chash>`          | diff 变更部分 |\n| 暂存区    | `git diff --staged --name-only` + `git diff --staged` | diff 变更部分 |\n| 文件\u002F目录 | `read_file` \u002F `list_dir` 后读取                       | 完整代码内容  |\n\nCommit\u002F暂存区模式还需用 `git show \u003Chash>:\u003Cfile>` 读取关键文件的完整上下文，避免 diff 孤岛效应。\n\n---\n\n## Stage 1: 基础代码审查\n\n**目标**：发现调试遗留、敏感信息、语法问题、边界遗漏。\n\n执行步骤：\n\n1. 读取目标代码，梳理变更文件清单\n2. 识别技术栈（React\u002FVue\u002FGo\u002FPython 等）\n3. 按 `references\u002Fchecklist.md` 中的「基础检查项」逐项扫描\n4. 执行技术栈专项检查（见 checklist.md §2）\n5. 问题按严重程度分为 **阻断性** 和 **建议项**\n\n关键原则：\n\n- 敏感信息泄露（硬编码密钥\u002FToken）必须标为阻断性\n- 调试代码遗留（console.log\u002Fdebugger）标为建议项，除非在关键路径上\n\n---\n\n## Stage 2: 代码质量检查\n\n**目标**：深度分析健壮性、副作用、Lint 问题、性能隐患。\n\n执行步骤：\n\n1. 运行 Lint 检查（使用 `read_lints` 工具，或项目自带的 lint 命令），重点关注：\n   - `no-undef`、`no-unused-vars`、`exhaustive-deps`（高危）\n   - `no-explicit-any`、`rules-of-hooks`（中危）\n2. 按 `references\u002Fchecklist.md` §3 评估健壮性、副作用、性能\n3. Commit\u002F暂存区模式仅分析变更部分；文件模式分析完整代码\n\n关键原则：\n\n- 竞态条件和内存泄漏（未清理的订阅\u002F定时器）是高频问题，务必检查\n- 修改公用组件时，需要用 `search_content` 检查下游调用方是否受影响\n\n---\n\n## Stage 3: 体积优化分析\n\n**目标**：评估变更对 Bundle Size 的影响，给出分级优化建议。\n\n执行步骤：\n\n1. 从 diff 或 import 语句识别新增依赖\n2. 按 `references\u002Fchecklist.md` §4 检查依赖引入方式、冗余代码、懒加载机会\n3. 用分级标准（? >10KB \u002F ? 2~10KB \u002F ? \u003C2KB gzip）给出建议\n\n关键原则：\n\n- 全量引入大型库（lodash\u002Fmoment\u002Fantd 全量）是常见问题，优先标记\n- 体积分析只在变更引入新依赖或大型代码块时才有意义，纯逻辑修改可简述\n\n---\n\n## Stage 4: 测试覆盖与验证\n\n**目标**：设计主流程和边缘情况的测试用例，并通过静态代码分析验证测试与实现的一致性。\n\n执行步骤：\n\n1. 梳理本次修改的目的和能力变化\n2. 识别技术栈对应的测试框架（见 checklist.md §5）\n3. 设计主流程链路测试（Happy Path）和边缘情况测试\n4. 提供 Mock 策略建议\n5. **静态代码分析验证测试用例**（关键步骤）\n\n关键原则：\n\n- 测试用例设计应覆盖修改涉及的能力变化，而非面面俱到\n- 优先 P0（主流程）和 P1（关键边缘），P2 仅列举\n- **必须对设计的测试用例进行代码验证**，不能只设计不验证\n\n### 4.5 静态代码分析验证测试用例\n\n**目的**：读取变更文件的完整源码，逐条对照设计的测试用例，通过代码逻辑推导验证每条用例的预期结果是否与实现一致。\n\n验证结论标记：\n\n| 结论标记 | 含义                                                      |\n| -------- | --------------------------------------------------------- |\n| ✅ 通过  | 代码逻辑与预期一致，该用例在正确实现下应当通过            |\n| ❌ 失败  | 代码逻辑与预期矛盾，该用例会失败，说明存在 Bug 或设计偏差 |\n| ⚠️ 存疑  | 代码逻辑存在歧义、依赖运行时状态或外部 Mock，无法静态确认 |\n\n验证步骤：\n\n1. 使用 `read_file` 读取 diff 中涉及的完整源文件（不只是变更行）\n2. 逐条取出设计的测试用例，模拟其输入，在脑中执行代码逻辑\n3. 对比执行结果与用例的预期输出，得出 ✅ \u002F ❌ \u002F ⚠️ 结论\n4. 对 ❌ 用例：说明代码哪一行\u002F哪段逻辑导致失败，并给出修复建议\n5. 对 ⚠️ 用例：说明不确定的原因（如依赖接口返回值、环境变量等）\n\n**特别注意**：\n\n- 必须读取完整源码进行验证，而非仅凭 diff 推断\n- ❌ 结论是重要发现，应在报告的\"必须处理\"部分重点标注\n- ⚠️ 结论需标注为\"需运行时验证\"，不能忽略\n\n---\n\n## 报告输出\n\n使用 `references\u002Freport-template.md` 中的模板生成报告。核心设计原则：\n\n1. **行动项前置** — 报告最前面就是「必须处理」和「建议优化」，让用户第一时间知道该做什么\n2. **阻断性问题带代码 diff** — 不只说问题，直接给出修复建议的代码对比\n3. **详情在后** — 四阶段的详细分析结果放在行动项之后，供需要深入了解时查阅\n4. **评分精简** — 每个维度一句话说明扣分原因，不做冗长的逐项打分\n\n### 评分规则\n\n| 维度         | 权重 | 评分依据                                                    |\n| ------------ | ---- | ----------------------------------------------------------- |\n| 基础代码审查 | 25%  | 无阻断性问题满分，每个阻断 -10，每个建议 -3                 |\n| 代码质量检查 | 30%  | Lint 错误、健壮性、性能问题综合评估                         |\n| 体积优化分析 | 20%  | 按高\u002F中\u002F低优先级建议数量扣分                                 |\n| 测试用例覆盖 | 25%  | 全部 ✅ 通过满分，有 ❌ 失败用例 -20，有 ⚠️ 存疑 -10        |\n\n评分分级：? 优秀 90-100 \u002F ? 良好 70-89 \u002F ? 需改进 \u003C70\n\n**测试覆盖评分细则**：\n- 全部 ✅ 通过：100 分\n- 有 ⚠️ 需运行时验证的用例（无法静态确认）：-10 分\n- 有 ❌ 代码逻辑与预期不符的用例（代码逻辑错误）：-20 分\n\n---\n\n## 执行策略\n\n### 工具使用建议\n\n| 工具 | 用途 | 使用场景 |\n| ---- | ---- | -------- |\n| `read_file` | 读取代码文件 | 批量读取，避免逐文件串行 |\n| `read_lints` | 获取 IDE 诊断 | Lint 检查，比手动分析更准确 |\n| `search_content` | 搜索引用 | 评估修改的下游影响 |\n| `git show` | 读取历史版本 | Commit 模式下补充完整上下文 |\n\n### 执行顺序建议\n\n**推荐顺序**：Stage 1 → Stage 2 → Stage 3 → Stage 4\n\n**原因**：\n1. Stage 1 识别阻断性问题，需要优先发现\n2. Stage 2 依赖 Stage 1 的基础审查结果\n3. Stage 3 和 Stage 4 可并行执行（各自独立分析）\n\n**并行优化**：当变更涉及多个不相关文件时，可以并行执行 Stage 2-4 的分析。\n\n### 常见问题模式识别\n\n快速识别以下高频问题模式：\n\n| 模式 | 特征 | 严重性 |\n| ---- | ---- | ------ |\n| 内存泄漏 | useEffect 无清理、订阅未取消、定时器未清除 | 阻断 |\n| 敏感信息泄露 | 硬编码 token\u002Fsecret\u002Fpassword | 阻断 |\n| 错误被吞 | catch 块空实现、只 console.error 不处理 | 阻断 |\n| 竞态条件 | 异步操作无 AbortController、fast-click 重复提交 | 阻断 |\n| 类型安全 | `any` 类型滥用、缺少类型守卫 | 建议 |\n| 性能问题 | 大列表无虚拟化、同步 heavy 操作 | 建议 |\n\n### 大规模变更的处理\n\n当变更涉及超过 10 个文件时：\n\n1. 先用 `git show --stat` 或 `git diff --staged --stat` 获取全局视图\n2. 优先审查核心业务逻辑文件（组件、hooks、工具函数）\n3. 配置文件、类型定义、样式文件可简要说明\n4. 报告中标注「因变更规模较大，部分文件为简要审查」\n\n---\n\n## 参考文件\n\n| 文件                            | 用途         | 何时读取         |\n| ------------------------------- | ------------ | ---------------- |\n| `references\u002Fchecklist.md`       | 完整检查清单 | 执行各阶段审查时 |\n| `references\u002Freport-template.md` | 报告模板     | 生成最终报告时   |\n","# 代码综合审查工作流\n\n执行四阶段审查，产出结构化 Markdown 报告。每个阶段独立完成，前置阶段的阻断性问题不阻塞后续阶段。\n\n## 阶段概览\n\n| 阶段 | 名称 | 核心目标 | 输入 | 输出 |\n| ---- | ---- | -------- | ---- | ---- |\n| 1 | 基础代码审查 | 发现阻断性问题（安全、错误处理、边界） | 代码\u002Fdiff | 问题清单（阻断\u002F建议） |\n| 2 | 代码质量检查 | 深度分析（Lint、健壮性、性能） | 代码 + Stage 1 结果 | 质量问题清单 |\n| 3 | 体积优化分析 | 评估 Bundle Size 影响 | 代码 + 依赖声明 | 优化建议清单 |\n| 4 | 测试覆盖与验证 | 设计用例 + 静态验证 | 代码 + diff | 测试用例 + 验证结论 |\n\n## 审查目标识别\n\n按优先级判断审查模式：\n\n1. `--commit=\u003Chash>` → 读取该 commit 的 diff\n2. `--staged` → 读取暂存区变更\n3. `--path=\u003Cpath>` 或 `--file=\u003Cfile>` → 读取指定文件\u002F目录的完整代码\n4. `--focus=\u003Carea>` → 可选，仅执行指定维度（quality \u002F bundle \u002F test）\n5. 无参数 → 询问用户选择模式\n\n### 代码获取方式\n\n| 模式      | 获取方式                                              | 审查重点      |\n| --------- | ----------------------------------------------------- | ------------- |\n| Commit    | `git show \u003Chash> --stat` + `git show \u003Chash>`          | diff 变更部分 |\n| 暂存区    | `git diff --staged --name-only` + `git diff --staged` | diff 变更部分 |\n| 文件\u002F目录 | `read_file` \u002F `list_dir` 后读取                       | 完整代码内容  |\n\nCommit\u002F暂存区模式还需用 `git show \u003Chash>:\u003Cfile>` 读取关键文件的完整上下文，避免 diff 孤岛效应。\n\n---\n\n## Stage 1: 基础代码审查\n\n**目标**：发现调试遗留、敏感信息、语法问题、边界遗漏。\n\n执行步骤：\n\n1. 读取目标代码，梳理变更文件清单\n2. 识别技术栈（React\u002FVue\u002FGo\u002FPython 等）\n3. 按 `references\u002Fchecklist.md` 中的「基础检查项」逐项扫描\n4. 执行技术栈专项检查（见 checklist.md §2）\n5. 问题按严重程度分为 **阻断性** 和 **建议项**\n\n关键原则：\n\n- 敏感信息泄露（硬编码密钥\u002FToken）必须标为阻断性\n- 调试代码遗留（console.log\u002Fdebugger）标为建议项，除非在关键路径上\n\n---\n\n## Stage 2: 代码质量检查\n\n**目标**：深度分析健壮性、副作用、Lint 问题、性能隐患。\n\n执行步骤：\n\n1. 运行 Lint 检查（使用 `read_lints` 工具，或项目自带的 lint 命令），重点关注：\n   - `no-undef`、`no-unused-vars`、`exhaustive-deps`（高危）\n   - `no-explicit-any`、`rules-of-hooks`（中危）\n2. 按 `references\u002Fchecklist.md` §3 评估健壮性、副作用、性能\n3. Commit\u002F暂存区模式仅分析变更部分；文件模式分析完整代码\n\n关键原则：\n\n- 竞态条件和内存泄漏（未清理的订阅\u002F定时器）是高频问题，务必检查\n- 修改公用组件时，需要用 `search_content` 检查下游调用方是否受影响\n\n---\n\n## Stage 3: 体积优化分析\n\n**目标**：评估变更对 Bundle Size 的影响，给出分级优化建议。\n\n执行步骤：\n\n1. 从 diff 或 import 语句识别新增依赖\n2. 按 `references\u002Fchecklist.md` §4 检查依赖引入方式、冗余代码、懒加载机会\n3. 用分级标准（? >10KB \u002F ? 2~10KB \u002F ? \u003C2KB gzip）给出建议\n\n关键原则：\n\n- 全量引入大型库（lodash\u002Fmoment\u002Fantd 全量）是常见问题，优先标记\n- 体积分析只在变更引入新依赖或大型代码块时才有意义，纯逻辑修改可简述\n\n---\n\n## Stage 4: 测试覆盖与验证\n\n**目标**：设计主流程和边缘情况的测试用例，并通过静态代码分析验证测试与实现的一致性。\n\n执行步骤：\n\n1. 梳理本次修改的目的和能力变化\n2. 识别技术栈对应的测试框架（见 checklist.md §5）\n3. 设计主流程链路测试（Happy Path）和边缘情况测试\n4. 提供 Mock 策略建议\n5. **静态代码分析验证测试用例**（关键步骤）\n\n关键原则：\n\n- 测试用例设计应覆盖修改涉及的能力变化，而非面面俱到\n- 优先 P0（主流程）和 P1（关键边缘），P2 仅列举\n- **必须对设计的测试用例进行代码验证**，不能只设计不验证\n\n### 4.5 静态代码分析验证测试用例\n\n**目的**：读取变更文件的完整源码，逐条对照设计的测试用例，通过代码逻辑推导验证每条用例的预期结果是否与实现一致。\n\n验证结论标记：\n\n| 结论标记 | 含义                                                      |\n| -------- | --------------------------------------------------------- |\n| ✅ 通过  | 代码逻辑与预期一致，该用例在正确实现下应当通过            |\n| ❌ 失败  | 代码逻辑与预期矛盾，该用例会失败，说明存在 Bug 或设计偏差 |\n| ⚠️ 存疑  | 代码逻辑存在歧义、依赖运行时状态或外部 Mock，无法静态确认 |\n\n验证步骤：\n\n1. 使用 `read_file` 读取 diff 中涉及的完整源文件（不只是变更行）\n2. 逐条取出设计的测试用例，模拟其输入，在脑中执行代码逻辑\n3. 对比执行结果与用例的预期输出，得出 ✅ \u002F ❌ \u002F ⚠️ 结论\n4. 对 ❌ 用例：说明代码哪一行\u002F哪段逻辑导致失败，并给出修复建议\n5. 对 ⚠️ 用例：说明不确定的原因（如依赖接口返回值、环境变量等）\n\n**特别注意**：\n\n- 必须读取完整源码进行验证，而非仅凭 diff 推断\n- ❌ 结论是重要发现，应在报告的\"必须处理\"部分重点标注\n- ⚠️ 结论需标注为\"需运行时验证\"，不能忽略\n\n---\n\n## 报告输出\n\n使用 `references\u002Freport-template.md` 中的模板生成报告。核心设计原则：\n\n1. **行动项前置** — 报告最前面就是「必须处理」和「建议优化」，让用户第一时间知道该做什么\n2. **阻断性问题带代码 diff** — 不只说问题，直接给出修复建议的代码对比\n3. **详情在后** — 四阶段的详细分析结果放在行动项之后，供需要深入了解时查阅\n4. **评分精简** — 每个维度一句话说明扣分原因，不做冗长的逐项打分\n\n### 评分规则\n\n| 维度         | 权重 | 评分依据                                                    |\n| ------------ | ---- | ----------------------------------------------------------- |\n| 基础代码审查 | 25%  | 无阻断性问题满分，每个阻断 -10，每个建议 -3                 |\n| 代码质量检查 | 30%  | Lint 错误、健壮性、性能问题综合评估                         |\n| 体积优化分析 | 20%  | 按高\u002F中\u002F低优先级建议数量扣分                                 |\n| 测试用例覆盖 | 25%  | 全部 ✅ 通过满分，有 ❌ 失败用例 -20，有 ⚠️ 存疑 -10        |\n\n评分分级：? 优秀 90-100 \u002F ? 良好 70-89 \u002F ? 需改进 \u003C70\n\n**测试覆盖评分细则**：\n- 全部 ✅ 通过：100 分\n- 有 ⚠️ 需运行时验证的用例（无法静态确认）：-10 分\n- 有 ❌ 代码逻辑与预期不符的用例（代码逻辑错误）：-20 分\n\n---\n\n## 执行策略\n\n### 工具使用建议\n\n| 工具 | 用途 | 使用场景 |\n| ---- | ---- | -------- |\n| `read_file` | 读取代码文件 | 批量读取，避免逐文件串行 |\n| `read_lints` | 获取 IDE 诊断 | Lint 检查，比手动分析更准确 |\n| `search_content` | 搜索引用 | 评估修改的下游影响 |\n| `git show` | 读取历史版本 | Commit 模式下补充完整上下文 |\n\n### 执行顺序建议\n\n**推荐顺序**：Stage 1 → Stage 2 → Stage 3 → Stage 4\n\n**原因**：\n1. Stage 1 识别阻断性问题，需要优先发现\n2. Stage 2 依赖 Stage 1 的基础审查结果\n3. Stage 3 和 Stage 4 可并行执行（各自独立分析）\n\n**并行优化**：当变更涉及多个不相关文件时，可以并行执行 Stage 2-4 的分析。\n\n### 常见问题模式识别\n\n快速识别以下高频问题模式：\n\n| 模式 | 特征 | 严重性 |\n| ---- | ---- | ------ |\n| 内存泄漏 | useEffect 无清理、订阅未取消、定时器未清除 | 阻断 |\n| 敏感信息泄露 | 硬编码 token\u002Fsecret\u002Fpassword | 阻断 |\n| 错误被吞 | catch 块空实现、只 console.error 不处理 | 阻断 |\n| 竞态条件 | 异步操作无 AbortController、fast-click 重复提交 | 阻断 |\n| 类型安全 | `any` 类型滥用、缺少类型守卫 | 建议 |\n| 性能问题 | 大列表无虚拟化、同步 heavy 操作 | 建议 |\n\n### 大规模变更的处理\n\n当变更涉及超过 10 个文件时：\n\n1. 先用 `git show --stat` 或 `git diff --staged --stat` 获取全局视图\n2. 优先审查核心业务逻辑文件（组件、hooks、工具函数）\n3. 配置文件、类型定义、样式文件可简要说明\n4. 报告中标注「因变更规模较大，部分文件为简要审查」\n\n---\n\n## 参考文件\n\n| 文件                            | 用途         | 何时读取         |\n| ------------------------------- | ------------ | ---------------- |\n| `references\u002Fchecklist.md`       | 完整检查清单 | 执行各阶段审查时 |\n| `references\u002Freport-template.md` | 报告模板     | 生成最终报告时   |\n",{"name":5,"category":53,"description":7},"main","b9a52d8e27455bdad953d64928696d028223ea1b","skills\u002Ftesting\u002Fcode-review-workflow","https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager","https:\u002F\u002Fgithub.com\u002FImaginerLabs","2026-04-18 16:27:13",{"source":8,"skillName":5,"commands":66,"prompt":76,"zipAvailable":77},[67,70,73],{"tool":68,"command":69},"npx","npx skills add ImaginerLabs\u002Fskill-manager --skill code-review-workflow",{"tool":71,"command":72},"bunx","bunx skills add ImaginerLabs\u002Fskill-manager --skill code-review-workflow",{"tool":74,"command":75},"pnpm","pnpm dlx skills add ImaginerLabs\u002Fskill-manager --skill code-review-workflow","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager\u002Fblob\u002Fmain\u002Fskills\u002Ftesting\u002Fcode-review-workflow\u002FSKILL.md",true,[79,85],{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fchecklist.md","REFERENCE","参考文档",10776,"https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager\u002Fblob\u002Fmain\u002Fskills\u002Ftesting\u002Fcode-review-workflow\u002Freferences\u002Fchecklist.md",{"path":86,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Freport-template.md",5627,"https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager\u002Fblob\u002Fmain\u002Fskills\u002Ftesting\u002Fcode-review-workflow\u002Freferences\u002Freport-template.md",[90,119,140,167,193,215],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":100,"publishedAt":54},"01M6QJCB2SD5KHC41ZDQC0GA1T","meeting-minutes","Generate concise, actionable meeting minutes for internal meetings. Includes metadata, attendees, agenda, decisions, action items (owner + due date), and follow-up steps.","https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager\u002Fblob\u002Fmain\u002Fskills\u002Fwriting\u002Fmeeting-minutes\u002FSKILL.md",[96,97],{"categoryNo":26,"categoryName":27,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":98,"categoryName":99,"taxonomyType":31,"taxonomyTypeDesc":32},"01JBSEEDCAT000000000000034","行政与办公人员",[101,102,103,104,105,106,107,108,109,110,92,59,111,112,113,114,115,116,117,118],"meeting minutes","meeting","minutes","writing","github","copilot","generate","decisions","meetings","up","agenda","actionable","concise","follow-up","tree","true","action","for",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":54},"01M6QJC71RRGTGNNFEHJG6S20G","documentation-writer","Diátaxis Documentation Expert. An expert technical writer specializing in creating high-quality software documentation, guided by the principles and structure of the Diátaxis technical documentation authoring framework.","https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager\u002Fblob\u002Fmain\u002Fskills\u002Fwriting\u002Fdocumentation-writer\u002FSKILL.md",[],[126,127,128,104,105,106,129,130,131,132,133,134,59,135,136,137,138,115,116,139],"documentation","documentation writer","writer","https","quality","technical","technical writer","expert","documentation expert","structure","authoring","software","principles","high",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":153,"publishedAt":54},"01M6QJC0V3C7C4R9768J1AJYWY","doc-coauthoring","Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.","https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager\u002Fblob\u002Fmain\u002Fskills\u002Fwriting\u002Fdoc-coauthoring\u002FSKILL.md",[146,149,150],{"categoryNo":147,"categoryName":148,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":26,"categoryName":27,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":151,"categoryName":152,"taxonomyType":31,"taxonomyTypeDesc":32},"01JBSEEDCAT000000000000036","内容创作者",[154,155,104,35,156,126,157,158,159,160,161,162,59,163,164,136,165,166,115,118],"doc coauthoring","doc","official","tasks","decision","write","context","proposals","guide","refine","iteration","trigger","co",{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":171,"categories":172,"keywords":182,"publishedAt":54},"01M6QJB7XNHV3VEEQF4W7FMWF6","code-change-test-designer","Analyzes code changes and designs comprehensive test cases. Reads diffs, summarizes capability changes, and designs test cases covering main flows and edge cases. Should be used when the user mentions test coverage, designing tests for code changes, or analyzing diff\u002Fcommit for testing purposes. Distinguished from code-review-workflow which provides comprehensive review, this skill focuses on test case design for code changes.","https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager\u002Fblob\u002Fmain\u002Fskills\u002Ftesting\u002Fcode-change-test-designer\u002FSKILL.md",[173,174,177,178,179],{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":175,"categoryName":176,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":26,"categoryName":27,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":29,"categoryName":30,"taxonomyType":31,"taxonomyTypeDesc":32},{"categoryNo":180,"categoryName":181,"taxonomyType":31,"taxonomyTypeDesc":32},"01JBSEEDCAT000000000000032","设计师",[51,50,37,183,184,53,185,186,35,187,48,188,46,189,59,190,191,192,118,40],"designer","code change test designer","design","diffs","commit","edge","diff","tests","flows","which",{"skillNo":194,"name":195,"nameZh":6,"description":196,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":197,"categories":198,"keywords":200,"publishedAt":54},"01M6QJB195WD7DCJWDMKWKB29S","skill-creator","Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.","https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager\u002Fblob\u002Fmain\u002Fskills\u002Fmeta-skills\u002Fskill-creator\u002FSKILL.md",[199],{"categoryNo":26,"categoryName":27,"taxonomyType":20,"taxonomyTypeDesc":21},[201,202,203,204,156,205,206,207,208,209,39,210,211,212,59,213,214,115,118,195],"skill creator","creator","performance","run evals","variance analysis","create","run","benchmark","Meta","improve","edit","evals","optimize","existing skill",{"skillNo":216,"name":217,"nameZh":6,"description":218,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":219,"categories":220,"keywords":222,"publishedAt":54},"01M6QJAKN1XMYCZERA9CGBQPNY","enhanced-skill-creator","Enhances and optimizes existing Skills. Analyzes Skills for trigger accuracy, execution effectiveness, and coverage completeness, then provides optimization recommendations. Should be used when the user mentions optimizing, improving, refactoring, or enhancing Skills. Distinguished from creating new skills — this skill focuses on improving existing ones.","https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager\u002Fblob\u002Fmain\u002Fskills\u002Fmeta-skills\u002Fenhanced-skill-creator\u002FSKILL.md",[221],{"categoryNo":26,"categoryName":27,"taxonomyType":20,"taxonomyTypeDesc":21},[201,202,223,224,225,209,226,227,228,46,229,165,230,118,231,232],"enhanced skill creator","optimization recommendations","Optimization","execution","refactoring","user","recommendations","completeness","accuracy","Existing"]