{"id":"e4f7f2f5-6f89-4b2c-8dc8-db689474a625","entityType":"agent","slug":"clawhub-kokxi-qa-code-review-for-test","name":"qa-code-review-for-test","canonicalUrl":"https://www.xpersona.co/agent/clawhub-kokxi-qa-code-review-for-test","canonicalPath":"/agent/clawhub-kokxi-qa-code-review-for-test","generatedAt":"2026-10-11T14:13:22.051Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"editorial-content","verified":true,"confidence":"high","updatedAt":"2026-10-11T10:29:17.168Z","emptyReason":null},"description":"当开发提了 PR、代码变更需要确定测试范围、或者想通过分析代码来预测可能出 Bug 的区域时使用此技能。从测试视角分析代码变更的影响范围、识别高危模式和典型风险区域。不要看完整代码逻辑——你只需要关注变更类型（新增/修改/删除/重构）、影响范围（接口定义/数据库字段/业务逻辑）和相关依赖，据此确定最小回归测试范围。输出代码变更影响分析报告。 触发场景：代码评审、CR、测试视角、看代码、代码变更、Diff、代码变更后需要确定测试范围时。 Use when the user asks about: reviewing a PR or code diff from a testing perspective to determine regression scope and high-risk areas. Skill: qa-code-review-for-test Owner: kokxi Summary: 当开发提了 PR、代码变更需要确定测试范围、或者想通过分析代码来预测可能出 Bug 的区域时使用此技能。从测试视角分析代码变更的影响范围、识别高危模式和典型风险区域。不要看完整代码逻辑——你只需要关注变更类型（新增/修改/删除/重构）、影响范围（接口定义/数据库字段/业务逻辑）和相关依赖，据此确定最小回归测试范围。输出代码变更影响分析报告。 触发场景：代码评审、CR、测试视角、看代码、代码变更、Diff、代码变更后需要确定测试范围时。 Use when the user asks about: reviewing a PR or code diff from a testing perspective to determine regression scope and high-risk areas. Tags: lates","descriptionLabel":"Technical summary","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 1.1K downloads reported by the source. Last updated 10/11/2026.","installCommand":"clawhub skill install s170jw3s1atcj5jwhqb4r7v7eh8912kp:qa-code-review-for-test","sourceUrl":"https://clawhub.ai/kokxi/qa-code-review-for-test","homepage":"https://clawhub.ai/kokxi/skills/qa-code-review-for-test","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/kokxi/qa-code-review-for-test","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/kokxi/skills/qa-code-review-for-test","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":61,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"当开发提了 PR、代码变更需要确定测试范围、或者想通过分析代码来预测可能出 Bug 的区域时使用此技能。从测试视角分析代码变更的影响范围、识别高危模式和典型风险区域。不要看完整代码逻辑——你只需要关注变更类型（新增/修改/删除/重构）、影响范围（接口定义/数据库字段/业务逻辑）和相关依赖，据此确定最小回归测试范围。输出"},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-11T10:29:17.168Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T10:29:17.168Z","emptyReason":null},"stars":null,"forks":null,"downloads":1087,"packageName":null,"latestVersion":"1.8.0","tractionLabel":"1.1K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T10:29:17.106Z","emptyReason":null},"lastUpdatedAt":"2026-10-11T10:29:17.168Z","lastCrawledAt":"2026-10-11T10:29:17.106Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-12T10:29:17.106Z","lastVerifiedAt":null,"highlights":[{"version":"1.8.0","createdAt":"2026-09-29T04:26:02.937Z","changelog":"Version 1.8.0 - Modularized documentation: moved “测试视角CR四看” to a new reference file (references/cr-lens.md) for better context management. - Updated SKILL.md metadata to include references, clarify usage triggers, and reflect the new file structure. - Improved SKILL.md conciseness by removing duplicate content and summarizing the invocation scenarios. - Removed redundant file (skill-card.md).","fileCount":4,"zipByteSize":5342},{"version":"1.7.7","createdAt":"2026-09-27T14:33:51.741Z","changelog":"1.7.7","fileCount":3,"zipByteSize":4782},{"version":"1.7.6","createdAt":"2026-09-01T12:38:04.865Z","changelog":"显示名改中文","fileCount":3,"zipByteSize":4984},{"version":"1.7.5","createdAt":"2026-08-30T15:12:31.926Z","changelog":"1.7.5: 版本号升级","fileCount":3,"zipByteSize":4798},{"version":"1.6.3","createdAt":"2026-08-12T15:22:18.875Z","changelog":"Version 1.6.3 - 增加 slug 与 displayName 字段，完善元数据规范 - 移除多余文件 skill-card.md - 更新 version 字段为 1.6.3，修正元数据 - 其余结构与文档内容保持不变","fileCount":3,"zipByteSize":4541},{"version":"1.6.0","createdAt":"2026-07-06T17:14:48.447Z","changelog":"Version 1.6.0 - Added output traceability with unique code review IDs and requirement/PR association. - Expanded output structure to include \"high_risk_patterns\". - Enhanced related_skills with downstream \"qa-regression-testing\". - Added feature categories and quantification of review depth requirements. - Introduced error recovery guidance for missing dependency analysis. - Removed the file \"skill-card.md\" for streamlining. - Updated example warnings for better clarity and safe usage reminders.","fileCount":3,"zipByteSize":4684},{"version":"1.5.0","createdAt":"2026-06-29T12:32:06.419Z","changelog":"- Now includes explicit input/output structure: review findings, test gaps, impact analysis, regression scope. - Adds a detailed \"深度要求\" (depth guideline) table for code review based on change complexity. - Clarifies skill purpose: focus strictly on change type, affected area, and dependencies to define minimal regression scope. - Streamlines usage scenario references and adds explicit required/optional fields for input. - Removes file: skill-card.md.","fileCount":3,"zipByteSize":4017},{"version":"1.4.1","createdAt":"2026-06-25T16:53:58.396Z","changelog":"- skill-card.md 文件已移除，精简冗余内容。 - SKILL.md 文件删减描述与简介，突出精准测试建议与触发场景。 - 保留完整“CR四看法”与评审检查清单，优化表达，更简练。 - 适当调整描述，强调技能激活条件与输出聚焦测试视角。","fileCount":3,"zipByteSize":3655}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s170jw3s1atcj5jwhqb4r7v7eh8912kp:qa-code-review-for-test","setupComplexity":"low","setupSteps":["Setup complexity is classified as HIGH. You must provision dedicated cloud infrastructure or an isolated VM. Do not run this directly on your local workstation.","Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-kokxi-qa-code-review-for-test/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-kokxi-qa-code-review-for-test/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-kokxi-qa-code-review-for-test/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-kokxi-qa-code-review-for-test/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-kokxi-qa-code-review-for-test/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-kokxi-qa-code-review-for-test/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-11T14:13:22.049Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-kokxi-qa-code-review-for-test/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-kokxi-qa-code-review-for-test/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-kokxi-qa-code-review-for-test/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-kokxi-qa-code-review-for-test/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"high","updatedAt":"2026-10-11T10:29:17.168Z","emptyReason":null},"readme":"Skill: qa-code-review-for-test\n\nOwner: kokxi\n\nSummary: 当开发提了 PR、代码变更需要确定测试范围、或者想通过分析代码来预测可能出 Bug 的区域时使用此技能。从测试视角分析代码变更的影响范围、识别高危模式和典型风险区域。不要看完整代码逻辑——你只需要关注变更类型（新增/修改/删除/重构）、影响范围（接口定义/数据库字段/业务逻辑）和相关依赖，据此确定最小回归测试范围。输出代码变更影响分析报告。 触发场景：代码评审、CR、测试视角、看代码、代码变更、Diff、代码变更后需要确定测试范围时。 Use when the user asks about: reviewing a PR or code diff from a testing perspective to determine regression scope and high-risk areas.\n\nTags: latest:1.8.0\n\nVersion history:\n\nv1.8.0 | 2026-09-29T04:26:02.937Z | auto\n\nVersion 1.8.0\n\n- Modularized documentation: moved “测试视角CR四看” to a new reference file (references/cr-lens.md) for better context management.\n- Updated SKILL.md metadata to include references, clarify usage triggers, and reflect the new file structure.\n- Improved SKILL.md conciseness by removing duplicate content and summarizing the invocation scenarios.\n- Removed redundant file (skill-card.md).\n\nv1.7.7 | 2026-09-27T14:33:51.741Z | user\n\n1.7.7\n\nv1.7.6 | 2026-09-01T12:38:04.865Z | user\n\n显示名改中文\n\nv1.7.5 | 2026-08-30T15:12:31.926Z | user\n\n1.7.5: 版本号升级\n\nv1.6.3 | 2026-08-12T15:22:18.875Z | auto\n\nVersion 1.6.3\n\n- 增加 slug 与 displayName 字段，完善元数据规范\n- 移除多余文件 skill-card.md\n- 更新 version 字段为 1.6.3，修正元数据\n- 其余结构与文档内容保持不变\n\nv1.6.0 | 2026-07-06T17:14:48.447Z | auto\n\nVersion 1.6.0\n\n- Added output traceability with unique code review IDs and requirement/PR association.\n- Expanded output structure to include \"high_risk_patterns\".\n- Enhanced related_skills with downstream \"qa-regression-testing\".\n- Added feature categories and quantification of review depth requirements.\n- Introduced error recovery guidance for missing dependency analysis.\n- Removed the file \"skill-card.md\" for streamlining.\n- Updated example warnings for better clarity and safe usage reminders.\n\nv1.5.0 | 2026-06-29T12:32:06.419Z | auto\n\n- Now includes explicit input/output structure: review findings, test gaps, impact analysis, regression scope.\n- Adds a detailed \"深度要求\" (depth guideline) table for code review based on change complexity.\n- Clarifies skill purpose: focus strictly on change type, affected area, and dependencies to define minimal regression scope.\n- Streamlines usage scenario references and adds explicit required/optional fields for input.\n- Removes file: skill-card.md.\n\nv1.4.1 | 2026-06-25T16:53:58.396Z | auto\n\n- skill-card.md 文件已移除，精简冗余内容。\n- SKILL.md 文件删减描述与简介，突出精准测试建议与触发场景。\n- 保留完整“CR四看法”与评审检查清单，优化表达，更简练。\n- 适当调整描述，强调技能激活条件与输出聚焦测试视角。\n\nv1.4.0 | 2026-06-24T05:06:16.992Z | auto\n\nVersion 1.4.0\n\n- Expanded and clarified the skill description with new keywords and usage scenarios for improved discoverability.\n- Updated \"when_to_use\" with more trigger phrases, covering a broader range of test-focused code review scenarios.\n- Added an \"Examples\" section detailing practical applications of the CR四看流程.\n- Reorganized and streamlined documentation structure for better readability and user guidance.\n- Removed the skill-card.md file for simplified maintenance.\n\nv1.3.0 | 2026-06-21T15:37:55.419Z | auto\n\n- 全面更新文档，明确了“测试视角的代码评审”技能的定位与使用场景。\n- 明确输入（git diff、边界分析、风险评估）与输出（测试视角CR报告）格式。\n- 补充“测试视角CR四看”分析框架，细化影响范围、风险模式与测试建议。\n- 增加详细的检查清单和验收流程，方便实际评审操作。\n- 完善相关上下游技能关联及代码读取权限说明。\n\nArchive index:\n\nArchive v1.8.0: 4 files, 5342 bytes\n\nFiles: references/cr-lens.md (2193b), skill-card.md (1662b), SKILL.md (5797b), _meta.json (142b)\n\nFile v1.8.0:SKILL.md\n\n---\nname: qa-code-review-for-test\ndescription: >-\n  当开发提了 PR、代码变更需要确定测试范围、或者想通过分析代码来预测可能出 Bug 的区域时使用此技能。从测试视角分析代码变更的影响范围、识别高危模式和典型风险区域。不要看完整代码逻辑——你只需要关注变更类型（新增/修改/删除/重构）、影响范围（接口定义/数据库字段/业务逻辑）和相关依赖，据此确定最小回归测试范围。输出代码变更影响分析报告。 触发场景：代码评审、CR、测试视角、看代码、代码变更、Diff、代码变更后需要确定测试范围时。 Use when the user asks about: reviewing a PR or code diff from a testing perspective to determine regression scope and high-risk areas.\nlicense: MIT\nallowed-tools: Read Grep Glob Bash\nmetadata:\n  display-name: \"Code Review For Test\"\n  version: \"1.8.0\"\n  when-to-use: \"用户说\\\"代码评审\\\"、\\\"CR\\\"、\\\"测试视角\\\"、\\\"看代码\\\"、\\\"代码变更\\\"、\\\"Diff\\\"、需要从测试角度分析代码变更、代码变更后需要确定测试范围时\"\n  related-skills: \"{\\\"upstream\\\":[\\\"qa-boundary-deep-dive\\\",\\\"qa-risk-intuition\\\"],\\\"downstream\\\":[\\\"qa-execution-observation\\\",\\\"qa-test-strategy-design\\\",\\\"qa-regression-testing\\\"]}\"\n  references: \"[\\\"references/cr-lens.md\\\"]\"\n  input-format: \"{\\\"required\\\":[{\\\"name\\\":\\\"代码变更\\\",\\\"type\\\":\\\"string\\\",\\\"description\\\":\\\"代码变更的diff或描述\\\"},{\\\"name\\\":\\\"测试用例\\\",\\\"type\\\":\\\"array\\\",\\\"description\\\":\\\"相关测试用例列表\\\"}],\\\"optional\\\":[{\\\"name\\\":\\\"需求文档\\\",\\\"type\\\":\\\"string\\\",\\\"description\\\":\\\"相关功能需求\\\"}]}\"\n  output-format: \"{\\\"traceability\\\":[\\\"每次代码评审带唯一ID（CR-XXXX）\\\",\\\"关联变更ID或需求ID\\\"],\\\"structure\\\":[\\\"覆盖率：标注口径（基于现有需求/输入文档），禁止\\\\\\\"全覆盖/100%\\\\\\\"绝对化表述；缺失模块标注\\\\\\\"未覆盖+原因\\\\\\\"\\\",{\\\"review_findings\\\":\\\"代码评审发现\\\"},{\\\"test_gaps\\\":\\\"测试遗漏点\\\"},{\\\"impact_analysis\\\":\\\"变更影响分析\\\"},{\\\"high_risk_patterns\\\":\\\"高危模式识别\\\"},{\\\"regression_scope\\\":\\\"回归测试范围建议\\\"}]}\"\n  error-recovery-guidance: \"{\\\"on_failure\\\":\\\"代码变更分析遗漏依赖时回退到边界分析补充\\\",\\\"retry_behavior\\\":\\\"补全依赖分析后重新确定回归范围\\\"}\"\n  categories: \"[\\\"Development\\\",\\\"Team\\\"]\"\n  depth-requirement: \"{\\\"reference_value\\\":\\\"根据代码变更量调整评审深度：简单×1/中等×2/复杂×3\\\",\\\"minimum\\\":\\\"至少分析变更类型、影响范围、回归范围3个维度\\\"}\"\n---\n> ⚠️ 本技能单独使用效果有限，建议配合完整技能集（12 步工作流）使用。安装：npx skills add Kokxi/qa-test-skills\n\n> **⚠️ 安全警告**：本技能的示例可能涉及代码变更分析（新增/修改/删除/重构）。\n> 实际使用时请勿直接基于评审结论修改源码，先与开发确认变更范围和回归风险。\n> 本技能仅在 workspace/ 输出评估文件，不持久化、不外传、不跨会话复用。\n\n# 测试视角的代码评审\n\n## 核心原则\n\n看代码不是为了Review代码质量，而是判断变更影响范围、识别需要重点回归的区域。\n\n> **代码读取许可**：本技能需要读取代码变更（git diff）进行分析，仅关注测试影响，不评估代码质量。\n\n## 深度要求（参考值）\n\n**关键指标**：根据代码变更复杂度调整CR深度\n\n| 复杂度 | CR检查点要求 | 说明 |\n|--------|-------------|------|\n| 简单变更 | 5-8个检查点 | 单文件/配置/文案变更 |\n| 中等变更 | 12-20个检查点 | 多文件/逻辑修改 |\n| 复杂变更 | 25-40个检查点 | 重构/重写/核心模块变更 |\n\n## 加载时机\n\n| 什么时候读 | 读哪个 |\n|-----------|--------|\n| 从测试角度评审代码变更时 | [`references/cr-lens.md`](references/cr-lens.md) |\n\n> `测试视角CR四看`的完整内容已下沉至 `references/cr-lens.md`，避免每次触发都占用上下文。\n\n## 代码评审检查清单\n\n### 功能变更检查\n- [ ] 业务逻辑是否正确？\n- [ ] 边界条件是否处理？\n- [ ] 异常处理是否完善？\n- [ ] 数据校验是否完整？\n\n### 数据变更检查\n- [ ] 数据库变更是否兼容？\n- [ ] 数据迁移是否安全？\n- [ ] 索引变更是否影响性能？\n- [ ] 数据一致性是否保证？\n\n### 接口变更检查\n- [ ] 接口入参是否兼容？\n- [ ] 接口出参是否变化？\n- [ ] 错误码是否变化？\n- [ ] 文档是否更新？\n\n### 配置变更检查\n- [ ] 配置项是否新增？\n- [ ] 默认值是否合理？\n- [ ] 环境差异是否考虑？\n- [ ] 回滚方案是否准备？\n\n### 性能变更检查\n- [ ] 是否有性能影响？\n- [ ] 是否有内存泄漏风险？\n- [ ] 是否有并发问题？\n- [ ] 是否有资源竞争？\n\n## 应用场景\n\n**开发提交了登录模块的代码变更**\n→ CR四看分析：\n  - 看diff：修改了LoginController.java，新增密码加密逻辑\n  - 看影响：影响登录流程、密码验证、Session创建\n  - 看风险模式：加密算法变更可能导致兼容性问题\n  - 看测试建议：回归登录成功/失败流程，新增加密算法兼容性测试\n\n**配置项变更（数据库连接池大小调整）**\n→ 影响范围评估：确定需要回归的接口和场景\n\n## 自检清单\n\n代码评审完成后检查：\n- [ ] 是否分析了diff内容？\n- [ ] 是否评估了影响范围？\n- [ ] 是否识别了风险模式？\n- [ ] 是否给出了测试建议？\n- [ ] 建议是否可执行？\n\n\n## 检查清单\n\n- [ ] 变更类型是否识别？\n- [ ] 影响范围是否分析？\n- [ ] 高风险模式是否标注？\n- [ ] 回归范围是否建议？\n- [ ] 可测试性问题是否提出？\n\nFile v1.8.0:_meta.json\n\n{\n  \"ownerId\": \"kn71y9b23csfx0ykgm55d5m9x5891zt8\",\n  \"slug\": \"qa-code-review-for-test\",\n  \"version\": \"1.8.0\",\n  \"publishedAt\": 1790655962937\n}\n\nFile v1.8.0:references/cr-lens.md\n\n# 测试视角 CR 四看详解\n\n> 本文是 `qa-code-review-for-test` 的**测试视角 CR 四看详解**。从测试角度评审代码变更时读本文；\n其余部分留在 SKILL.md，不必读本文。\n\n---\n\n\n### 第1看：看diff（改了什么）\n\n```text\n分析维度：\n├─ 新增文件：新增了哪些文件？\n├─ 修改文件：修改了哪些文件？\n├─ 删除文件：删除了哪些文件？\n├─ 代码行数：新增/修改/删除多少行？\n└─ 变更类型：功能/修复/重构/配置？\n\n关注点：\n- 核心逻辑变更\n- 数据库变更\n- 配置变更\n- 接口变更\n```\n\n### 第2看：看影响（波及哪里）\n\n```text\n分析维度：\n├─ 调用方：哪些地方调用了这个方法？\n├─ 数据流向：数据从哪来、到哪去？\n├─ 接口变更：对外接口有没有变？\n├─ 数据库变更：表结构/索引有没有变？\n└─ 配置变更：配置项有没有变？\n\n关注点：\n- 影响范围评估\n- 需要回归的区域\n- 需要新增的测试场景\n```\n\n### 第3看：看风险模式（有什么风险）\n\n```text\n风险模式识别：\n├─ 静态数据变化：硬编码的值变了\n├─ 超时/重试：涉及超时或重试逻辑\n├─ 异常吞没：异常被catch但没处理\n├─ 并发处理：涉及多线程/分布式锁\n├─ 状态管理：涉及状态变更\n├─ 权限控制：涉及认证/授权\n├─ 数据转换：涉及格式/类型转换\n└─ 外部依赖：涉及第三方服务\n\n关注点：\n- 每个风险模式对应的测试场景\n- 需要重点验证的区域\n```\n\n### 第4看：看测试建议（怎么测）\n\n```text\n测试建议输出：\n├─ 回归测试：哪些功能需要回归？\n├─ 新增测试：需要新增哪些测试场景？\n├─ 重点测试：哪些区域需要深测？\n├─ 性能测试：是否需要性能测试？\n└─ 安全测试：是否需要安全测试？\n\n输出格式：\n[变更描述]\n├─ 影响范围：[影响的功能/模块]\n├─ 回归范围：[需要回归的功能]\n├─ 新增场景：[需要新增的测试场景]\n├─ 重点区域：[需要深测的区域]\n└─ 测试建议：[具体的测试建议]\n```\n\nFile v1.8.0:skill-card.md\n\n## Description:\n\nReviews code changes from a testing perspective to identify affected areas, high-risk patterns, and a focused regression test scope.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[kokxi](https://clawhub.ai/user/kokxi)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers and testers use this skill to review pull requests or diffs for change impact, test gaps, and targeted regression scenarios.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The optional installation command fetches an unpinned package.\n\nMitigation: Only install from a trusted source, or pin and verify the package first.\n\nRisk: The review reads repository diffs and related code, which may contain sensitive information.\n\nMitigation: Limit access to the intended repository and avoid sharing sensitive code in review outputs.\n\n## Reference(s):\n\n- [Testing-focused code review lens](references/cr-lens.md)\n- [ClawHub skill release](https://clawhub.ai/kokxi/skills/qa-code-review-for-test)\n\n## Skill Output:\n\n**Output Type(s):** [Analysis, Guidance]\n\n**Output Format:** [Markdown]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Includes review findings, test gaps, impact analysis, risk patterns, and a regression scope with a review ID.]\n\n## Skill Version(s):\n\n1.8.0 (source: skill frontmatter and ClawHub release)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.7.7: 3 files, 4782 bytes\n\nFiles: skill-card.md (1907b), SKILL.md (7449b), _meta.json (142b)\n\nFile v1.7.7:SKILL.md\n\n---\nname: qa-code-review-for-test\nslug: qa-code-review-for-test\ndisplayName: Code Review For Test\nversion: 1.7.7\ndescription: >-\n  当开发提了 PR、代码变更需要确定测试范围、或者想通过分析代码来预测可能出 Bug 的区域时使用此技能。从测试视角分析代码变更的影响范围、识别高危模式和典型风险区域。不要看完整代码逻辑——你只需要关注变更类型（新增/修改/删除/重构）、影响范围（接口定义/数据库字段/业务逻辑）和相关依赖，据此确定最小回归测试范围。输出代码变更影响分析报告。\n\nwhen_to_use: 用户说\"代码评审\"、\"CR\"、\"测试视角\"、\"看代码\"、\"代码变更\"、\"Diff\"、需要从测试角度分析代码变更、代码变更后需要确定测试范围时\nallowed-tools: Read Grep Glob Bash\nrelated_skills:\n  upstream:\n    - qa-boundary-deep-dive      # 输入：边界分析识别风险区域\n    - qa-risk-intuition          # 输入：风险评估识别高风险区域\n  downstream:\n    - qa-execution-observation   # 输出：代码变更指导执行观察\n    - qa-test-strategy-design    # 输出：代码变更影响测试策略\n    - qa-regression-testing\ninput_format:\n  required:\n    - name: 代码变更\n      type: string\n      description: 代码变更的diff或描述\n    - name: 测试用例\n      type: array\n      description: 相关测试用例列表\n  optional:\n    - name: 需求文档\n      type: string\n      description: 相关功能需求\noutput_format:\n  traceability:\n    - 每次代码评审带唯一ID（CR-XXXX）\n    - 关联变更ID或需求ID\n  structure:\n    - 测试用例表格：固定 9 列（用例编号|测试类型|功能模块|测试标题|用例级别|预置条件|测试步骤|预期结果|风险等级）\n    - 用例级别：P0≤20%（核心流程）/ P1≤40%（主要功能）/ P2≤30%（次要功能）/ P3≤10%（边缘场景）\n    - 覆盖率：标注口径（基于现有需求/输入文档），禁止\"全覆盖/100%\"绝对化表述；缺失模块标注\"未覆盖+原因\"\n    - review_findings: 代码评审发现\n    - test_gaps: 测试遗漏点\n    - impact_analysis: 变更影响分析\n    - high_risk_patterns: 高危模式识别\n    - regression_scope: 回归测试范围建议\ncategories: ['Development','Team']\ndepth_requirement_quantification:\n  reference_value: \"根据代码变更量调整评审深度：简单×1/中等×2/复杂×3\"\n  minimum: \"至少分析变更类型、影响范围、回归范围3个维度\"\nerror_recovery_guidance:\n  on_failure: \"代码变更分析遗漏依赖时回退到边界分析补充\"\n  retry_behavior: \"补全依赖分析后重新确定回归范围\"\n---\n> **⚠️ 安全警告**：本技能的示例可能涉及代码变更分析（新增/修改/删除/重构）。\n> 实际使用时请勿直接基于评审结论修改源码，先与开发确认变更范围和回归风险。\n> 本技能仅在 workspace/ 输出评估文件，不持久化、不外传、不跨会话复用。\n\n# 测试视角的代码评审\n\n## 核心原则\n\n看代码不是为了Review代码质量，而是判断变更影响范围、识别需要重点回归的区域。\n\n> **代码读取许可**：本技能需要读取代码变更（git diff）进行分析，仅关注测试影响，不评估代码质量。\n\n## 深度要求（参考值）\n\n**关键指标**：根据代码变更复杂度调整CR深度\n\n| 复杂度 | CR检查点要求 | 说明 |\n|--------|-------------|------|\n| 简单变更 | 5-8个检查点 | 单文件/配置/文案变更 |\n| 中等变更 | 12-20个检查点 | 多文件/逻辑修改 |\n| 复杂变更 | 25-40个检查点 | 重构/重写/核心模块变更 |\n\n## 测试视角CR四看\n\n### 第1看：看diff（改了什么）\n\n```text\n分析维度：\n├─ 新增文件：新增了哪些文件？\n├─ 修改文件：修改了哪些文件？\n├─ 删除文件：删除了哪些文件？\n├─ 代码行数：新增/修改/删除多少行？\n└─ 变更类型：功能/修复/重构/配置？\n\n关注点：\n- 核心逻辑变更\n- 数据库变更\n- 配置变更\n- 接口变更\n```\n\n### 第2看：看影响（波及哪里）\n\n```text\n分析维度：\n├─ 调用方：哪些地方调用了这个方法？\n├─ 数据流向：数据从哪来、到哪去？\n├─ 接口变更：对外接口有没有变？\n├─ 数据库变更：表结构/索引有没有变？\n└─ 配置变更：配置项有没有变？\n\n关注点：\n- 影响范围评估\n- 需要回归的区域\n- 需要新增的测试场景\n```\n\n### 第3看：看风险模式（有什么风险）\n\n```text\n风险模式识别：\n├─ 静态数据变化：硬编码的值变了\n├─ 超时/重试：涉及超时或重试逻辑\n├─ 异常吞没：异常被catch但没处理\n├─ 并发处理：涉及多线程/分布式锁\n├─ 状态管理：涉及状态变更\n├─ 权限控制：涉及认证/授权\n├─ 数据转换：涉及格式/类型转换\n└─ 外部依赖：涉及第三方服务\n\n关注点：\n- 每个风险模式对应的测试场景\n- 需要重点验证的区域\n```\n\n### 第4看：看测试建议（怎么测）\n\n```text\n测试建议输出：\n├─ 回归测试：哪些功能需要回归？\n├─ 新增测试：需要新增哪些测试场景？\n├─ 重点测试：哪些区域需要深测？\n├─ 性能测试：是否需要性能测试？\n└─ 安全测试：是否需要安全测试？\n\n输出格式：\n[变更描述]\n├─ 影响范围：[影响的功能/模块]\n├─ 回归范围：[需要回归的功能]\n├─ 新增场景：[需要新增的测试场景]\n├─ 重点区域：[需要深测的区域]\n└─ 测试建议：[具体的测试建议]\n```\n\n## 代码评审检查清单\n\n### 功能变更检查\n- [ ] 业务逻辑是否正确？\n- [ ] 边界条件是否处理？\n- [ ] 异常处理是否完善？\n- [ ] 数据校验是否完整？\n\n### 数据变更检查\n- [ ] 数据库变更是否兼容？\n- [ ] 数据迁移是否安全？\n- [ ] 索引变更是否影响性能？\n- [ ] 数据一致性是否保证？\n\n### 接口变更检查\n- [ ] 接口入参是否兼容？\n- [ ] 接口出参是否变化？\n- [ ] 错误码是否变化？\n- [ ] 文档是否更新？\n\n### 配置变更检查\n- [ ] 配置项是否新增？\n- [ ] 默认值是否合理？\n- [ ] 环境差异是否考虑？\n- [ ] 回滚方案是否准备？\n\n### 性能变更检查\n- [ ] 是否有性能影响？\n- [ ] 是否有内存泄漏风险？\n- [ ] 是否有并发问题？\n- [ ] 是否有资源竞争？\n\n## 应用场景\n\n**开发提交了登录模块的代码变更**\n→ CR四看分析：\n  - 看diff：修改了LoginController.java，新增密码加密逻辑\n  - 看影响：影响登录流程、密码验证、Session创建\n  - 看风险模式：加密算法变更可能导致兼容性问题\n  - 看测试建议：回归登录成功/失败流程，新增加密算法兼容性测试\n\n**配置项变更（数据库连接池大小调整）**\n→ 影响范围评估：确定需要回归的接口和场景\n\n## 自检清单\n\n代码评审完成后检查：\n- [ ] 是否分析了diff内容？\n- [ ] 是否评估了影响范围？\n- [ ] 是否识别了风险模式？\n- [ ] 是否给出了测试建议？\n- [ ] 建议是否可执行？\n\n\n## 检查清单\n\n- [ ] 变更类型是否识别？\n- [ ] 影响范围是否分析？\n- [ ] 高风险模式是否标注？\n- [ ] 回归范围是否建议？\n- [ ] 可测试性问题是否提出？\n\nFile v1.7.7:_meta.json\n\n{\n  \"ownerId\": \"kn71y9b23csfx0ykgm55d5m9x5891zt8\",\n  \"slug\": \"qa-code-review-for-test\",\n  \"version\": \"1.7.7\",\n  \"publishedAt\": 1790519631741\n}\n\nFile v1.7.7:skill-card.md\n\n## Description:\n\nAnalyzes code changes from a testing perspective to identify affected areas, high-risk patterns, and a focused regression testing scope.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[kokxi](https://clawhub.ai/user/kokxi)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers and QA engineers use this skill to review code diffs, identify change-related test gaps, and plan targeted regression testing rather than assess overall code quality.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Broad review requests can invoke testing-focused analysis when a full engineering code review is intended.\n\nMitigation: Specify whether the request calls for test-scope analysis or a full engineering review.\n\nRisk: A mistaken impact assessment can omit dependencies or narrow regression coverage incorrectly.\n\nMitigation: Check affected callers and dependencies, disclose uncovered areas, and confirm the change scope and regression risks with developers before acting on recommendations.\n\n## Reference(s):\n\n- [ClawHub skill release](https://clawhub.ai/kokxi/skills/qa-code-review-for-test)\n\n## Skill Output:\n\n**Output Type(s):** [Markdown, Guidance]\n\n**Output Format:** [Markdown code-change impact analysis report with a nine-column test case table]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Includes review findings, test gaps, high-risk patterns, regression scope, and a review ID; coverage claims must state their basis and identify uncovered modules.]\n\n## Skill Version(s):\n\n1.7.7 (source: release metadata and skill frontmatter)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.7.6: 3 files, 4984 bytes\n\nFiles: skill-card.md (1993b), SKILL.md (7954b), _meta.json (142b)\n\nFile v1.7.6:SKILL.md\n\n---\r\nname: qa-code-review-for-test\r\nslug: qa-code-review-for-test\r\ndisplayName: 测试视角代码评审\r\nversion: 1.7.5\r\ndescription: >-\r\n  当开发提了 PR、代码变更需要确定测试范围、或者想通过分析代码来预测可能出 Bug 的区域时使用此技能。从测试视角分析代码变更的影响范围、识别高危模式和典型风险区域。不要看完整代码逻辑——你只需要关注变更类型（新增/修改/删除/重构）、影响范围（接口定义/数据库字段/业务逻辑）和相关依赖，据此确定最小回归测试范围。输出代码变更影响分析报告。\r\n  本技能属于 QA Test Skills 技能集（49 个技能之一），完整工作流体验需安装全套：npx skills add Kokxi/qa-test-skills\r\n\r\nwhen_to_use: 用户说\"代码评审\"、\"CR\"、\"测试视角\"、\"看代码\"、\"代码变更\"、\"Diff\"、需要从测试角度分析代码变更、代码变更后需要确定测试范围时\r\nallowed-tools: Read Grep Glob Bash\r\nrelated_skills:\r\n  upstream:\r\n    - qa-boundary-deep-dive      # 输入：边界分析识别风险区域\r\n    - qa-risk-intuition          # 输入：风险评估识别高风险区域\r\n  downstream:\r\n    - qa-execution-observation   # 输出：代码变更指导执行观察\r\n    - qa-test-strategy-design    # 输出：代码变更影响测试策略\r\n    - qa-regression-testing\r\ninput_format:\r\n  required:\r\n    - name: 代码变更\r\n      type: string\r\n      description: 代码变更的diff或描述\r\n    - name: 测试用例\r\n      type: array\r\n      description: 相关测试用例列表\r\n  optional:\r\n    - name: 需求文档\r\n      type: string\r\n      description: 相关功能需求\r\noutput_format:\r\n  traceability:\r\n    - 每次代码评审带唯一ID（CR-XXXX）\r\n    - 关联变更ID或需求ID\r\n  structure:\r\n    - 测试用例表格：固定 9 列（用例编号|测试类型|功能模块|测试标题|用例级别|预置条件|测试步骤|预期结果|风险等级）\r\n    - 用例级别：P0≤20%（核心流程）/ P1≤40%（主要功能）/ P2≤30%（次要功能）/ P3≤10%（边缘场景）\r\n    - 覆盖率：标注口径（基于现有需求/输入文档），禁止\"全覆盖/100%\"绝对化表述；缺失模块标注\"未覆盖+原因\"\r\n    - review_findings: 代码评审发现\r\n    - test_gaps: 测试遗漏点\r\n    - impact_analysis: 变更影响分析\r\n    - high_risk_patterns: 高危模式识别\r\n    - regression_scope: 回归测试范围建议\r\ncategories: ['Development','Team']\r\ndepth_requirement_quantification:\r\n  reference_value: \"根据代码变更量调整评审深度：简单×1/中等×2/复杂×3\"\r\n  minimum: \"至少分析变更类型、影响范围、回归范围3个维度\"\r\nerror_recovery_guidance:\r\n  on_failure: \"代码变更分析遗漏依赖时回退到边界分析补充\"\r\n  retry_behavior: \"补全依赖分析后重新确定回归范围\"\r\n---\r\n> ⚠️ 本技能单独使用效果有限，建议配合完整技能集（12 步工作流）使用。安装：npx skills add Kokxi/qa-test-skills\r\n\r\n> **⚠️ 安全警告**：本技能的示例可能涉及代码变更分析（新增/修改/删除/重构）。\r\n> 实际使用时请勿直接基于评审结论修改源码，先与开发确认变更范围和回归风险。\r\n> 本技能仅在 workspace/ 输出评估文件，不持久化、不外传、不跨会话复用。\r\n\r\n# 测试视角的代码评审\r\n\r\n## 核心原则\r\n\r\n看代码不是为了Review代码质量，而是判断变更影响范围、识别需要重点回归的区域。\r\n\r\n> **代码读取许可**：本技能需要读取代码变更（git diff）进行分析，仅关注测试影响，不评估代码质量。\r\n\r\n## 深度要求（参考值）\r\n\r\n**关键指标**：根据代码变更复杂度调整CR深度\r\n\r\n| 复杂度 | CR检查点要求 | 说明 |\r\n|--------|-------------|------|\r\n| 简单变更 | 5-8个检查点 | 单文件/配置/文案变更 |\r\n| 中等变更 | 12-20个检查点 | 多文件/逻辑修改 |\r\n| 复杂变更 | 25-40个检查点 | 重构/重写/核心模块变更 |\r\n\r\n## 测试视角CR四看\r\n\r\n### 第1看：看diff（改了什么）\r\n\r\n```text\r\n分析维度：\r\n├─ 新增文件：新增了哪些文件？\r\n├─ 修改文件：修改了哪些文件？\r\n├─ 删除文件：删除了哪些文件？\r\n├─ 代码行数：新增/修改/删除多少行？\r\n└─ 变更类型：功能/修复/重构/配置？\r\n\r\n关注点：\r\n- 核心逻辑变更\r\n- 数据库变更\r\n- 配置变更\r\n- 接口变更\r\n```\r\n\r\n### 第2看：看影响（波及哪里）\r\n\r\n```text\r\n分析维度：\r\n├─ 调用方：哪些地方调用了这个方法？\r\n├─ 数据流向：数据从哪来、到哪去？\r\n├─ 接口变更：对外接口有没有变？\r\n├─ 数据库变更：表结构/索引有没有变？\r\n└─ 配置变更：配置项有没有变？\r\n\r\n关注点：\r\n- 影响范围评估\r\n- 需要回归的区域\r\n- 需要新增的测试场景\r\n```\r\n\r\n### 第3看：看风险模式（有什么风险）\r\n\r\n```text\r\n风险模式识别：\r\n├─ 静态数据变化：硬编码的值变了\r\n├─ 超时/重试：涉及超时或重试逻辑\r\n├─ 异常吞没：异常被catch但没处理\r\n├─ 并发处理：涉及多线程/分布式锁\r\n├─ 状态管理：涉及状态变更\r\n├─ 权限控制：涉及认证/授权\r\n├─ 数据转换：涉及格式/类型转换\r\n└─ 外部依赖：涉及第三方服务\r\n\r\n关注点：\r\n- 每个风险模式对应的测试场景\r\n- 需要重点验证的区域\r\n```\r\n\r\n### 第4看：看测试建议（怎么测）\r\n\r\n```text\r\n测试建议输出：\r\n├─ 回归测试：哪些功能需要回归？\r\n├─ 新增测试：需要新增哪些测试场景？\r\n├─ 重点测试：哪些区域需要深测？\r\n├─ 性能测试：是否需要性能测试？\r\n└─ 安全测试：是否需要安全测试？\r\n\r\n输出格式：\r\n[变更描述]\r\n├─ 影响范围：[影响的功能/模块]\r\n├─ 回归范围：[需要回归的功能]\r\n├─ 新增场景：[需要新增的测试场景]\r\n├─ 重点区域：[需要深测的区域]\r\n└─ 测试建议：[具体的测试建议]\r\n```\r\n\r\n## 代码评审检查清单\r\n\r\n### 功能变更检查\r\n- [ ] 业务逻辑是否正确？\r\n- [ ] 边界条件是否处理？\r\n- [ ] 异常处理是否完善？\r\n- [ ] 数据校验是否完整？\r\n\r\n### 数据变更检查\r\n- [ ] 数据库变更是否兼容？\r\n- [ ] 数据迁移是否安全？\r\n- [ ] 索引变更是否影响性能？\r\n- [ ] 数据一致性是否保证？\r\n\r\n### 接口变更检查\r\n- [ ] 接口入参是否兼容？\r\n- [ ] 接口出参是否变化？\r\n- [ ] 错误码是否变化？\r\n- [ ] 文档是否更新？\r\n\r\n### 配置变更检查\r\n- [ ] 配置项是否新增？\r\n- [ ] 默认值是否合理？\r\n- [ ] 环境差异是否考虑？\r\n- [ ] 回滚方案是否准备？\r\n\r\n### 性能变更检查\r\n- [ ] 是否有性能影响？\r\n- [ ] 是否有内存泄漏风险？\r\n- [ ] 是否有并发问题？\r\n- [ ] 是否有资源竞争？\r\n\r\n## 应用场景\r\n\r\n**开发提交了登录模块的代码变更**\r\n→ CR四看分析：\r\n  - 看diff：修改了LoginController.java，新增密码加密逻辑\r\n  - 看影响：影响登录流程、密码验证、Session创建\r\n  - 看风险模式：加密算法变更可能导致兼容性问题\r\n  - 看测试建议：回归登录成功/失败流程，新增加密算法兼容性测试\r\n\r\n**配置项变更（数据库连接池大小调整）**\r\n→ 影响范围评估：确定需要回归的接口和场景\r\n\r\n## 自检清单\r\n\r\n代码评审完成后检查：\r\n- [ ] 是否分析了diff内容？\r\n- [ ] 是否评估了影响范围？\r\n- [ ] 是否识别了风险模式？\r\n- [ ] 是否给出了测试建议？\r\n- [ ] 建议是否可执行？\r\n\r\n\r\n## 检查清单\r\n\r\n- [ ] 变更类型是否识别？\r\n- [ ] 影响范围是否分析？\r\n- [ ] 高风险模式是否标注？\r\n- [ ] 回归范围是否建议？\r\n- [ ] 可测试性问题是否提出？\n\nFile v1.7.6:_meta.json\n\n{\n  \"ownerId\": \"kn71y9b23csfx0ykgm55d5m9x5891zt8\",\n  \"slug\": \"qa-code-review-for-test\",\n  \"version\": \"1.7.6\",\n  \"publishedAt\": 1788266284865\n}\n\nFile v1.7.6:skill-card.md\n\n## Description:\n\nThis skill helps QA reviewers analyze code changes from a testing perspective, identify impact areas and high-risk patterns, and define a focused regression test scope.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[kokxi](https://clawhub.ai/user/kokxi)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nQA engineers, developers, and release reviewers use this skill when a pull request or code diff needs test-impact analysis. It produces practical guidance on changed areas, dependency impact, risk patterns, test gaps, and the minimum regression scope.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill recommends an unpinned command that can install a larger third-party skill collection and affect future agent behavior.\n\nMitigation: Verify the package source and pin a trusted version or commit before running `npx skills add Kokxi/qa-test-skills`.\n\nRisk: The skill reads repository code and diffs to perform QA review.\n\nMitigation: Use it only in repositories where code-reading by a third-party skill is acceptable, and review its conclusions before acting on them.\n\n## Reference(s):\n\n- [ClawHub skill page](https://clawhub.ai/kokxi/skills/qa-code-review-for-test)\n- [ClawHub publisher profile](https://clawhub.ai/user/kokxi)\n\n## Skill Output:\n\n**Output Type(s):** [text, markdown, guidance]\n\n**Output Format:** [Markdown analysis report with tables and structured sections]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May include review findings, test gaps, impact analysis, high-risk patterns, regression scope, and prioritized test cases.]\n\n## Skill Version(s):\n\n1.7.6 (source: server release metadata)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.7.5: 3 files, 4798 bytes\n\nFiles: skill-card.md (1970b), SKILL.md (7449b), _meta.json (142b)\n\nFile v1.7.5:SKILL.md\n\n---\nname: qa-code-review-for-test\nslug: qa-code-review-for-test\ndisplayName: Code Review For Test\nversion: 1.7.5\ndescription: >-\n  当开发提了 PR、代码变更需要确定测试范围、或者想通过分析代码来预测可能出 Bug 的区域时使用此技能。从测试视角分析代码变更的影响范围、识别高危模式和典型风险区域。不要看完整代码逻辑——你只需要关注变更类型（新增/修改/删除/重构）、影响范围（接口定义/数据库字段/业务逻辑）和相关依赖，据此确定最小回归测试范围。输出代码变更影响分析报告。\n\nwhen_to_use: 用户说\"代码评审\"、\"CR\"、\"测试视角\"、\"看代码\"、\"代码变更\"、\"Diff\"、需要从测试角度分析代码变更、代码变更后需要确定测试范围时\nallowed-tools: Read Grep Glob Bash\nrelated_skills:\n  upstream:\n    - qa-boundary-deep-dive      # 输入：边界分析识别风险区域\n    - qa-risk-intuition          # 输入：风险评估识别高风险区域\n  downstream:\n    - qa-execution-observation   # 输出：代码变更指导执行观察\n    - qa-test-strategy-design    # 输出：代码变更影响测试策略\n    - qa-regression-testing\ninput_format:\n  required:\n    - name: 代码变更\n      type: string\n      description: 代码变更的diff或描述\n    - name: 测试用例\n      type: array\n      description: 相关测试用例列表\n  optional:\n    - name: 需求文档\n      type: string\n      description: 相关功能需求\noutput_format:\n  traceability:\n    - 每次代码评审带唯一ID（CR-XXXX）\n    - 关联变更ID或需求ID\n  structure:\n    - 测试用例表格：固定 9 列（用例编号|测试类型|功能模块|测试标题|用例级别|预置条件|测试步骤|预期结果|风险等级）\n    - 用例级别：P0≤20%（核心流程）/ P1≤40%（主要功能）/ P2≤30%（次要功能）/ P3≤10%（边缘场景）\n    - 覆盖率：标注口径（基于现有需求/输入文档），禁止\"全覆盖/100%\"绝对化表述；缺失模块标注\"未覆盖+原因\"\n    - review_findings: 代码评审发现\n    - test_gaps: 测试遗漏点\n    - impact_analysis: 变更影响分析\n    - high_risk_patterns: 高危模式识别\n    - regression_scope: 回归测试范围建议\ncategories: ['Development','Team']\ndepth_requirement_quantification:\n  reference_value: \"根据代码变更量调整评审深度：简单×1/中等×2/复杂×3\"\n  minimum: \"至少分析变更类型、影响范围、回归范围3个维度\"\nerror_recovery_guidance:\n  on_failure: \"代码变更分析遗漏依赖时回退到边界分析补充\"\n  retry_behavior: \"补全依赖分析后重新确定回归范围\"\n---\n> **⚠️ 安全警告**：本技能的示例可能涉及代码变更分析（新增/修改/删除/重构）。\n> 实际使用时请勿直接基于评审结论修改源码，先与开发确认变更范围和回归风险。\n> 本技能仅在 workspace/ 输出评估文件，不持久化、不外传、不跨会话复用。\n\n# 测试视角的代码评审\n\n## 核心原则\n\n看代码不是为了Review代码质量，而是判断变更影响范围、识别需要重点回归的区域。\n\n> **代码读取许可**：本技能需要读取代码变更（git diff）进行分析，仅关注测试影响，不评估代码质量。\n\n## 深度要求（参考值）\n\n**关键指标**：根据代码变更复杂度调整CR深度\n\n| 复杂度 | CR检查点要求 | 说明 |\n|--------|-------------|------|\n| 简单变更 | 5-8个检查点 | 单文件/配置/文案变更 |\n| 中等变更 | 12-20个检查点 | 多文件/逻辑修改 |\n| 复杂变更 | 25-40个检查点 | 重构/重写/核心模块变更 |\n\n## 测试视角CR四看\n\n### 第1看：看diff（改了什么）\n\n```text\n分析维度：\n├─ 新增文件：新增了哪些文件？\n├─ 修改文件：修改了哪些文件？\n├─ 删除文件：删除了哪些文件？\n├─ 代码行数：新增/修改/删除多少行？\n└─ 变更类型：功能/修复/重构/配置？\n\n关注点：\n- 核心逻辑变更\n- 数据库变更\n- 配置变更\n- 接口变更\n```\n\n### 第2看：看影响（波及哪里）\n\n```text\n分析维度：\n├─ 调用方：哪些地方调用了这个方法？\n├─ 数据流向：数据从哪来、到哪去？\n├─ 接口变更：对外接口有没有变？\n├─ 数据库变更：表结构/索引有没有变？\n└─ 配置变更：配置项有没有变？\n\n关注点：\n- 影响范围评估\n- 需要回归的区域\n- 需要新增的测试场景\n```\n\n### 第3看：看风险模式（有什么风险）\n\n```text\n风险模式识别：\n├─ 静态数据变化：硬编码的值变了\n├─ 超时/重试：涉及超时或重试逻辑\n├─ 异常吞没：异常被catch但没处理\n├─ 并发处理：涉及多线程/分布式锁\n├─ 状态管理：涉及状态变更\n├─ 权限控制：涉及认证/授权\n├─ 数据转换：涉及格式/类型转换\n└─ 外部依赖：涉及第三方服务\n\n关注点：\n- 每个风险模式对应的测试场景\n- 需要重点验证的区域\n```\n\n### 第4看：看测试建议（怎么测）\n\n```text\n测试建议输出：\n├─ 回归测试：哪些功能需要回归？\n├─ 新增测试：需要新增哪些测试场景？\n├─ 重点测试：哪些区域需要深测？\n├─ 性能测试：是否需要性能测试？\n└─ 安全测试：是否需要安全测试？\n\n输出格式：\n[变更描述]\n├─ 影响范围：[影响的功能/模块]\n├─ 回归范围：[需要回归的功能]\n├─ 新增场景：[需要新增的测试场景]\n├─ 重点区域：[需要深测的区域]\n└─ 测试建议：[具体的测试建议]\n```\n\n## 代码评审检查清单\n\n### 功能变更检查\n- [ ] 业务逻辑是否正确？\n- [ ] 边界条件是否处理？\n- [ ] 异常处理是否完善？\n- [ ] 数据校验是否完整？\n\n### 数据变更检查\n- [ ] 数据库变更是否兼容？\n- [ ] 数据迁移是否安全？\n- [ ] 索引变更是否影响性能？\n- [ ] 数据一致性是否保证？\n\n### 接口变更检查\n- [ ] 接口入参是否兼容？\n- [ ] 接口出参是否变化？\n- [ ] 错误码是否变化？\n- [ ] 文档是否更新？\n\n### 配置变更检查\n- [ ] 配置项是否新增？\n- [ ] 默认值是否合理？\n- [ ] 环境差异是否考虑？\n- [ ] 回滚方案是否准备？\n\n### 性能变更检查\n- [ ] 是否有性能影响？\n- [ ] 是否有内存泄漏风险？\n- [ ] 是否有并发问题？\n- [ ] 是否有资源竞争？\n\n## 应用场景\n\n**开发提交了登录模块的代码变更**\n→ CR四看分析：\n  - 看diff：修改了LoginController.java，新增密码加密逻辑\n  - 看影响：影响登录流程、密码验证、Session创建\n  - 看风险模式：加密算法变更可能导致兼容性问题\n  - 看测试建议：回归登录成功/失败流程，新增加密算法兼容性测试\n\n**配置项变更（数据库连接池大小调整）**\n→ 影响范围评估：确定需要回归的接口和场景\n\n## 自检清单\n\n代码评审完成后检查：\n- [ ] 是否分析了diff内容？\n- [ ] 是否评估了影响范围？\n- [ ] 是否识别了风险模式？\n- [ ] 是否给出了测试建议？\n- [ ] 建议是否可执行？\n\n\n## 检查清单\n\n- [ ] 变更类型是否识别？\n- [ ] 影响范围是否分析？\n- [ ] 高风险模式是否标注？\n- [ ] 回归范围是否建议？\n- [ ] 可测试性问题是否提出？\n\nFile v1.7.5:_meta.json\n\n{\n  \"ownerId\": \"kn71y9b23csfx0ykgm55d5m9x5891zt8\",\n  \"slug\": \"qa-code-review-for-test\",\n  \"version\": \"1.7.5\",\n  \"publishedAt\": 1788102751926\n}\n\nFile v1.7.5:skill-card.md\n\n## Description:\n\nAnalyzes code changes from a testing perspective to identify affected areas, high-risk patterns, test gaps, and a minimal regression testing scope.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[kokxi](https://clawhub.ai/user/kokxi)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers, QA engineers, and test leads use this skill to review diffs or change descriptions, estimate test impact, identify risky change patterns, and plan focused regression coverage.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Broad activation wording may invoke the skill during ordinary code-review discussions or against unrelated repository content.\n\nMitigation: Limit use to intended diffs, change descriptions, requirements, and relevant test cases; keep sensitive repositories and unrelated files out of scope.\n\nRisk: The impact analysis and regression recommendations may be incomplete or misleading if dependencies or change scope are missing.\n\nMitigation: Confirm the change scope and regression risk with developers before using the conclusions to guide testing or source changes.\n\n## Reference(s):\n\n\n## Skill Output:\n\n**Output Type(s):** [analysis, markdown, guidance]\n\n**Output Format:** [Markdown report with test case tables, review findings, test gaps, impact analysis, high-risk patterns, and regression scope recommendations.]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Uses a CR traceability identifier and risk-ranked test recommendations; no external provenance references are available for this release.]\n\n## Skill Version(s):\n\n1.7.5 (source: frontmatter and server release evidence)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.6.3: 3 files, 4541 bytes\n\nFiles: skill-card.md (1986b), SKILL.md (7008b), _meta.json (142b)\n\nFile v1.6.3:SKILL.md\n\n---\nname: qa-code-review-for-test\nslug: qa-code-review-for-test\ndisplayName: Code Review For Test\nversion: 1.6.3\ndescription: >-\n  当开发提了 PR、代码变更需要确定测试范围、或者想通过分析代码来预测可能出 Bug 的区域时使用此技能。从测试视角分析代码变更的影响范围、识别高危模式和典型风险区域。不要看完整代码逻辑——你只需要关注变更类型（新增/修改/删除/重构）、影响范围（接口定义/数据库字段/业务逻辑）和相关依赖，据此确定最小回归测试范围。输出代码变更影响分析报告。\n\nwhen_to_use: 用户说\"代码评审\"、\"CR\"、\"测试视角\"、\"看代码\"、\"代码变更\"、\"Diff\"、需要从测试角度分析代码变更、代码变更后需要确定测试范围时\nallowed-tools: Read Grep Glob Bash\nrelated_skills:\n  upstream:\n    - qa-boundary-deep-dive      # 输入：边界分析识别风险区域\n    - qa-risk-intuition          # 输入：风险评估识别高风险区域\n  downstream:\n    - qa-execution-observation   # 输出：代码变更指导执行观察\n    - qa-test-strategy-design    # 输出：代码变更影响测试策略\n    - qa-regression-testing\ninput_format:\n  required:\n    - name: 代码变更\n      type: string\n      description: 代码变更的diff或描述\n    - name: 测试用例\n      type: array\n      description: 相关测试用例列表\n  optional:\n    - name: 需求文档\n      type: string\n      description: 相关功能需求\noutput_format:\n  traceability:\n    - 每次代码评审带唯一ID（CR-XXXX）\n    - 关联变更ID或需求ID\n  structure:\n    - review_findings: 代码评审发现\n    - test_gaps: 测试遗漏点\n    - impact_analysis: 变更影响分析\n    - high_risk_patterns: 高危模式识别\n    - regression_scope: 回归测试范围建议\ncategories: ['Development','Team']\ndepth_requirement_quantification:\n  reference_value: \"根据代码变更量调整评审深度：简单×1/中等×2/复杂×3\"\n  minimum: \"至少分析变更类型、影响范围、回归范围3个维度\"\nerror_recovery_guidance:\n  on_failure: \"代码变更分析遗漏依赖时回退到边界分析补充\"\n  retry_behavior: \"补全依赖分析后重新确定回归范围\"\n---\n> **⚠️ 安全警告**：本技能的示例可能涉及代码变更分析（新增/修改/删除/重构）。\n> 实际使用时请勿直接基于评审结论修改源码，先与开发确认变更范围和回归风险。\n> 本技能仅在 workspace/ 输出评估文件，不持久化、不外传、不跨会话复用。\n\n# 测试视角的代码评审\n\n## 核心原则\n\n看代码不是为了Review代码质量，而是判断变更影响范围、识别需要重点回归的区域。\n\n> **代码读取许可**：本技能需要读取代码变更（git diff）进行分析，仅关注测试影响，不评估代码质量。\n\n## 深度要求（参考值）\n\n**关键指标**：根据代码变更复杂度调整CR深度\n\n| 复杂度 | CR检查点要求 | 说明 |\n|--------|-------------|------|\n| 简单变更 | 5-8个检查点 | 单文件/配置/文案变更 |\n| 中等变更 | 12-20个检查点 | 多文件/逻辑修改 |\n| 复杂变更 | 25-40个检查点 | 重构/重写/核心模块变更 |\n\n## 测试视角CR四看\n\n### 第1看：看diff（改了什么）\n\n```text\n分析维度：\n├─ 新增文件：新增了哪些文件？\n├─ 修改文件：修改了哪些文件？\n├─ 删除文件：删除了哪些文件？\n├─ 代码行数：新增/修改/删除多少行？\n└─ 变更类型：功能/修复/重构/配置？\n\n关注点：\n- 核心逻辑变更\n- 数据库变更\n- 配置变更\n- 接口变更\n```\n\n### 第2看：看影响（波及哪里）\n\n```text\n分析维度：\n├─ 调用方：哪些地方调用了这个方法？\n├─ 数据流向：数据从哪来、到哪去？\n├─ 接口变更：对外接口有没有变？\n├─ 数据库变更：表结构/索引有没有变？\n└─ 配置变更：配置项有没有变？\n\n关注点：\n- 影响范围评估\n- 需要回归的区域\n- 需要新增的测试场景\n```\n\n### 第3看：看风险模式（有什么风险）\n\n```text\n风险模式识别：\n├─ 静态数据变化：硬编码的值变了\n├─ 超时/重试：涉及超时或重试逻辑\n├─ 异常吞没：异常被catch但没处理\n├─ 并发处理：涉及多线程/分布式锁\n├─ 状态管理：涉及状态变更\n├─ 权限控制：涉及认证/授权\n├─ 数据转换：涉及格式/类型转换\n└─ 外部依赖：涉及第三方服务\n\n关注点：\n- 每个风险模式对应的测试场景\n- 需要重点验证的区域\n```\n\n### 第4看：看测试建议（怎么测）\n\n```text\n测试建议输出：\n├─ 回归测试：哪些功能需要回归？\n├─ 新增测试：需要新增哪些测试场景？\n├─ 重点测试：哪些区域需要深测？\n├─ 性能测试：是否需要性能测试？\n└─ 安全测试：是否需要安全测试？\n\n输出格式：\n[变更描述]\n├─ 影响范围：[影响的功能/模块]\n├─ 回归范围：[需要回归的功能]\n├─ 新增场景：[需要新增的测试场景]\n├─ 重点区域：[需要深测的区域]\n└─ 测试建议：[具体的测试建议]\n```\n\n## 代码评审检查清单\n\n### 功能变更检查\n- [ ] 业务逻辑是否正确？\n- [ ] 边界条件是否处理？\n- [ ] 异常处理是否完善？\n- [ ] 数据校验是否完整？\n\n### 数据变更检查\n- [ ] 数据库变更是否兼容？\n- [ ] 数据迁移是否安全？\n- [ ] 索引变更是否影响性能？\n- [ ] 数据一致性是否保证？\n\n### 接口变更检查\n- [ ] 接口入参是否兼容？\n- [ ] 接口出参是否变化？\n- [ ] 错误码是否变化？\n- [ ] 文档是否更新？\n\n### 配置变更检查\n- [ ] 配置项是否新增？\n- [ ] 默认值是否合理？\n- [ ] 环境差异是否考虑？\n- [ ] 回滚方案是否准备？\n\n### 性能变更检查\n- [ ] 是否有性能影响？\n- [ ] 是否有内存泄漏风险？\n- [ ] 是否有并发问题？\n- [ ] 是否有资源竞争？\n\n## 应用场景\n\n**开发提交了登录模块的代码变更**\n→ CR四看分析：\n  - 看diff：修改了LoginController.java，新增密码加密逻辑\n  - 看影响：影响登录流程、密码验证、Session创建\n  - 看风险模式：加密算法变更可能导致兼容性问题\n  - 看测试建议：回归登录成功/失败流程，新增加密算法兼容性测试\n\n**配置项变更（数据库连接池大小调整）**\n→ 影响范围评估：确定需要回归的接口和场景\n\n## 自检清单\n\n代码评审完成后检查：\n- [ ] 是否分析了diff内容？\n- [ ] 是否评估了影响范围？\n- [ ] 是否识别了风险模式？\n- [ ] 是否给出了测试建议？\n- [ ] 建议是否可执行？\n\n\n## 检查清单\n\n- [ ] 变更类型是否识别？\n- [ ] 影响范围是否分析？\n- [ ] 高风险模式是否标注？\n- [ ] 回归范围是否建议？\n- [ ] 可测试性问题是否提出？\n\nFile v1.6.3:_meta.json\n\n{\n  \"ownerId\": \"kn71y9b23csfx0ykgm55d5m9x5891zt8\",\n  \"slug\": \"qa-code-review-for-test\",\n  \"version\": \"1.6.3\",\n  \"publishedAt\": 1786548138875\n}\n\nFile v1.6.3:skill-card.md\n\n## Description:\n\nHelps developers and QA engineers review code changes from a testing perspective, identify impact areas and high-risk patterns, and define a minimal regression test scope.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[kokxi](https://clawhub.ai/user/kokxi)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers, QA engineers, and test leads use this skill when a PR, diff, or described code change needs test-impact analysis. It focuses on changed files, affected interfaces, data or configuration changes, high-risk patterns, and practical regression scope recommendations.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill reads code changes and diffs to analyze test impact.\n\nMitigation: Use it only in workspaces where code and diff review for QA purposes is acceptable.\n\nRisk: Broad trigger phrases may match ordinary developer conversations.\n\nMitigation: Invoke it explicitly for PR or diff test-impact analysis when that behavior is intended.\n\nRisk: Test-impact recommendations may be incomplete or misleading if the provided diff or context omits dependencies.\n\nMitigation: Review the recommendations with developers and supplement with dependency or boundary analysis before relying on the regression scope.\n\n## Reference(s):\n\n\n## Skill Output:\n\n**Output Type(s):** [Analysis, Markdown, Guidance]\n\n**Output Format:** [Markdown test-impact analysis report]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Outputs review findings, test gaps, impact analysis, high-risk patterns, and regression scope recommendations.]\n\n## Skill Version(s):\n\n1.6.3 (source: frontmatter and server release evidence)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.6.0: 3 files, 4684 bytes\n\nFiles: skill-card.md (2346b), SKILL.md (7145b), _meta.json (142b)\n\nFile v1.6.0:SKILL.md\n\n---\r\nname: qa-code-review-for-test\r\nversion: 1.6.0\r\ndescription: >-\r\n  当开发提了 PR、代码变更需要确定测试范围、或者想通过分析代码来预测可能出 Bug 的区域时使用此技能。从测试视角分析代码变更的影响范围、识别高危模式和典型风险区域。不要看完整代码逻辑——你只需要关注变更类型（新增/修改/删除/重构）、影响范围（接口定义/数据库字段/业务逻辑）和相关依赖，据此确定最小回归测试范围。输出代码变更影响分析报告。\r\n\r\nwhen_to_use: 用户说\"代码评审\"、\"CR\"、\"测试视角\"、\"看代码\"、\"代码变更\"、\"Diff\"、需要从测试角度分析代码变更、代码变更后需要确定测试范围时\r\nallowed-tools: Read Grep Glob Bash\r\nrelated_skills:\r\n  upstream:\r\n    - qa-boundary-deep-dive      # 输入：边界分析识别风险区域\r\n    - qa-risk-intuition          # 输入：风险评估识别高风险区域\r\n  downstream:\r\n    - qa-execution-observation   # 输出：代码变更指导执行观察\r\n    - qa-test-strategy-design    # 输出：代码变更影响测试策略\r\n    - qa-regression-testing\r\ninput_format:\r\n  required:\r\n    - name: 代码变更\r\n      type: string\r\n      description: 代码变更的diff或描述\r\n    - name: 测试用例\r\n      type: array\r\n      description: 相关测试用例列表\r\n  optional:\r\n    - name: 需求文档\r\n      type: string\r\n      description: 相关功能需求\r\noutput_format:\r\n  traceability:\r\n    - 每次代码评审带唯一ID（CR-XXXX）\r\n    - 关联变更ID或需求ID\r\n  structure:\r\n    - review_findings: 代码评审发现\r\n    - test_gaps: 测试遗漏点\r\n    - impact_analysis: 变更影响分析\r\n    - high_risk_patterns: 高危模式识别\r\n    - regression_scope: 回归测试范围建议\r\ncategories: ['Development','Team']\r\ndepth_requirement_quantification:\r\n  reference_value: \"根据代码变更量调整评审深度：简单×1/中等×2/复杂×3\"\r\n  minimum: \"至少分析变更类型、影响范围、回归范围3个维度\"\r\nerror_recovery_guidance:\r\n  on_failure: \"代码变更分析遗漏依赖时回退到边界分析补充\"\r\n  retry_behavior: \"补全依赖分析后重新确定回归范围\"\r\n---\r\n> **⚠️ 安全警告**：本技能的示例可能涉及代码变更分析（新增/修改/删除/重构）。\r\n> 实际使用时请勿直接基于评审结论修改源码，先与开发确认变更范围和回归风险。\r\n> 本技能仅在 workspace/ 输出评估文件，不持久化、不外传、不跨会话复用。\r\n\r\n# 测试视角的代码评审\r\n\r\n## 核心原则\r\n\r\n看代码不是为了Review代码质量，而是判断变更影响范围、识别需要重点回归的区域。\r\n\r\n> **代码读取许可**：本技能需要读取代码变更（git diff）进行分析，仅关注测试影响，不评估代码质量。\r\n\r\n## 深度要求（参考值）\r\n\r\n**关键指标**：根据代码变更复杂度调整CR深度\r\n\r\n| 复杂度 | CR检查点要求 | 说明 |\r\n|--------|-------------|------|\r\n| 简单变更 | 5-8个检查点 | 单文件/配置/文案变更 |\r\n| 中等变更 | 12-20个检查点 | 多文件/逻辑修改 |\r\n| 复杂变更 | 25-40个检查点 | 重构/重写/核心模块变更 |\r\n\r\n## 测试视角CR四看\r\n\r\n### 第1看：看diff（改了什么）\r\n\r\n```text\r\n分析维度：\r\n├─ 新增文件：新增了哪些文件？\r\n├─ 修改文件：修改了哪些文件？\r\n├─ 删除文件：删除了哪些文件？\r\n├─ 代码行数：新增/修改/删除多少行？\r\n└─ 变更类型：功能/修复/重构/配置？\r\n\r\n关注点：\r\n- 核心逻辑变更\r\n- 数据库变更\r\n- 配置变更\r\n- 接口变更\r\n```\r\n\r\n### 第2看：看影响（波及哪里）\r\n\r\n```text\r\n分析维度：\r\n├─ 调用方：哪些地方调用了这个方法？\r\n├─ 数据流向：数据从哪来、到哪去？\r\n├─ 接口变更：对外接口有没有变？\r\n├─ 数据库变更：表结构/索引有没有变？\r\n└─ 配置变更：配置项有没有变？\r\n\r\n关注点：\r\n- 影响范围评估\r\n- 需要回归的区域\r\n- 需要新增的测试场景\r\n```\r\n\r\n### 第3看：看风险模式（有什么风险）\r\n\r\n```text\r\n风险模式识别：\r\n├─ 静态数据变化：硬编码的值变了\r\n├─ 超时/重试：涉及超时或重试逻辑\r\n├─ 异常吞没：异常被catch但没处理\r\n├─ 并发处理：涉及多线程/分布式锁\r\n├─ 状态管理：涉及状态变更\r\n├─ 权限控制：涉及认证/授权\r\n├─ 数据转换：涉及格式/类型转换\r\n└─ 外部依赖：涉及第三方服务\r\n\r\n关注点：\r\n- 每个风险模式对应的测试场景\r\n- 需要重点验证的区域\r\n```\r\n\r\n### 第4看：看测试建议（怎么测）\r\n\r\n```text\r\n测试建议输出：\r\n├─ 回归测试：哪些功能需要回归？\r\n├─ 新增测试：需要新增哪些测试场景？\r\n├─ 重点测试：哪些区域需要深测？\r\n├─ 性能测试：是否需要性能测试？\r\n└─ 安全测试：是否需要安全测试？\r\n\r\n输出格式：\r\n[变更描述]\r\n├─ 影响范围：[影响的功能/模块]\r\n├─ 回归范围：[需要回归的功能]\r\n├─ 新增场景：[需要新增的测试场景]\r\n├─ 重点区域：[需要深测的区域]\r\n└─ 测试建议：[具体的测试建议]\r\n```\r\n\r\n## 代码评审检查清单\r\n\r\n### 功能变更检查\r\n- [ ] 业务逻辑是否正确？\r\n- [ ] 边界条件是否处理？\r\n- [ ] 异常处理是否完善？\r\n- [ ] 数据校验是否完整？\r\n\r\n### 数据变更检查\r\n- [ ] 数据库变更是否兼容？\r\n- [ ] 数据迁移是否安全？\r\n- [ ] 索引变更是否影响性能？\r\n- [ ] 数据一致性是否保证？\r\n\r\n### 接口变更检查\r\n- [ ] 接口入参是否兼容？\r\n- [ ] 接口出参是否变化？\r\n- [ ] 错误码是否变化？\r\n- [ ] 文档是否更新？\r\n\r\n### 配置变更检查\r\n- [ ] 配置项是否新增？\r\n- [ ] 默认值是否合理？\r\n- [ ] 环境差异是否考虑？\r\n- [ ] 回滚方案是否准备？\r\n\r\n### 性能变更检查\r\n- [ ] 是否有性能影响？\r\n- [ ] 是否有内存泄漏风险？\r\n- [ ] 是否有并发问题？\r\n- [ ] 是否有资源竞争？\r\n\r\n## 应用场景\r\n\r\n**开发提交了登录模块的代码变更**\r\n→ CR四看分析：\r\n  - 看diff：修改了LoginController.java，新增密码加密逻辑\r\n  - 看影响：影响登录流程、密码验证、Session创建\r\n  - 看风险模式：加密算法变更可能导致兼容性问题\r\n  - 看测试建议：回归登录成功/失败流程，新增加密算法兼容性测试\r\n\r\n**配置项变更（数据库连接池大小调整）**\r\n→ 影响范围评估：确定需要回归的接口和场景\r\n\r\n## 自检清单\r\n\r\n代码评审完成后检查：\r\n- [ ] 是否分析了diff内容？\r\n- [ ] 是否评估了影响范围？\r\n- [ ] 是否识别了风险模式？\r\n- [ ] 是否给出了测试建议？\r\n- [ ] 建议是否可执行？\r\n\r\n\r\n## 检查清单\r\n\r\n- [ ] 变更类型是否识别？\r\n- [ ] 影响范围是否分析？\r\n- [ ] 高风险模式是否标注？\r\n- [ ] 回归范围是否建议？\r\n- [ ] 可测试性问题是否提出？\n\nFile v1.6.0:_meta.json\n\n{\n  \"ownerId\": \"kn71y9b23csfx0ykgm55d5m9x5891zt8\",\n  \"slug\": \"qa-code-review-for-test\",\n  \"version\": \"1.6.0\",\n  \"publishedAt\": 1783358088447\n}\n\nFile v1.6.0:skill-card.md\n\n## Description: <br>\nProvides Chinese-language QA review guidance for code changes, focusing on change impact, high-risk patterns, test gaps, and the minimum regression test scope. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[kokxi](https://clawhub.ai/user/kokxi) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nQA engineers, developers, and test leads use this skill after pull requests or code changes to identify affected areas, likely defect zones, missing tests, and focused regression coverage. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: The skill may activate on broad code review prompts and can read workspace code while assessing test impact. <br>\nMitigation: Use it only in repositories where QA review access to code changes is appropriate. <br>\nRisk: Review findings may be incomplete or misleading if dependency impact is missed. <br>\nMitigation: Confirm the change scope and regression risk with the development team, and supplement with boundary analysis when dependency coverage is uncertain. <br>\nRisk: Users may treat the review report as direct implementation guidance. <br>\nMitigation: Use the report to plan testing and review coverage; do not modify source code solely from the report without developer confirmation. <br>\n\n\n## Reference(s): <br>\n- [ClawHub skill page](https://clawhub.ai/kokxi/skills/qa-code-review-for-test) <br>\n- [Publisher profile](https://clawhub.ai/user/kokxi) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [text, markdown, guidance] <br>\n**Output Format:** [Markdown report with structured review findings, test gaps, impact analysis, high-risk patterns, and regression scope recommendations.] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Uses traceability identifiers for each code review and links findings to a change or requirement identifier when available.] <br>\n\n## Skill Version(s): <br>\n1.6.0 (source: SKILL.md frontmatter and server release metadata) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.5.0: 3 files, 4017 bytes\n\nFiles: skill-card.md (1803b), SKILL.md (6223b), _meta.json (142b)\n\nFile v1.5.0:SKILL.md\n\n---\r\nname: qa-code-review-for-test\r\nversion: 1.5.0\r\ndescription: >-\r\n  当开发提了 PR、代码变更需要确定测试范围、或者想通过分析代码来预测可能出 Bug 的区域时使用此技能。从测试视角分析代码变更的影响范围、识别高危模式和典型风险区域。不要看完整代码逻辑——你只需要关注变更类型（新增/修改/删除/重构）、影响范围（接口定义/数据库字段/业务逻辑）和相关依赖，据此确定最小回归测试范围。输出代码变更影响分析报告。\r\n\r\nwhen_to_use: 用户说\"代码评审\"、\"CR\"、\"测试视角\"、\"看代码\"、\"代码变更\"、\"Diff\"、需要从测试角度分析代码变更、代码变更后需要确定测试范围时\r\nallowed-tools: Read Grep Glob Bash\r\nrelated_skills:\r\n  upstream:\r\n    - qa-boundary-deep-dive      # 输入：边界分析识别风险区域\r\n    - qa-risk-intuition          # 输入：风险评估识别高风险区域\r\n  downstream:\r\n    - qa-execution-observation   # 输出：代码变更指导执行观察\r\n    - qa-test-strategy-design    # 输出：代码变更影响测试策略\r\ninput_format:\r\n  required:\r\n    - name: 代码变更\r\n      type: string\r\n      description: 代码变更的diff或描述\r\n    - name: 测试用例\r\n      type: array\r\n      description: 相关测试用例列表\r\n  optional:\r\n    - name: 需求文档\r\n      type: string\r\n      description: 相关功能需求\r\noutput_format:\r\n  structure:\r\n    - review_findings: 代码评审发现\r\n    - test_gaps: 测试遗漏点\r\n    - impact_analysis: 变更影响分析\r\n    - regression_scope: 回归测试范围建议\r\n---\r\n\r\n# 测试视角的代码评审\r\n\r\n## 核心原则\r\n\r\n你是一位测试视角的代码评审专家，擅长从测试角度分析代码变更。\r\n**核心原则**：看代码不是为了Review代码质量，而是判断变更影响范围、识别需要重点回归的区域。\r\n本技能提供CR四看法（看diff/看影响/看风险模式/看测试建议）。\r\n\r\n> **代码读取许可**：本技能需要读取代码变更（git diff）进行分析，仅关注测试影响，不评估代码质量。\r\n\r\n## 深度要求（参考值）\r\n\r\n**关键指标**：根据代码变更复杂度调整CR深度\r\n\r\n| 复杂度 | CR检查点要求 | 说明 |\r\n|--------|-------------|------|\r\n| 简单变更 | 5-8个检查点 | 单文件/配置/文案变更 |\r\n| 中等变更 | 12-20个检查点 | 多文件/逻辑修改 |\r\n| 复杂变更 | 25-40个检查点 | 重构/重写/核心模块变更 |\r\n\r\n## 测试视角CR四看\r\n\r\n### 第1看：看diff（改了什么）\r\n\r\n```text\r\n分析维度：\r\n├─ 新增文件：新增了哪些文件？\r\n├─ 修改文件：修改了哪些文件？\r\n├─ 删除文件：删除了哪些文件？\r\n├─ 代码行数：新增/修改/删除多少行？\r\n└─ 变更类型：功能/修复/重构/配置？\r\n\r\n关注点：\r\n- 核心逻辑变更\r\n- 数据库变更\r\n- 配置变更\r\n- 接口变更\r\n```\r\n\r\n### 第2看：看影响（波及哪里）\r\n\r\n```text\r\n分析维度：\r\n├─ 调用方：哪些地方调用了这个方法？\r\n├─ 数据流向：数据从哪来、到哪去？\r\n├─ 接口变更：对外接口有没有变？\r\n├─ 数据库变更：表结构/索引有没有变？\r\n└─ 配置变更：配置项有没有变？\r\n\r\n关注点：\r\n- 影响范围评估\r\n- 需要回归的区域\r\n- 需要新增的测试场景\r\n```\r\n\r\n### 第3看：看风险模式（有什么风险）\r\n\r\n```text\r\n风险模式识别：\r\n├─ 静态数据变化：硬编码的值变了\r\n├─ 超时/重试：涉及超时或重试逻辑\r\n├─ 异常吞没：异常被catch但没处理\r\n├─ 并发处理：涉及多线程/分布式锁\r\n├─ 状态管理：涉及状态变更\r\n├─ 权限控制：涉及认证/授权\r\n├─ 数据转换：涉及格式/类型转换\r\n└─ 外部依赖：涉及第三方服务\r\n\r\n关注点：\r\n- 每个风险模式对应的测试场景\r\n- 需要重点验证的区域\r\n```\r\n\r\n### 第4看：看测试建议（怎么测）\r\n\r\n```text\r\n测试建议输出：\r\n├─ 回归测试：哪些功能需要回归？\r\n├─ 新增测试：需要新增哪些测试场景？\r\n├─ 重点测试：哪些区域需要深测？\r\n├─ 性能测试：是否需要性能测试？\r\n└─ 安全测试：是否需要安全测试？\r\n\r\n输出格式：\r\n[变更描述]\r\n├─ 影响范围：[影响的功能/模块]\r\n├─ 回归范围：[需要回归的功能]\r\n├─ 新增场景：[需要新增的测试场景]\r\n├─ 重点区域：[需要深测的区域]\r\n└─ 测试建议：[具体的测试建议]\r\n```\r\n\r\n## 代码评审检查清单\r\n\r\n### 功能变更检查\r\n- [ ] 业务逻辑是否正确？\r\n- [ ] 边界条件是否处理？\r\n- [ ] 异常处理是否完善？\r\n- [ ] 数据校验是否完整？\r\n\r\n### 数据变更检查\r\n- [ ] 数据库变更是否兼容？\r\n- [ ] 数据迁移是否安全？\r\n- [ ] 索引变更是否影响性能？\r\n- [ ] 数据一致性是否保证？\r\n\r\n### 接口变更检查\r\n- [ ] 接口入参是否兼容？\r\n- [ ] 接口出参是否变化？\r\n- [ ] 错误码是否变化？\r\n- [ ] 文档是否更新？\r\n\r\n### 配置变更检查\r\n- [ ] 配置项是否新增？\r\n- [ ] 默认值是否合理？\r\n- [ ] 环境差异是否考虑？\r\n- [ ] 回滚方案是否准备？\r\n\r\n### 性能变更检查\r\n- [ ] 是否有性能影响？\r\n- [ ] 是否有内存泄漏风险？\r\n- [ ] 是否有并发问题？\r\n- [ ] 是否有资源竞争？\r\n\r\n## 应用场景\r\n\r\n**开发提交了登录模块的代码变更**\r\n→ CR四看分析：\r\n  - 看diff：修改了LoginController.java，新增密码加密逻辑\r\n  - 看影响：影响登录流程、密码验证、Session创建\r\n  - 看风险模式：加密算法变更可能导致兼容性问题\r\n  - 看测试建议：回归登录成功/失败流程，新增加密算法兼容性测试\r\n\r\n**配置项变更（数据库连接池大小调整）**\r\n→ 影响范围评估：确定需要回归的接口和场景\r\n\r\n## 自检清单\r\n\r\n代码评审完成后检查：\r\n- [ ] 是否分析了diff内容？\r\n- [ ] 是否评估了影响范围？\r\n- [ ] 是否识别了风险模式？\r\n- [ ] 是否给出了测试建议？\r\n- [ ] 建议是否可执行？\n\nFile v1.5.0:_meta.json\n\n{\n  \"ownerId\": \"kn71y9b23csfx0ykgm55d5m9x5891zt8\",\n  \"slug\": \"qa-code-review-for-test\",\n  \"version\": \"1.5.0\",\n  \"publishedAt\": 1782736326419\n}\n\nFile v1.5.0:skill-card.md\n\n## Description: <br>\nAnalyzes code changes from a testing perspective to identify impact scope, high-risk patterns, test gaps, and a minimal regression testing scope. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[kokxi](https://clawhub.ai/user/kokxi) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nDevelopers, QA engineers, and reviewers use this skill when a pull request or code diff needs test-focused impact analysis. It helps identify affected areas, missing tests, risk patterns, and regression coverage without performing a full code-quality review. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: The skill may activate on broad code-review wording and produce guidance that is too general for the specific change. <br>\nMitigation: Use clear prompts that include the code diff, related test cases, and the desired testing perspective, then review the generated recommendations before applying them. <br>\n\n\n## Reference(s): <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [Analysis, Guidance, Markdown] <br>\n**Output Format:** [Markdown report with structured review findings, test gaps, impact analysis, and regression scope] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Requires a code diff or change description and related test cases; a requirements document is optional.] <br>\n\n## Skill Version(s): <br>\n1.5.0 (source: frontmatter and server release evidence) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.4.1: 3 files, 3655 bytes\n\nFiles: skill-card.md (2109b), SKILL.md (5127b), _meta.json (142b)\n\nFile v1.4.1:SKILL.md\n\n---\r\nname: qa-code-review-for-test\r\ndescription: >-\r\n  测试视角的代码评审，分析代码变更的影响范围和风险模式，输出精准测试建议。当需要从测试视角做CR或评估变更影响时激活。\r\n\r\nwhen_to_use: 用户说\"代码评审\"、\"CR\"、\"测试视角\"、\"看代码\"、\"代码变更\"、\"Diff\"、需要从测试角度分析代码变更、代码变更后需要确定测试范围时\r\nallowed-tools: Read Grep Glob Bash\r\nrelated_skills:\r\n  upstream:\r\n    - qa-boundary-deep-dive      # 输入：边界分析识别风险区域\r\n    - qa-risk-intuition          # 输入：风险评估识别高风险区域\r\n  downstream:\r\n    - qa-execution-observation   # 输出：代码变更指导执行观察\r\n    - qa-test-strategy-design    # 输出：代码变更影响测试策略\r\ninput_format: 代码变更（git diff）+ 边界分析 + 风险评估\r\noutput_format: 测试视角CR报告（影响范围+风险模式+测试建议）\r\n---\r\n\r\n# 测试视角的代码评审\r\n\r\n## Overview\r\n\r\n你是一位测试视角的代码评审专家，擅长从测试角度分析代码变更。\r\n**核心原则**：看代码不是为了Review代码质量，而是判断变更影响范围、识别需要重点回归的区域。\r\n本技能提供CR四看法（看diff/看影响/看风险模式/看测试建议）。\r\n\r\n> **代码读取许可**：本技能需要读取代码变更（git diff）进行分析，仅关注测试影响，不评估代码质量。\r\n\r\n## 测试视角CR四看\r\n\r\n### 第1看：看diff（改了什么）\r\n\r\n```\r\n分析维度：\r\n├─ 新增文件：新增了哪些文件？\r\n├─ 修改文件：修改了哪些文件？\r\n├─ 删除文件：删除了哪些文件？\r\n├─ 代码行数：新增/修改/删除多少行？\r\n└─ 变更类型：功能/修复/重构/配置？\r\n\r\n关注点：\r\n- 核心逻辑变更\r\n- 数据库变更\r\n- 配置变更\r\n- 接口变更\r\n```\r\n\r\n### 第2看：看影响（波及哪里）\r\n\r\n```\r\n分析维度：\r\n├─ 调用方：哪些地方调用了这个方法？\r\n├─ 数据流向：数据从哪来、到哪去？\r\n├─ 接口变更：对外接口有没有变？\r\n├─ 数据库变更：表结构/索引有没有变？\r\n└─ 配置变更：配置项有没有变？\r\n\r\n关注点：\r\n- 影响范围评估\r\n- 需要回归的区域\r\n- 需要新增的测试场景\r\n```\r\n\r\n### 第3看：看风险模式（有什么风险）\r\n\r\n```\r\n风险模式识别：\r\n├─ 静态数据变化：硬编码的值变了\r\n├─ 超时/重试：涉及超时或重试逻辑\r\n├─ 异常吞没：异常被catch但没处理\r\n├─ 并发处理：涉及多线程/分布式锁\r\n├─ 状态管理：涉及状态变更\r\n├─ 权限控制：涉及认证/授权\r\n├─ 数据转换：涉及格式/类型转换\r\n└─ 外部依赖：涉及第三方服务\r\n\r\n关注点：\r\n- 每个风险模式对应的测试场景\r\n- 需要重点验证的区域\r\n```\r\n\r\n### 第4看：看测试建议（怎么测）\r\n\r\n```\r\n测试建议输出：\r\n├─ 回归测试：哪些功能需要回归？\r\n├─ 新增测试：需要新增哪些测试场景？\r\n├─ 重点测试：哪些区域需要深测？\r\n├─ 性能测试：是否需要性能测试？\r\n└─ 安全测试：是否需要安全测试？\r\n\r\n输出格式：\r\n[变更描述]\r\n├─ 影响范围：[影响的功能/模块]\r\n├─ 回归范围：[需要回归的功能]\r\n├─ 新增场景：[需要新增的测试场景]\r\n├─ 重点区域：[需要深测的区域]\r\n└─ 测试建议：[具体的测试建议]\r\n```\r\n\r\n## 代码评审检查清单\r\n\r\n### 功能变更检查\r\n- [ ] 业务逻辑是否正确？\r\n- [ ] 边界条件是否处理？\r\n- [ ] 异常处理是否完善？\r\n- [ ] 数据校验是否完整？\r\n\r\n### 数据变更检查\r\n- [ ] 数据库变更是否兼容？\r\n- [ ] 数据迁移是否安全？\r\n- [ ] 索引变更是否影响性能？\r\n- [ ] 数据一致性是否保证？\r\n\r\n### 接口变更检查\r\n- [ ] 接口入参是否兼容？\r\n- [ ] 接口出参是否变化？\r\n- [ ] 错误码是否变化？\r\n- [ ] 文档是否更新？\r\n\r\n### 配置变更检查\r\n- [ ] 配置项是否新增？\r\n- [ ] 默认值是否合理？\r\n- [ ] 环境差异是否考虑？\r\n- [ ] 回滚方案是否准备？\r\n\r\n### 性能变更检查\r\n- [ ] 是否有性能影响？\r\n- [ ] 是否有内存泄漏风险？\r\n- [ ] 是否有并发问题？\r\n- [ ] 是否有资源竞争？\r\n\r\n## Examples\r\n\r\n**开发提交了登录模块的代码变更**\r\n→ CR四看分析：\r\n  - 看diff：修改了LoginController.java，新增密码加密逻辑\r\n  - 看影响：影响登录流程、密码验证、Session创建\r\n  - 看风险模式：加密算法变更可能导致兼容性问题\r\n  - 看测试建议：回归登录成功/失败流程，新增加密算法兼容性测试\r\n\r\n**配置项变更（数据库连接池大小调整）**\r\n→ 影响范围评估：确定需要回归的接口和场景\r\n\r\n## Guidelines\r\n\r\n代码评审完成后检查：\r\n- [ ] 是否分析了diff内容？\r\n- [ ] 是否评估了影响范围？\r\n- [ ] 是否识别了风险模式？\r\n- [ ] 是否给出了测试建议？\r\n- [ ] 建议是否可执行？\n\nFile v1.4.1:_meta.json\n\n{\n  \"ownerId\": \"kn71y9b23csfx0ykgm55d5m9x5891zt8\",\n  \"slug\": \"qa-code-review-for-test\",\n  \"version\": \"1.4.1\",\n  \"publishedAt\": 1782406438396\n}\n\nFile v1.4.1:skill-card.md\n\n## Description: <br>\nReviews code changes from a QA and testing perspective to identify change impact, risk patterns, and precise test recommendations. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[kokxi](https://clawhub.ai/user/kokxi) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nDevelopers, QA engineers, and code reviewers use this skill to review diffs, understand impact scope, identify testing risks, and choose regression or new test coverage. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Broad activation phrases could route ordinary code-review requests into a test-focused review posture. <br>\nMitigation: Narrow activation phrases to explicit QA, testing, impact-analysis, or test-review intents before publishing or relying on the skill. <br>\nRisk: The security summary flags hidden or control-character signals in SKILL.md. <br>\nMitigation: Remove invisible and control characters from SKILL.md and rescan before publication. <br>\nRisk: The skill is intended to read code changes and may use shell commands while preparing review guidance. <br>\nMitigation: Use it only in intended repositories and review any proposed shell commands before execution. <br>\n\n\n## Reference(s): <br>\n- [ClawHub skill page](https://clawhub.ai/kokxi/skills/qa-code-review-for-test) <br>\n- [Publisher profile](https://clawhub.ai/user/kokxi) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [text, markdown, guidance] <br>\n**Output Format:** [Markdown test-review report] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Focuses on impact scope, risk patterns, regression areas, and actionable test recommendations.] <br>\n\n## Skill Version(s): <br>\n1.4.1 (source: server release evidence) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.4.0: 3 files, 3656 bytes\n\nFiles: skill-card.md (1876b), SKILL.md (5405b), _meta.json (142b)\n\nFile v1.4.0:SKILL.md\n\n---\r\nname: qa-code-review-for-test\r\ndescription: >-\r\n  测试视角的代码评审，从测试角度分析代码变更的影响范围和风险模式。当用户需要从测试角度评审代码、进行CR或分析代码变更影响时自动触发。\r\n  也适用于：代码变更后需要确定测试范围，或评估变更引入的回归风险时。\r\n   关键词：代码评审、CR、测试视角、变更影响分析、代码覆盖率、变更风险评估、测试范围分析、回归风险、代码Diff。\nwhen_to_use: 用户说\"代码评审\"、\"CR\"、\"测试视角\"、\"看代码\"、\"代码变更\"、\"Diff\"、需要从测试角度分析代码变更、代码变更后需要确定测试范围时\r\nallowed-tools: Read Grep Glob Bash\r\nrelated_skills:\r\n  upstream:\r\n    - qa-boundary-deep-dive      # 输入：边界分析识别风险区域\r\n    - qa-risk-intuition          # 输入：风险评估识别高风险区域\r\n  downstream:\r\n    - qa-execution-observation   # 输出：代码变更指导执行观察\r\n    - qa-test-strategy-design    # 输出：代码变更影响测试策略\r\ninput_format: 代码变更（git diff）+ 边界分析 + 风险评估\r\noutput_format: 测试视角CR报告（影响范围+风险模式+测试建议）\r\n---\r\n\r\n# 测试视角的代码评审\r\n\r\n## Overview\r\n\r\n你是一位测试视角的代码评审专家，擅长从测试角度分析代码变更。\r\n**核心原则**：看代码不是为了Review代码质量，而是判断变更影响范围、识别需要重点回归的区域。\r\n本技能提供CR四看法（看diff/看影响/看风险模式/看测试建议）。\r\n\r\n> **代码读取许可**：本技能需要读取代码变更（git diff）进行分析，仅关注测试影响，不评估代码质量。\r\n\r\n## 测试视角CR四看\r\n\r\n### 第1看：看diff（改了什么）\r\n\r\n```\r\n分析维度：\r\n├─ 新增文件：新增了哪些文件？\r\n├─ 修改文件：修改了哪些文件？\r\n├─ 删除文件：删除了哪些文件？\r\n├─ 代码行数：新增/修改/删除多少行？\r\n└─ 变更类型：功能/修复/重构/配置？\r\n\r\n关注点：\r\n- 核心逻辑变更\r\n- 数据库变更\r\n- 配置变更\r\n- 接口变更\r\n```\r\n\r\n### 第2看：看影响（波及哪里）\r\n\r\n```\r\n分析维度：\r\n├─ 调用方：哪些地方调用了这个方法？\r\n├─ 数据流向：数据从哪来、到哪去？\r\n├─ 接口变更：对外接口有没有变？\r\n├─ 数据库变更：表结构/索引有没有变？\r\n└─ 配置变更：配置项有没有变？\r\n\r\n关注点：\r\n- 影响范围评估\r\n- 需要回归的区域\r\n- 需要新增的测试场景\r\n```\r\n\r\n### 第3看：看风险模式（有什么风险）\r\n\r\n```\r\n风险模式识别：\r\n├─ 静态数据变化：硬编码的值变了\r\n├─ 超时/重试：涉及超时或重试逻辑\r\n├─ 异常吞没：异常被catch但没处理\r\n├─ 并发处理：涉及多线程/分布式锁\r\n├─ 状态管理：涉及状态变更\r\n├─ 权限控制：涉及认证/授权\r\n├─ 数据转换：涉及格式/类型转换\r\n└─ 外部依赖：涉及第三方服务\r\n\r\n关注点：\r\n- 每个风险模式对应的测试场景\r\n- 需要重点验证的区域\r\n```\r\n\r\n### 第4看：看测试建议（怎么测）\r\n\r\n```\r\n测试建议输出：\r\n├─ 回归测试：哪些功能需要回归？\r\n├─ 新增测试：需要新增哪些测试场景？\r\n├─ 重点测试：哪些区域需要深测？\r\n├─ 性能测试：是否需要性能测试？\r\n└─ 安全测试：是否需要安全测试？\r\n\r\n输出格式：\r\n[变更描述]\r\n├─ 影响范围：[影响的功能/模块]\r\n├─ 回归范围：[需要回归的功能]\r\n├─ 新增场景：[需要新增的测试场景]\r\n├─ 重点区域：[需要深测的区域]\r\n└─ 测试建议：[具体的测试建议]\r\n```\r\n\r\n## 代码评审检查清单\r\n\r\n### 功能变更检查\r\n- [ ] 业务逻辑是否正确？\r\n- [ ] 边界条件是否处理？\r\n- [ ] 异常处理是否完善？\r\n- [ ] 数据校验是否完整？\r\n\r\n### 数据变更检查\r\n- [ ] 数据库变更是否兼容？\r\n- [ ] 数据迁移是否安全？\r\n- [ ] 索引变更是否影响性能？\r\n- [ ] 数据一致性是否保证？\r\n\r\n### 接口变更检查\r\n- [ ] 接口入参是否兼容？\r\n- [ ] 接口出参是否变化？\r\n- [ ] 错误码是否变化？\r\n- [ ] 文档是否更新？\r\n\r\n### 配置变更检查\r\n- [ ] 配置项是否新增？\r\n- [ ] 默认值是否合理？\r\n- [ ] 环境差异是否考虑？\r\n- [ ] 回滚方案是否准备？\r\n\r\n### 性能变更检查\r\n- [ ] 是否有性能影响？\r\n- [ ] 是否有内存泄漏风险？\r\n- [ ] 是否有并发问题？\r\n- [ ] 是否有资源竞争？\r\n\r\n## Examples\r\n\r\n**开发提交了登录模块的代码变更**\r\n→ CR四看分析：\r\n  - 看diff：修改了LoginController.java，新增密码加密逻辑\r\n  - 看影响：影响登录流程、密码验证、Session创建\r\n  - 看风险模式：加密算法变更可能导致兼容性问题\r\n  - 看测试建议：回归登录成功/失败流程，新增加密算法兼容性测试\r\n\r\n**配置项变更（数据库连接池大小调整）**\r\n→ 影响范围评估：确定需要回归的接口和场景\r\n\r\n## Guidelines\r\n\r\n代码评审完成后检查：\r\n- [ ] 是否分析了diff内容？\r\n- [ ] 是否评估了影响范围？\r\n- [ ] 是否识别了风险模式？\r\n- [ ] 是否给出了测试建议？\r\n- [ ] 建议是否可执行？\n\nFile v1.4.0:_meta.json\n\n{\n  \"ownerId\": \"kn71y9b23csfx0ykgm55d5m9x5891zt8\",\n  \"slug\": \"qa-code-review-for-test\",\n  \"version\": \"1.4.0\",\n  \"publishedAt\": 1782277576992\n}\n\nFile v1.4.0:skill-card.md\n\n## Description: <br>\nProvides a Chinese-language, testing-focused code review workflow that analyzes code diffs for change impact, regression risk patterns, and actionable test recommendations. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[kokxi](https://clawhub.ai/user/kokxi) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nDevelopers and QA engineers use this skill to review code diffs from a testing perspective, identify affected areas and regression risks, and produce test recommendations after code changes. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: The skill reads repository diffs and may surface sensitive implementation details in its analysis. <br>\nMitigation: Use it only in repositories the agent is allowed to inspect and keep Bash usage limited to read-oriented repository inspection. <br>\nRisk: Broad trigger phrases such as CR or Diff may invoke a testing-focused review when a general code review was intended. <br>\nMitigation: Confirm the desired review perspective and scope before relying on the recommendations. <br>\n\n\n## Reference(s): <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [Analysis, Markdown, Guidance] <br>\n**Output Format:** [Markdown test-focused code review report] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [May include impact scope, regression risks, new test scenarios, priority areas, and concrete test recommendations.] <br>\n\n## Skill Version(s): <br>\n1.4.0 (source: server release metadata) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.3.0: 3 files, 3344 bytes\n\nFiles: skill-card.md (2078b), SKILL.md (4588b), _meta.json (142b)\n\nFile v1.3.0:SKILL.md\n\n---\r\nname: qa-code-review-for-test\r\ndescription: 测试视角的代码评审，从测试角度分析代码变更。当需要从测试角度评审代码时激活。\r\nwhen_to_use: 用户说\"代码评审\"、\"CR\"、\"测试视角\"、需要从测试角度分析代码变更时\r\nallowed-tools: Read Grep Glob Bash\r\nrelated_skills:\r\n  upstream:\r\n    - qa-boundary-deep-dive      # 输入：边界分析识别风险区域\r\n    - qa-risk-intuition          # 输入：风险评估识别高风险区域\r\n  downstream:\r\n    - qa-execution-observation   # 输出：代码变更指导执行观察\r\n    - qa-test-strategy-design    # 输出：代码变更影响测试策略\r\ninput_format: 代码变更（git diff）+ 边界分析 + 风险评估\r\noutput_format: 测试视角CR报告（影响范围+风险模式+测试建议）\r\n---\r\n\r\n# 测试视角的代码评审\r\n\r\n你是一位测试视角的代码评审专家，擅长从测试角度分析代码变更。\r\n\r\n## 核心原则\r\n\r\n**有经验的测试会在CR阶段看代码，不是为了Review代码质量，而是判断变更影响范围、识别需要重点回归的区域。**\r\n\r\n**代码读取许可**：\r\n- **本技能需要读取代码**：与其他技能不同，本技能需要读取代码变更（git diff）进行分析\r\n- **目的**：从测试角度评审代码变更，识别影响范围和风险区域\r\n- **注意**：仅读取代码变更，不评估代码质量，只关注测试影响\r\n\r\n## 测试视角CR四看\r\n\r\n### 第1看：看diff（改了什么）\r\n\r\n```\r\n分析维度：\r\n├─ 新增文件：新增了哪些文件？\r\n├─ 修改文件：修改了哪些文件？\r\n├─ 删除文件：删除了哪些文件？\r\n├─ 代码行数：新增/修改/删除多少行？\r\n└─ 变更类型：功能/修复/重构/配置？\r\n\r\n关注点：\r\n- 核心逻辑变更\r\n- 数据库变更\r\n- 配置变更\r\n- 接口变更\r\n```\r\n\r\n### 第2看：看影响（波及哪里）\r\n\r\n```\r\n分析维度：\r\n├─ 调用方：哪些地方调用了这个方法？\r\n├─ 数据流向：数据从哪来、到哪去？\r\n├─ 接口变更：对外接口有没有变？\r\n├─ 数据库变更：表结构/索引有没有变？\r\n└─ 配置变更：配置项有没有变？\r\n\r\n关注点：\r\n- 影响范围评估\r\n- 需要回归的区域\r\n- 需要新增的测试场景\r\n```\r\n\r\n### 第3看：看风险模式（有什么风险）\r\n\r\n```\r\n风险模式识别：\r\n├─ 静态数据变化：硬编码的值变了\r\n├─ 超时/重试：涉及超时或重试逻辑\r\n├─ 异常吞没：异常被catch但没处理\r\n├─ 并发处理：涉及多线程/分布式锁\r\n├─ 状态管理：涉及状态变更\r\n├─ 权限控制：涉及认证/授权\r\n├─ 数据转换：涉及格式/类型转换\r\n└─ 外部依赖：涉及第三方服务\r\n\r\n关注点：\r\n- 每个风险模式对应的测试场景\r\n- 需要重点验证的区域\r\n```\r\n\r\n### 第4看：看测试建议（怎么测）\r\n\r\n```\r\n测试建议输出：\r\n├─ 回归测试：哪些功能需要回归？\r\n├─ 新增测试：需要新增哪些测试场景？\r\n├─ 重点测试：哪些区域需要深测？\r\n├─ 性能测试：是否需要性能测试？\r\n└─ 安全测试：是否需要安全测试？\r\n\r\n输出格式：\r\n[变更描述]\r\n├─ 影响范围：[影响的功能/模块]\r\n├─ 回归范围：[需要回归的功能]\r\n├─ 新增场景：[需要新增的测试场景]\r\n├─ 重点区域：[需要深测的区域]\r\n└─ 测试建议：[具体的测试建议]\r\n```\r\n\r\n## 代码评审检查清单\r\n\r\n### 功能变更检查\r\n- [ ] 业务逻辑是否正确？\r\n- [ ] 边界条件是否处理？\r\n- [ ] 异常处理是否完善？\r\n- [ ] 数据校验是否完整？\r\n\r\n### 数据变更检查\r\n- [ ] 数据库变更是否兼容？\r\n- [ ] 数据迁移是否安全？\r\n- [ ] 索引变更是否影响性能？\r\n- [ ] 数据一致性是否保证？\r\n\r\n### 接口变更检查\r\n- [ ] 接口入参是否兼容？\r\n- [ ] 接口出参是否变化？\r\n- [ ] 错误码是否变化？\r\n- [ ] 文档是否更新？\r\n\r\n### 配置变更检查\r\n- [ ] 配置项是否新增？\r\n- [ ] 默认值是否合理？\r\n- [ ] 环境差异是否考虑？\r\n- [ ] 回滚方案是否准备？\r\n\r\n### 性能变更检查\r\n- [ ] 是否有性能影响？\r\n- [ ] 是否有内存泄漏风险？\r\n- [ ] 是否有并发问题？\r\n- [ ] 是否有资源竞争？\r\n\r\n## 验收清单\r\n\r\n代码评审完成后检查：\r\n- [ ] 是否分析了diff内容？\r\n- [ ] 是否评估了影响范围？\r\n- [ ] 是否识别了风险模式？\r\n- [ ] 是否给出了测试建议？\r\n- [ ] 建议是否可执行？\n\nFile v1.3.0:_meta.json\n\n{\n  \"ownerId\": \"kn71y9b23csfx0ykgm55d5m9x5891zt8\",\n  \"slug\": \"qa-code-review-for-test\",\n  \"version\": \"1.3.0\",\n  \"publishedAt\": 1782056275419\n}\n\nFile v1.3.0:skill-card.md\n\n## Description: <br>\nProvides a QA-focused code review guide that reads code diffs to identify impact scope, risk patterns, regression coverage, and concrete testing recommendations. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[kokxi](https://clawhub.ai/user/kokxi) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nQA engineers, test leads, and developers use this skill during code review to translate code changes into impact scope, risk patterns, regression areas, and actionable test suggestions. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: The skill may activate on broad code review or CR requests and shift the review toward testing impact instead of general code quality. <br>\nMitigation: Use explicit wording when requesting a testing-focused review, and ask for another review style when broader implementation review is desired. <br>\nRisk: The skill reads code diffs and related code context to produce its review. <br>\nMitigation: Use it only in workspaces where the agent is allowed to inspect the relevant code changes. <br>\n\n\n## Reference(s): <br>\n- [ClawHub skill page](https://clawhub.ai/kokxi/qa-code-review-for-test) <br>\n- [Publisher profile](https://clawhub.ai/user/kokxi) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [text, markdown, guidance] <br>\n**Output Format:** [Markdown QA code review report with impact scope, risk patterns, regression coverage, and testing recommendations] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [The skill reads git diffs and related code context for QA impact analysis; it does not assess general code quality.] <br>\n\n## Skill Version(s): <br>\n1.3.0 (source: ClawHub release evidence) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>","readmeExcerpt":"Skill: qa-code-review-for-test Owner: kokxi Summary: 当开发提了 PR、代码变更需要确定测试范围、或者想通过分析代码来预测可能出 Bug 的区域时使用此技能。从测试视角分析代码变更的影响范围、识别高危模式和典型风险区域。不要看完整代码逻辑——你只需要关注变更类型（新增/修改/删除/重构）、影响范围（接口定义/数据库字段/业务逻辑）和相关依赖，据此确定最小回归测试范围。输出代码变更影响分析报告。 触发场景：代码评审、CR、测试视角、看代码、代码变更、Diff、代码变更后需要确定测试范围时。 Use when the user asks about: reviewing a PR or code diff from a testing perspective to determine regression scope and high-risk areas. Tags: lates","codeSnippets":[],"executableExamples":[{"language":"text","snippet":"分析维度：\n├─ 新增文件：新增了哪些文件？\n├─ 修改文件：修改了哪些文件？\n├─ 删除文件：删除了哪些文件？\n├─ 代码行数：新增/修改/删除多少行？\n└─ 变更类型：功能/修复/重构/配置？\n\n关注点：\n- 核心逻辑变更\n- 数据库变更\n- 配置变更\n- 接口变更"},{"language":"text","snippet":"分析维度：\n├─ 调用方：哪些地方调用了这个方法？\n├─ 数据流向：数据从哪来、到哪去？\n├─ 接口变更：对外接口有没有变？\n├─ 数据库变更：表结构/索引有没有变？\n└─ 配置变更：配置项有没有变？\n\n关注点：\n- 影响范围评估\n- 需要回归的区域\n- 需要新增的测试场景"},{"language":"text","snippet":"风险模式识别：\n├─ 静态数据变化：硬编码的值变了\n├─ 超时/重试：涉及超时或重试逻辑\n├─ 异常吞没：异常被catch但没处理\n├─ 并发处理：涉及多线程/分布式锁\n├─ 状态管理：涉及状态变更\n├─ 权限控制：涉及认证/授权\n├─ 数据转换：涉及格式/类型转换\n└─ 外部依赖：涉及第三方服务\n\n关注点：\n- 每个风险模式对应的测试场景\n- 需要重点验证的区域"},{"language":"text","snippet":"测试建议输出：\n├─ 回归测试：哪些功能需要回归？\n├─ 新增测试：需要新增哪些测试场景？\n├─ 重点测试：哪些区域需要深测？\n├─ 性能测试：是否需要性能测试？\n└─ 安全测试：是否需要安全测试？\n\n输出格式：\n[变更描述]\n├─ 影响范围：[影响的功能/模块]\n├─ 回归范围：[需要回归的功能]\n├─ 新增场景：[需要新增的测试场景]\n├─ 重点区域：[需要深测的区域]\n└─ 测试建议：[具体的测试建议]"},{"language":"text","snippet":"分析维度：\n├─ 新增文件：新增了哪些文件？\n├─ 修改文件：修改了哪些文件？\n├─ 删除文件：删除了哪些文件？\n├─ 代码行数：新增/修改/删除多少行？\n└─ 变更类型：功能/修复/重构/配置？\n\n关注点：\n- 核心逻辑变更\n- 数据库变更\n- 配置变更\n- 接口变更"},{"language":"text","snippet":"分析维度：\n├─ 调用方：哪些地方调用了这个方法？\n├─ 数据流向：数据从哪来、到哪去？\n├─ 接口变更：对外接口有没有变？\n├─ 数据库变更：表结构/索引有没有变？\n└─ 配置变更：配置项有没有变？\n\n关注点：\n- 影响范围评估\n- 需要回归的区域\n- 需要新增的测试场景"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: qa-code-review-for-test\ndescription: >-\n  当开发提了 PR、代码变更需要确定测试范围、或者想通过分析代码来预测可能出 Bug 的区域时使用此技能。从测试视角分析代码变更的影响范围、识别高危模式和典型风险区域。不要看完整代码逻辑——你只需要关注变更类型（新增/修改/删除/重构）、影响范围（接口定义/数据库字段/业务逻辑）和相关依赖，据此确定最小回归测试范围。输出代码变更影响分析报告。 触发场景：代码评审、CR、测试视角、看代码、代码变更、Diff、代码变更后需要确定测试范围时。 Use when the user asks about: reviewing a PR or code diff from a testing perspective to determine regression scope and high-risk areas.\nlicense: MIT\nallowed-tools: Read Grep Glob Bash\nmetadata:\n  display-name: \"Code Review For Test\"\n  version: \"1.8.0\"\n  when-to-use: \"用户说\\\"代码评审\\\"、\\\"CR\\\"、\\\"测试视角\\\"、\\\"看代码\\\"、\\\"代码变更\\\"、\\\"Diff\\\"、需要从测试角度分析代码变更、代码变更后需要确定测试范围时\"\n  related-skills: \"{\\\"upstream\\\":[\\\"qa-boundary-deep-dive\\\",\\\"qa-risk-intuition\\\"],\\\"downstream\\\":[\\\"qa-execution-observation\\\",\\\"qa-test-strategy-design\\\",\\\"qa-regression-testing\\\"]}\"\n  references: \"[\\\"references/cr-lens.md\\\"]\"\n  input-format: \"{\\\"required\\\":[{\\\"name\\\":\\\"代码变更\\\",\\\"type\\\":\\\"string\\\",\\\"description\\\":\\\"代码变更的diff或描述\\\"},{\\\"name\\\":\\\"测试用例\\\",\\\"type\\\":\\\"array\\\",\\\"description\\\":\\\"相关测试用例列表\\\"}],\\\"optional\\\":[{\\\"name\\\":\\\"需求文档\\\",\\\"type\\\":\\\"string\\\",\\\"description\\\":\\\"相关功能需求\\\"}]}\"\n  output-format: \"{\\\"traceability\\\":[\\\"每次代码评审带唯一ID（CR-XXXX）\\\",\\\"关联变更ID或需求ID\\\"],\\\"structure\\\":[\\\"覆盖率：标注口径（基于现有需求/输入文档），禁止\\\\\\\"全覆盖/100%\\\\\\\"绝对化表述；缺失模块标注\\\\\\\"未覆盖+原因\\\\\\\"\\\",{\\\"review_findings\\\":\\\"代码评审发现\\\"},{\\\"test_gaps\\\":\\\"测试遗漏点\\\"},{\\\"impact_analysis\\\":\\\"变更影响分析\\\"},{\\\"high_risk_patterns\\\":\\\"高危模式识别\\\"},{\\\"regression_scope\\\":\\\"回归测试范围建议\\\"}]}\"\n  error-recovery-guidance: \"{\\\"on_failure\\\":\\\"代码变更分析遗漏依赖时回退到边界分析补充\\\",\\\"retry_behavior\\\":\\\"补全依赖分析后重新确定回归范围\\\"}\"\n  categories: \"[\\\"Development\\\",\\\"Team\\\"]\"\n  depth-requirement: \"{\\\"reference_value\\\":\\\"根据代码变更量调整评审深度：简单×1/中等×2/复杂×3\\\",\\\"minimum\\\":\\\"至少分析变更类型、影响范围、回归范围3个维度\\\"}\"\n---\n> ⚠️ 本技能单独使用效果有限，建议配合完整技能集（12 步工作流）使用。安装：npx skills add Kokxi/qa-test-skills\n\n> **⚠️ 安全警告**：本技能的示例可能涉及代码变更分析（新增/修改/删除/重构）。\n> 实际使用时请勿直接基于评审结论修改源码，先与开发确认变更范围和回归风险。\n> 本技能仅在 workspace/ 输出评估文件，不持久化、不外传、不跨会话复用。\n\n# 测试视角的代码评审\n\n## 核心原则\n\n看代码不是为了Review代码质量，而是判断变更影响范围、识别需要重点回归的区域。\n\n> **代码读取许可**：本技能需要读取代码变更（git diff）进行分析，仅关注测试影响，不评估代码质量。\n\n## 深度要求（参考值）\n\n**关键指标**：根据代码变更复杂度调整CR深度\n\n| 复杂度 | CR检查点要求 | 说明 |\n|--------|-------------|------|\n| 简单变更 | 5-8个检查点 | 单文件/配置/文案变更 |\n| 中等变更 | 12-20个检查点 | 多文件/逻辑修改 |\n| 复杂变更 | 25-40个检查点 | 重构/重写/核心模块变更 |\n\n## 加载时机\n\n| 什么时候读 | 读哪个 |\n|-----------|--------|\n| 从测试角度评审代码变更时 | [`references/cr-lens.md`](references/cr-lens.md) |\n\n> `测试视角CR四看`的完整内容已下沉至 `references/cr-lens.md`，避免每次触发都占用上下文。\n\n## 代码评审检查清单\n\n### 功能变更检查\n- [ ] 业务逻辑是否正确？\n- [ ] 边界条件是否处理？\n- [ ] 异常处理是否完善？\n- [ ] 数据校验是否完整？\n\n### 数据变更检查\n- [ ] 数据库变更是否兼容？\n- [ ] 数据迁移是否安全？\n- [ ] 索引变更是否影响性能？\n- [ ] 数据一致性是否保证？\n\n### 接口变更检查\n- [ ] 接口入参是否兼容？\n- [ ] 接口出参是否变化？\n- [ ] 错误码是否变化？\n- [ ] 文档是否更新？\n\n### 配置变更检查\n- [ ] 配置项是否新增？\n- [ ] 默认值是否合理？\n- [ ] 环境差异是否考虑？\n- [ ] 回滚方案是否准备？\n\n### 性能变更检查\n- [ ] 是否有性能影响？\n- [ ] 是否有内存泄漏风险？\n- [ ] 是否有并发问题？\n- [ ] 是否有资源竞争？\n\n## 应用场景\n\n**开发提交了登录模块的代码变更**\n→ CR四看分析：\n  - 看diff：修改了LoginController.java，新增密码加密逻辑\n  - 看影响：影响登录流程、密码验证、Session创建\n  - 看风险模式：加密算法变更可能导致兼容性问题\n  - 看测试建议：回归登录成功/失败流程，新增加密算法兼容性测试\n\n**配置项变更（数据库连接池大小调整"},{"path":"_meta.json","content":"{\n  \"ownerId\": \"kn71y9b23csfx0ykgm55d5m9x5891zt8\",\n  \"slug\": \"qa-code-review-for-test\",\n  \"version\": \"1.8.0\",\n  \"publishedAt\": 1790655962937\n}"},{"path":"references/cr-lens.md","content":"# 测试视角 CR 四看详解\n\n> 本文是 `qa-code-review-for-test` 的**测试视角 CR 四看详解**。从测试角度评审代码变更时读本文；\n其余部分留在 SKILL.md，不必读本文。\n\n---\n\n\n### 第1看：看diff（改了什么）\n\n```text\n分析维度：\n├─ 新增文件：新增了哪些文件？\n├─ 修改文件：修改了哪些文件？\n├─ 删除文件：删除了哪些文件？\n├─ 代码行数：新增/修改/删除多少行？\n└─ 变更类型：功能/修复/重构/配置？\n\n关注点：\n- 核心逻辑变更\n- 数据库变更\n- 配置变更\n- 接口变更\n```\n\n### 第2看：看影响（波及哪里）\n\n```text\n分析维度：\n├─ 调用方：哪些地方调用了这个方法？\n├─ 数据流向：数据从哪来、到哪去？\n├─ 接口变更：对外接口有没有变？\n├─ 数据库变更：表结构/索引有没有变？\n└─ 配置变更：配置项有没有变？\n\n关注点：\n- 影响范围评估\n- 需要回归的区域\n- 需要新增的测试场景\n```\n\n### 第3看：看风险模式（有什么风险）\n\n```text\n风险模式识别：\n├─ 静态数据变化：硬编码的值变了\n├─ 超时/重试：涉及超时或重试逻辑\n├─ 异常吞没：异常被catch但没处理\n├─ 并发处理：涉及多线程/分布式锁\n├─ 状态管理：涉及状态变更\n├─ 权限控制：涉及认证/授权\n├─ 数据转换：涉及格式/类型转换\n└─ 外部依赖：涉及第三方服务\n\n关注点：\n- 每个风险模式对应的测试场景\n- 需要重点验证的区域\n```\n\n### 第4看：看测试建议（怎么测）\n\n```text\n测试建议输出：\n├─ 回归测试：哪些功能需要回归？\n├─ 新增测试：需要新增哪些测试场景？\n├─ 重点测试：哪些区域需要深测？\n├─ 性能测试：是否需要性能测试？\n└─ 安全测试：是否需要安全测试？\n\n输出格式：\n[变更描述]\n├─ 影响范围：[影响的功能/模块]\n├─ 回归范围：[需要回归的功能]\n├─ 新增场景：[需要新增的测试场景]\n├─ 重点区域：[需要深测的区域]\n└─ 测试建议：[具体的测试建议]\n```"},{"path":"skill-card.md","content":"## Description:\n\nReviews code changes from a testing perspective to identify affected areas, high-risk patterns, and a focused regression test scope.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[kokxi](https://clawhub.ai/user/kokxi)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers and testers use this skill to review pull requests or diffs for change impact, test gaps, and targeted regression scenarios.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The optional installation command fetches an unpinned package.\n\nMitigation: Only install from a trusted source, or pin and verify the package first.\n\nRisk: The review reads repository diffs and related code, which may contain sensitive information.\n\nMitigation: Limit access to the intended repository and avoid sharing sensitive code in review outputs.\n\n## Reference(s):\n\n- [Testing-focused code review lens](references/cr-lens.md)\n- [ClawHub skill release](https://clawhub.ai/kokxi/skills/qa-code-review-for-test)\n\n## Skill Output:\n\n**Output Type(s):** [Analysis, Guidance]\n\n**Output Format:** [Markdown]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Includes review findings, test gaps, impact analysis, risk patterns, and a regression scope with a review ID.]\n\n## Skill Version(s):\n\n1.8.0 (source: skill frontmatter and ClawHub release)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment."}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":"当开发提了 PR、代码变更需要确定测试范围、或者想通过分析代码来预测可能出 Bug 的区域时使用此技能。从测试视角分析代码变更的影响范围、识别高危模式和典型风险区域。不要看完整代码逻辑——你只需要关注变更类型（新增/修改/删除/重构）、影响范围（接口定义/数据库字段/业务逻辑）和相关依赖，据此确定最小回归测试范围。输出代码变更影响分析报告。 触发场景：代码评审、CR、测试视角、看代码、代码变更、Diff、代码变更后需要确定测试范围时。 Use when the user asks about: reviewing a PR or code diff from a testing perspective to determine regression scope and high-risk areas. Skill: qa-code-review-for-test Owner: kokxi Summary: 当开发提了 PR、代码变更需要确定测试范围、或者想通过分析代码来预测可能出 Bug 的区域时使用此技能。从测试视角分析代码变更的影响范围、识别高危模式和典型风险区域。不要看完整代码逻辑——你只需要关注变更类型（新增/修改/删除/重构）、影响范围（接口定义/数据库字段/业务逻辑）和相关依赖，据此确定最小回归测试范围。输出代码变更影响分析报告。 触发场景：代码评审、CR、测试视角、看代码、代码变更、Diff、代码变更后需要确定测试范围时。 Use when the user asks about: reviewing a PR or code diff from a testing perspective to determine regression scope and high-risk areas. Tags: lates","editorialQuality":{"score":100,"threshold":65,"status":"ready","wordCount":984,"uniquenessScore":49,"reasons":[]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-11T10:29:17.168Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-11T10:29:17.168Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-11T14:13:22.051Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}