[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ACCCAA36RCWAA93YDDRBX8":3,"skill-same:01M6ACCCAA36RCWAA93YDDRBX8":110},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":28,"publishedAt":51,"linkOnly":52,"markdownContent":53,"markdownBody":54,"frontMatter":55,"refName":57,"commitSha":58,"skillDirectory":59,"forksCount":60,"repositoryHtmlUrl":61,"repositoryHomepageUrl":62,"ownerHtmlUrl":63,"ownerBlogUrl":64,"ownerDescription":6,"updatedAt":65,"install":66,"resources":79},"01M6ACCCAA36RCWAA93YDDRBX8","shallow-review",null,"Shallow (quick) ensemble bug-finding review using 6 specialist agents in parallel. Each specialist reviews the same patch through a different lens: Logic & Types, Boundaries & I\u002FO, Concurrency & State, Resources & Serialization, Absence Analysis, and API Completeness. Findings are merged and deduplicated. Best for: quick first-pass review of patches, triage of diffs, broad surface-level bug scan. For deeper file-focused review with full pattern catalogs and codebase investigation, use the deep-review skill instead.","apache\u002Fcassandra","apache","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F47359?v=4","01M6AC83E6K4FDKK7HZ8WNMQKE","The Apache Software Foundation","01M6ACBT70F584W658X9T70A5M",10153,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fapache\u002Fcassandra\u002Fblob\u002Ftrunk\u002F.claude\u002Fskills\u002Fshallow-review\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50],"shallow review","review","scan","for","reviews","quick","types","lens","resources","full","deep","pattern","deeper","bug","patch","parallel","api","analysis","concurrency","state","triage","diffs","2026-11-10 10:12:30",false,"---\nname: shallow-review\nversion: \"1.0.0\"\ndescription: >\n  Shallow (quick) ensemble bug-finding review using 6 specialist agents in parallel. Each\n  specialist reviews the same patch through a different lens: Logic & Types, Boundaries &\n  I\u002FO, Concurrency & State, Resources & Serialization, Absence Analysis, and API\n  Completeness. Findings are merged and deduplicated. Best for: quick first-pass review of\n  patches, triage of diffs, broad surface-level bug scan. For deeper file-focused review\n  with full pattern catalogs and codebase investigation, use the deep-review skill instead.\n---\n\n# Ensemble Code Review\n\nSix specialist agents review the same patch in parallel. Each applies Phase 0 (understand\nthe change, form hypotheses) then a focused checklist. Their findings are merged and\ndeduplicated.\n\n```\n                    +------------------+\n                    |   Input Patch    |\n                    +--------+---------+\n                             |\n    +-------+------+---------+---------+-----------+\n    |       |      |         |         |           |\n+---v--+ +--v--+ +-v-----+ +-v------+ +v-----+ +---v-------+\n|Logic | |Bound| |Concurr| |Resource| |Absenc| | Complete. |\n|&Type | | &I\u002FO| |&State | |& Serde | |(2-ph)| | & Contr.  |\n+--+---+ +--+--+ +---+---+ +---+----+ +--+---+ +---+-------+\n   |        |        |         |          |        |\n   +--------+--------+---------+----------+--------+\n                               |\n                    +----------v----------+\n                    |  Pass 3: Symmetry   |\n                    |  (serial, optional) |\n                    +----------+----------+\n                               |\n                    +----------v----------+\n                    |   Merge & Dedup     |\n                    |   (main agent)      |\n                    +---------------------+\n```\n\n## Quick Start\n\n1. **Identify target** — patch, diff, file, or subsystem\n2. **Launch 6 specialists** in parallel (see prompts below)\n3. **Run Pass 3 Symmetry** check (serial, after specialists complete)\n4. **Merge** findings: deduplicate, rank by confidence\n5. **Report** in unified format\n\n## Phase 0: Understand Before Checking\n\nEvery specialist runs Phase 0 BEFORE touching the checklist:\n\n1. **Summarize** the patch in 2–3 sentences (feature, fix, refactor, move?)\n2. **Hypothesize** — list 3–5 things that could go wrong with this type of change\n3. **Note** code shapes that warrant deeper investigation\n\nThis switches the review from bottom-up (checklist→code) to top-down\n(code→hypotheses→verification). The checklist then verifies and extends the hypotheses.\n\n---\n\n## The Six Specialists\n\n### 1. Logic & Types (52% of bugs)\n\n**Priority**: wrong comparisons, missing returns, wrong constants, boolean polarity, sentinel ambiguity.\n\n**Reference**: `references\u002Fgeneral\u002Fspecialists\u002Flogic.md`\n\n**Prompt**:\n```\nYou are a LOGIC specialist reviewing a patch for correctness bugs.\n\nPHASE 0 — Understand the patch first (before reading checklist):\nRead the patch: `{PATCH_PATH}`\n1. Summarize what this patch does in 2-3 sentences.\n2. List 3-5 things that could go wrong with this type of change.\n3. Note any suspicious code shapes (control flow, comparisons, constants, sentinels).\n\nPHASE 1 — Apply checklist:\nRead your checklist: `{SKILL_DIR}\u002Freferences\u002Fgeneral\u002Fspecialists\u002Flogic.md`\nApply questions that match your hypotheses and code shapes. Check all 30 items\nagainst the patch but spend the most effort where your hypotheses pointed.\n\nReport ALL findings above a noise floor. For each: Location, Confidence\n(High\u002FMedium\u002FLow), What's wrong (1-2 sentences).\nOr \"No finding in my domain\" if nothing applies.\n```\n\n### 2. Boundaries & I\u002FO (17% of bugs)\n\n**Priority**: off-by-one, integer overflow, null\u002Fbounds checks, buffer sizing, I\u002FO completeness.\n\n**Reference**: `references\u002Fgeneral\u002Fspecialists\u002Fboundary.md`\n\n**Prompt**:\n```\nYou are a BOUNDARY specialist reviewing a patch for correctness bugs.\n\nPHASE 0 — Understand the patch first (before reading checklist):\nRead the patch: `{PATCH_PATH}`\n1. Summarize what this patch does in 2-3 sentences.\n2. List 3-5 things that could go wrong with this type of change.\n3. Note any arithmetic, indexing, range, or I\u002FO operations.\n\nPHASE 1 — Apply checklist:\nRead your checklist: `{SKILL_DIR}\u002Freferences\u002Fgeneral\u002Fspecialists\u002Fboundary.md`\nApply questions that match your hypotheses and code shapes. Check all 22 items\nagainst the patch but spend the most effort where your hypotheses pointed.\n\nReport ALL findings above a noise floor. For each: Location, Confidence\n(High\u002FMedium\u002FLow), What's wrong (1-2 sentences).\nOr \"No finding in my domain\" if nothing applies.\n```\n\n### 3. Concurrency & State (16% of bugs)\n\n**Priority**: races, TOCTOU, live-view iteration, lock ordering, state cleanup.\n\n**Reference**: `references\u002Fgeneral\u002Fspecialists\u002Fconcurrency.md`\n\n**Prompt**:\n```\nYou are a CONCURRENCY specialist reviewing a patch for correctness bugs.\n\nPHASE 0 — Understand the patch first (before reading checklist):\nRead the patch: `{PATCH_PATH}`\n1. Summarize what this patch does in 2-3 sentences.\n2. List 3-5 things that could go wrong with this type of change.\n3. Note any shared state, locks, collections, lifecycle operations.\n\nPHASE 1 — Apply checklist:\nRead your checklist: `{SKILL_DIR}\u002Freferences\u002Fgeneral\u002Fspecialists\u002Fconcurrency.md`\nApply questions that match your hypotheses and code shapes. Check all 24 items\nagainst the patch but spend the most effort where your hypotheses pointed.\n\nReport ALL findings above a noise floor. For each: Location, Confidence\n(High\u002FMedium\u002FLow), What's wrong (1-2 sentences).\nOr \"No finding in my domain\" if nothing applies.\n```\n\n### 4. Resources & Serialization (15% of bugs)\n\n**Priority**: resource leaks, serialization mismatches, wrong metric types, background tasks, wrapper bypass.\n\n**Reference**: `references\u002Fgeneral\u002Fspecialists\u002Fresources.md`\n\n**Prompt**:\n```\nYou are a RESOURCES specialist reviewing a patch for correctness bugs.\n\nPHASE 0 — Understand the patch first (before reading checklist):\nRead the patch: `{PATCH_PATH}`\n1. Summarize what this patch does in 2-3 sentences.\n2. List 3-5 things that could go wrong with this type of change.\n3. Note any resource allocation, serialization methods, metrics, streams.\n\nPHASE 1 — Apply checklist:\nRead your checklist: `{SKILL_DIR}\u002Freferences\u002Fgeneral\u002Fspecialists\u002Fresources.md`\nApply questions that match your hypotheses and code shapes. Check all 26 items\nagainst the patch but spend the most effort where your hypotheses pointed.\n\nReport ALL findings above a noise floor. For each: Location, Confidence\n(High\u002FMedium\u002FLow), What's wrong (1-2 sentences).\nOr \"No finding in my domain\" if nothing applies.\n```\n\n### 5. Absence Analysis (cross-cutting)\n\n**Priority**: find what SHOULD be present but ISN'T — missing guards, cleanup, handlers, registrations.\n\n**Reference**: `references\u002Fgeneral\u002Fspecialists\u002Fabsence.md`\n\n**Prompt**:\n```\nYou are an ABSENCE specialist. Your job: find bugs that are purely absent — missing\nguards, cleanup, handlers, or conditions that leave no signal in the diff.\n\nPHASE 0 — Understand the patch first:\nRead the patch: `{PATCH_PATH}`\n1. Summarize what this patch does in 2-3 sentences.\n2. List 3-5 things that SHOULD be present but might be missing.\n\nPHASE 1 — Build the search list:\nRead your checklist: `{SKILL_DIR}\u002Freferences\u002Fgeneral\u002Fspecialists\u002Fabsence.md`\nFor each event in the diff matching items (a)-(q), add to your search list.\n\nPHASE 2 — Execute searches and report:\nFor each item in your search list:\n  - Use Grep and Read tools to gather evidence from the codebase\n  - If match found (remove\u002Fderegister exists): discard\n  - If no match found: report as finding\n\nReport ALL findings above a noise floor. For each: what's missing, where it should\nbe, what evidence you searched for, Confidence (High\u002FMedium\u002FLow).\nOr \"No absence finding\" if nothing applies.\n```\n\n### 6. API Completeness & Contracts\n\n**Priority**: missing fields, missing overrides, registration symmetry, visibility, event coverage.\n\n**Reference**: `references\u002Fgeneral\u002Fspecialists\u002Fcompleteness.md`\n\n**Prompt**:\n```\nYou are an API COMPLETENESS specialist reviewing a patch for correctness bugs.\n\nPHASE 0 — Understand the patch first (before reading checklist):\nRead the patch: `{PATCH_PATH}`\n1. Summarize what this patch does in 2-3 sentences.\n2. List 3-5 things that could be incomplete about this change.\n3. Note any new classes, new fields, new registrations, visibility changes.\n\nPHASE 1 — Apply checklist:\nRead your checklist: `{SKILL_DIR}\u002Freferences\u002Fgeneral\u002Fspecialists\u002Fcompleteness.md`\nApply questions that match your hypotheses and code shapes. Check all 22 items\nagainst the patch but spend the most effort where your hypotheses pointed.\n\nReport ALL findings above a noise floor. For each: Location, Confidence\n(High\u002FMedium\u002FLow), What's wrong (1-2 sentences).\nOr \"No finding in my domain\" if nothing applies.\n```\n\n---\n\n## Pass 3: Cross-Path Symmetry (serial, after specialists complete)\n\n**Prompt**:\n```\nYou are a SYMMETRY specialist. For each code path modified in this patch, identify\nwhether a structurally parallel path (same class, interface, event family, version range)\nwas NOT modified. For each asymmetry:\n- Where path A was changed\n- Where parallel path B exists\n- What was changed on A that is absent on B\n- Whether the asymmetry is intentional or suspicious\n\nRead the patch: `{PATCH_PATH}`\nSearch the codebase as needed using Grep and Read.\nReport all asymmetries, Confidence High\u002FMedium\u002FLow.\n```\n\n---\n\n## Merge & Dedup\n\nAfter all specialists report:\n\n1. **Collect** all findings from 6 specialists + symmetry\n2. **Deduplicate** — same code location + related reasons → combine\n3. **Rank** by confidence — findings confirmed by multiple specialists rank highest\n4. **Cross-check** reinforcement:\n   - Logic + Absence at same location → boost to High\n   - Concurrency + Resources on same lifecycle → boost to High\n   - Any finding flagged by 3+ specialists → treat as confirmed\n5. **3-point test** each finding:\n   - The code construct actually exists in the diff (not inferred)\n   - The bug is possible given the visible context (not speculative)\n   - The finding is actionable (what specifically should change)\n6. **Specialist Silence Rule**: If Absence or Completeness reports nothing on a >100-line\n   diff, note: \"Consider verifying Phase 2 searches executed for registration symmetry,\n   handler coverage, and field completeness.\"\n\n---\n\n## Report Format\n\n```\n## Review: [target]\n\n### Findings (ranked by confidence)\n\n#### Finding 1: [title]\n- **Location**: [file:line]\n- **Confidence**: High \u002F Medium \u002F Low\n- **Flagged by**: [specialists]\n- **What's wrong**: [1-2 sentences]\n\n### Specialist Coverage\n- Logic: [N findings \u002F no finding]\n- Boundary: [N findings \u002F no finding]\n- Concurrency: [N findings \u002F no finding]\n- Resources: [N findings \u002F no finding]\n- Absence: [N findings \u002F no finding]\n- Completeness: [N findings \u002F no finding]\n- Symmetry: [N asymmetries \u002F none]\n```\n\n## Statistical Priors\n\n| Category | Share | Specialist |\n|---|---|---|\n| Logic error in condition | 26% | Logic |\n| Wrong constant \u002F default | 15% | Logic |\n| Missing null \u002F bounds check | 13% | Boundary |\n| Incorrect filtering \u002F result | 11% | Logic |\n| Race condition | 9% | Concurrency |\n| Wrong serialization | 8% | Resources |\n| State not cleaned up | 7% | Concurrency |\n| Off-by-one | 4% | Boundary |\n| Resource leak | 3% | Resources |\n\n## Reference Files\n\n### Specialist checklists (trimmed, ensemble mode)\n- `references\u002Fgeneral\u002Fspecialists\u002Flogic.md` — 30 items, Logic specialist\n- `references\u002Fgeneral\u002Fspecialists\u002Fboundary.md` — 22 items, Boundary specialist\n- `references\u002Fgeneral\u002Fspecialists\u002Fconcurrency.md` — 24 items, Concurrency specialist\n- `references\u002Fgeneral\u002Fspecialists\u002Fresources.md` — 26 items, Resources specialist\n- `references\u002Fgeneral\u002Fspecialists\u002Fabsence.md` — Phase 1\u002F2 search patterns, Absence specialist\n- `references\u002Fgeneral\u002Fspecialists\u002Fcompleteness.md` — 22 items, Completeness specialist\n","# Ensemble Code Review\n\nSix specialist agents review the same patch in parallel. Each applies Phase 0 (understand\nthe change, form hypotheses) then a focused checklist. Their findings are merged and\ndeduplicated.\n\n```\n                    +------------------+\n                    |   Input Patch    |\n                    +--------+---------+\n                             |\n    +-------+------+---------+---------+-----------+\n    |       |      |         |         |           |\n+---v--+ +--v--+ +-v-----+ +-v------+ +v-----+ +---v-------+\n|Logic | |Bound| |Concurr| |Resource| |Absenc| | Complete. |\n|&Type | | &I\u002FO| |&State | |& Serde | |(2-ph)| | & Contr.  |\n+--+---+ +--+--+ +---+---+ +---+----+ +--+---+ +---+-------+\n   |        |        |         |          |        |\n   +--------+--------+---------+----------+--------+\n                               |\n                    +----------v----------+\n                    |  Pass 3: Symmetry   |\n                    |  (serial, optional) |\n                    +----------+----------+\n                               |\n                    +----------v----------+\n                    |   Merge & Dedup     |\n                    |   (main agent)      |\n                    +---------------------+\n```\n\n## Quick Start\n\n1. **Identify target** — patch, diff, file, or subsystem\n2. **Launch 6 specialists** in parallel (see prompts below)\n3. **Run Pass 3 Symmetry** check (serial, after specialists complete)\n4. **Merge** findings: deduplicate, rank by confidence\n5. **Report** in unified format\n\n## Phase 0: Understand Before Checking\n\nEvery specialist runs Phase 0 BEFORE touching the checklist:\n\n1. **Summarize** the patch in 2–3 sentences (feature, fix, refactor, move?)\n2. **Hypothesize** — list 3–5 things that could go wrong with this type of change\n3. **Note** code shapes that warrant deeper investigation\n\nThis switches the review from bottom-up (checklist→code) to top-down\n(code→hypotheses→verification). The checklist then verifies and extends the hypotheses.\n\n---\n\n## The Six Specialists\n\n### 1. Logic & Types (52% of bugs)\n\n**Priority**: wrong comparisons, missing returns, wrong constants, boolean polarity, sentinel ambiguity.\n\n**Reference**: `references\u002Fgeneral\u002Fspecialists\u002Flogic.md`\n\n**Prompt**:\n```\nYou are a LOGIC specialist reviewing a patch for correctness bugs.\n\nPHASE 0 — Understand the patch first (before reading checklist):\nRead the patch: `{PATCH_PATH}`\n1. Summarize what this patch does in 2-3 sentences.\n2. List 3-5 things that could go wrong with this type of change.\n3. Note any suspicious code shapes (control flow, comparisons, constants, sentinels).\n\nPHASE 1 — Apply checklist:\nRead your checklist: `{SKILL_DIR}\u002Freferences\u002Fgeneral\u002Fspecialists\u002Flogic.md`\nApply questions that match your hypotheses and code shapes. Check all 30 items\nagainst the patch but spend the most effort where your hypotheses pointed.\n\nReport ALL findings above a noise floor. For each: Location, Confidence\n(High\u002FMedium\u002FLow), What's wrong (1-2 sentences).\nOr \"No finding in my domain\" if nothing applies.\n```\n\n### 2. Boundaries & I\u002FO (17% of bugs)\n\n**Priority**: off-by-one, integer overflow, null\u002Fbounds checks, buffer sizing, I\u002FO completeness.\n\n**Reference**: `references\u002Fgeneral\u002Fspecialists\u002Fboundary.md`\n\n**Prompt**:\n```\nYou are a BOUNDARY specialist reviewing a patch for correctness bugs.\n\nPHASE 0 — Understand the patch first (before reading checklist):\nRead the patch: `{PATCH_PATH}`\n1. Summarize what this patch does in 2-3 sentences.\n2. List 3-5 things that could go wrong with this type of change.\n3. Note any arithmetic, indexing, range, or I\u002FO operations.\n\nPHASE 1 — Apply checklist:\nRead your checklist: `{SKILL_DIR}\u002Freferences\u002Fgeneral\u002Fspecialists\u002Fboundary.md`\nApply questions that match your hypotheses and code shapes. Check all 22 items\nagainst the patch but spend the most effort where your hypotheses pointed.\n\nReport ALL findings above a noise floor. For each: Location, Confidence\n(High\u002FMedium\u002FLow), What's wrong (1-2 sentences).\nOr \"No finding in my domain\" if nothing applies.\n```\n\n### 3. Concurrency & State (16% of bugs)\n\n**Priority**: races, TOCTOU, live-view iteration, lock ordering, state cleanup.\n\n**Reference**: `references\u002Fgeneral\u002Fspecialists\u002Fconcurrency.md`\n\n**Prompt**:\n```\nYou are a CONCURRENCY specialist reviewing a patch for correctness bugs.\n\nPHASE 0 — Understand the patch first (before reading checklist):\nRead the patch: `{PATCH_PATH}`\n1. Summarize what this patch does in 2-3 sentences.\n2. List 3-5 things that could go wrong with this type of change.\n3. Note any shared state, locks, collections, lifecycle operations.\n\nPHASE 1 — Apply checklist:\nRead your checklist: `{SKILL_DIR}\u002Freferences\u002Fgeneral\u002Fspecialists\u002Fconcurrency.md`\nApply questions that match your hypotheses and code shapes. Check all 24 items\nagainst the patch but spend the most effort where your hypotheses pointed.\n\nReport ALL findings above a noise floor. For each: Location, Confidence\n(High\u002FMedium\u002FLow), What's wrong (1-2 sentences).\nOr \"No finding in my domain\" if nothing applies.\n```\n\n### 4. Resources & Serialization (15% of bugs)\n\n**Priority**: resource leaks, serialization mismatches, wrong metric types, background tasks, wrapper bypass.\n\n**Reference**: `references\u002Fgeneral\u002Fspecialists\u002Fresources.md`\n\n**Prompt**:\n```\nYou are a RESOURCES specialist reviewing a patch for correctness bugs.\n\nPHASE 0 — Understand the patch first (before reading checklist):\nRead the patch: `{PATCH_PATH}`\n1. Summarize what this patch does in 2-3 sentences.\n2. List 3-5 things that could go wrong with this type of change.\n3. Note any resource allocation, serialization methods, metrics, streams.\n\nPHASE 1 — Apply checklist:\nRead your checklist: `{SKILL_DIR}\u002Freferences\u002Fgeneral\u002Fspecialists\u002Fresources.md`\nApply questions that match your hypotheses and code shapes. Check all 26 items\nagainst the patch but spend the most effort where your hypotheses pointed.\n\nReport ALL findings above a noise floor. For each: Location, Confidence\n(High\u002FMedium\u002FLow), What's wrong (1-2 sentences).\nOr \"No finding in my domain\" if nothing applies.\n```\n\n### 5. Absence Analysis (cross-cutting)\n\n**Priority**: find what SHOULD be present but ISN'T — missing guards, cleanup, handlers, registrations.\n\n**Reference**: `references\u002Fgeneral\u002Fspecialists\u002Fabsence.md`\n\n**Prompt**:\n```\nYou are an ABSENCE specialist. Your job: find bugs that are purely absent — missing\nguards, cleanup, handlers, or conditions that leave no signal in the diff.\n\nPHASE 0 — Understand the patch first:\nRead the patch: `{PATCH_PATH}`\n1. Summarize what this patch does in 2-3 sentences.\n2. List 3-5 things that SHOULD be present but might be missing.\n\nPHASE 1 — Build the search list:\nRead your checklist: `{SKILL_DIR}\u002Freferences\u002Fgeneral\u002Fspecialists\u002Fabsence.md`\nFor each event in the diff matching items (a)-(q), add to your search list.\n\nPHASE 2 — Execute searches and report:\nFor each item in your search list:\n  - Use Grep and Read tools to gather evidence from the codebase\n  - If match found (remove\u002Fderegister exists): discard\n  - If no match found: report as finding\n\nReport ALL findings above a noise floor. For each: what's missing, where it should\nbe, what evidence you searched for, Confidence (High\u002FMedium\u002FLow).\nOr \"No absence finding\" if nothing applies.\n```\n\n### 6. API Completeness & Contracts\n\n**Priority**: missing fields, missing overrides, registration symmetry, visibility, event coverage.\n\n**Reference**: `references\u002Fgeneral\u002Fspecialists\u002Fcompleteness.md`\n\n**Prompt**:\n```\nYou are an API COMPLETENESS specialist reviewing a patch for correctness bugs.\n\nPHASE 0 — Understand the patch first (before reading checklist):\nRead the patch: `{PATCH_PATH}`\n1. Summarize what this patch does in 2-3 sentences.\n2. List 3-5 things that could be incomplete about this change.\n3. Note any new classes, new fields, new registrations, visibility changes.\n\nPHASE 1 — Apply checklist:\nRead your checklist: `{SKILL_DIR}\u002Freferences\u002Fgeneral\u002Fspecialists\u002Fcompleteness.md`\nApply questions that match your hypotheses and code shapes. Check all 22 items\nagainst the patch but spend the most effort where your hypotheses pointed.\n\nReport ALL findings above a noise floor. For each: Location, Confidence\n(High\u002FMedium\u002FLow), What's wrong (1-2 sentences).\nOr \"No finding in my domain\" if nothing applies.\n```\n\n---\n\n## Pass 3: Cross-Path Symmetry (serial, after specialists complete)\n\n**Prompt**:\n```\nYou are a SYMMETRY specialist. For each code path modified in this patch, identify\nwhether a structurally parallel path (same class, interface, event family, version range)\nwas NOT modified. For each asymmetry:\n- Where path A was changed\n- Where parallel path B exists\n- What was changed on A that is absent on B\n- Whether the asymmetry is intentional or suspicious\n\nRead the patch: `{PATCH_PATH}`\nSearch the codebase as needed using Grep and Read.\nReport all asymmetries, Confidence High\u002FMedium\u002FLow.\n```\n\n---\n\n## Merge & Dedup\n\nAfter all specialists report:\n\n1. **Collect** all findings from 6 specialists + symmetry\n2. **Deduplicate** — same code location + related reasons → combine\n3. **Rank** by confidence — findings confirmed by multiple specialists rank highest\n4. **Cross-check** reinforcement:\n   - Logic + Absence at same location → boost to High\n   - Concurrency + Resources on same lifecycle → boost to High\n   - Any finding flagged by 3+ specialists → treat as confirmed\n5. **3-point test** each finding:\n   - The code construct actually exists in the diff (not inferred)\n   - The bug is possible given the visible context (not speculative)\n   - The finding is actionable (what specifically should change)\n6. **Specialist Silence Rule**: If Absence or Completeness reports nothing on a >100-line\n   diff, note: \"Consider verifying Phase 2 searches executed for registration symmetry,\n   handler coverage, and field completeness.\"\n\n---\n\n## Report Format\n\n```\n## Review: [target]\n\n### Findings (ranked by confidence)\n\n#### Finding 1: [title]\n- **Location**: [file:line]\n- **Confidence**: High \u002F Medium \u002F Low\n- **Flagged by**: [specialists]\n- **What's wrong**: [1-2 sentences]\n\n### Specialist Coverage\n- Logic: [N findings \u002F no finding]\n- Boundary: [N findings \u002F no finding]\n- Concurrency: [N findings \u002F no finding]\n- Resources: [N findings \u002F no finding]\n- Absence: [N findings \u002F no finding]\n- Completeness: [N findings \u002F no finding]\n- Symmetry: [N asymmetries \u002F none]\n```\n\n## Statistical Priors\n\n| Category | Share | Specialist |\n|---|---|---|\n| Logic error in condition | 26% | Logic |\n| Wrong constant \u002F default | 15% | Logic |\n| Missing null \u002F bounds check | 13% | Boundary |\n| Incorrect filtering \u002F result | 11% | Logic |\n| Race condition | 9% | Concurrency |\n| Wrong serialization | 8% | Resources |\n| State not cleaned up | 7% | Concurrency |\n| Off-by-one | 4% | Boundary |\n| Resource leak | 3% | Resources |\n\n## Reference Files\n\n### Specialist checklists (trimmed, ensemble mode)\n- `references\u002Fgeneral\u002Fspecialists\u002Flogic.md` — 30 items, Logic specialist\n- `references\u002Fgeneral\u002Fspecialists\u002Fboundary.md` — 22 items, Boundary specialist\n- `references\u002Fgeneral\u002Fspecialists\u002Fconcurrency.md` — 24 items, Concurrency specialist\n- `references\u002Fgeneral\u002Fspecialists\u002Fresources.md` — 26 items, Resources specialist\n- `references\u002Fgeneral\u002Fspecialists\u002Fabsence.md` — Phase 1\u002F2 search patterns, Absence specialist\n- `references\u002Fgeneral\u002Fspecialists\u002Fcompleteness.md` — 22 items, Completeness specialist\n",{"name":5,"version":56,"description":7},"1.0.0","trunk","ae4e78c0ece616138963019388061efa4208f67a",".claude\u002Fskills\u002Fshallow-review",4066,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fcassandra","https:\u002F\u002Fcassandra.apache.org\u002F","https:\u002F\u002Fgithub.com\u002Fapache","https:\u002F\u002Fwww.apache.org\u002F","2026-11-14 00:43:44",{"source":8,"skillName":5,"commands":67,"prompt":77,"zipAvailable":78},[68,71,74],{"tool":69,"command":70},"npx","npx skills add apache\u002Fcassandra --skill shallow-review",{"tool":72,"command":73},"bunx","bunx skills add apache\u002Fcassandra --skill shallow-review",{"tool":75,"command":76},"pnpm","pnpm dlx skills add apache\u002Fcassandra --skill shallow-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fapache\u002Fcassandra\u002Fblob\u002Ftrunk\u002F.claude\u002Fskills\u002Fshallow-review\u002FSKILL.md",true,[80,86,90,94,98,102,106],{"path":81,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":84,"sourceHtmlUrl":85},"EVAL-PROMPT.md","REFERENCE","参考文档",4359,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fcassandra\u002Fblob\u002Ftrunk\u002F.claude\u002Fskills\u002Fshallow-review\u002FEVAL-PROMPT.md",{"path":87,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Fgeneral\u002Fspecialists\u002Fabsence.md",5823,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fcassandra\u002Fblob\u002Ftrunk\u002F.claude\u002Fskills\u002Fshallow-review\u002Freferences\u002Fgeneral\u002Fspecialists\u002Fabsence.md",{"path":91,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002Fgeneral\u002Fspecialists\u002Fboundary.md",5010,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fcassandra\u002Fblob\u002Ftrunk\u002F.claude\u002Fskills\u002Fshallow-review\u002Freferences\u002Fgeneral\u002Fspecialists\u002Fboundary.md",{"path":95,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002Fgeneral\u002Fspecialists\u002Fcompleteness.md",5672,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fcassandra\u002Fblob\u002Ftrunk\u002F.claude\u002Fskills\u002Fshallow-review\u002Freferences\u002Fgeneral\u002Fspecialists\u002Fcompleteness.md",{"path":99,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":100,"sourceHtmlUrl":101},"references\u002Fgeneral\u002Fspecialists\u002Fconcurrency.md",5843,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fcassandra\u002Fblob\u002Ftrunk\u002F.claude\u002Fskills\u002Fshallow-review\u002Freferences\u002Fgeneral\u002Fspecialists\u002Fconcurrency.md",{"path":103,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":104,"sourceHtmlUrl":105},"references\u002Fgeneral\u002Fspecialists\u002Flogic.md",8169,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fcassandra\u002Fblob\u002Ftrunk\u002F.claude\u002Fskills\u002Fshallow-review\u002Freferences\u002Fgeneral\u002Fspecialists\u002Flogic.md",{"path":107,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":108,"sourceHtmlUrl":109},"references\u002Fgeneral\u002Fspecialists\u002Fresources.md",6420,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fcassandra\u002Fblob\u002Ftrunk\u002F.claude\u002Fskills\u002Fshallow-review\u002Freferences\u002Fgeneral\u002Fspecialists\u002Fresources.md",[111,140,164,189,208,226],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":120,"publishedAt":51},"01M6ACCP3HAMTRVENVB5ZT9TX1","write-reproducer","Write minimal, reliable bug reproducers (repros) for any project. Use when: (1) a bug report or issue needs a test that reliably demonstrates the failure, (2) converting a described failure scenario into runnable code, (3) minimizing an existing complex test to its essential trigger conditions. Covers the full repro workflow: failure characterization, scope selection, writing the repro, verifying it fails for the right reason, and minimizing to the smallest possible trigger.","https:\u002F\u002Fgithub.com\u002Fapache\u002Fcassandra\u002Fblob\u002Ftrunk\u002F.claude\u002Fskills\u002Fwrite-reproducer\u002FSKILL.md",[117],{"categoryNo":118,"categoryName":119,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",[121,122,123,124,125,126,127,128,129,130,131,42,132,133,134,38,135,136,137,138,32,139],"write reproducer","reproducer","write","writing","workflow","test","bug report","code","report","repro","minimal","issue","selection","project","essential","scenario","trigger","scope","when",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":146,"publishedAt":51},"01M6ACCJXC5SQSQ2K3APRC6GQV","tla-plus","Create, run, and verify TLA+ and PlusCal formal specifications. Use for modeling distributed systems, protocols, concurrent algorithms, state machines. Can compose specs from code, find divergences between spec and implementation, spot concurrency bugs and invariant violations. Use when asked to \"write a TLA+ spec\", \"model check\", \"verify protocol\", \"find race conditions\", or \"formal verification\".","https:\u002F\u002Fgithub.com\u002Fapache\u002Fcassandra\u002Fblob\u002Ftrunk\u002F.claude\u002Fskills\u002Ftla-plus\u002FSKILL.md",[],[147,148,149,150,151,128,48,152,153,154,47,155,123,156,157,158,159,160,161,32,162,163,139],"tla plus","spec","distributed","create","run","protocol","verification","protocols","model","use","compose","algorithms","modeling","state machines","TLA+","bugs","model check",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":168,"categories":169,"keywords":173,"publishedAt":51},"01M6ACCF4FQX1PFWXEDHQ8YRF9","targeted-review","Findings-driven targeted code review. Understands the patch via patch-explainer and surrounding code via codebase-analysis, then consults a catalog of bug patterns (~11 categories under references\u002Fcategories\u002F). Picks only categories whose diff-signals match the patch and items whose \"look for\" hints match actual code shapes, groups them by review focus (function\u002Ffile\u002Ffeature), and spawns parallel subagents — each with a tight scope and selective checklist. Use for medium-to-large patches (50-1000 LOC) as a focused alternative to whole-patch ensemble or whole-file deep review. Triggers on: \"review this patch\u002Fdiff\u002Fchange\", \"find bugs in this change\", \"scoped review\", \"what could go wrong here\", \"review using findings\", or proactive PR review.","https:\u002F\u002Fgithub.com\u002Fapache\u002Fcassandra\u002Fblob\u002Ftrunk\u002F.claude\u002Fskills\u002Ftargeted-review\u002FSKILL.md",[170],{"categoryNo":171,"categoryName":172,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查",[30,174,175,176,177,178,179,128,180,46,44,181,182,43,42,183,184,185,186,39,187,138,188],"targeted review","code review","go","change","pr review","pr","deep review","subagents","only","references","patterns","focus","signals","as","categories",{"skillNo":190,"name":191,"nameZh":6,"description":192,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":193,"categories":194,"keywords":196,"publishedAt":51},"01M6ACC9R6QCJN390ERFPN8VA0","patch-explainer","Deep code analysis with ASCII visualizations showing structure, flow, and state transitions. Use when analyzing patches\u002Fdiffs, explaining classes or subsystems, understanding code architecture, reviewing changes for inconsistencies, or when asked to visualize how code works. Provides before\u002Fafter diagrams, data\u002Fcontrol flow, concurrency analysis, assumptions, and failure modes. Triggers on explain this patch\u002Fcode\u002Fclass, how does X work, show me the flow, visualize this change, code review requests, or proactive analysis during PR reviews.","https:\u002F\u002Fgithub.com\u002Fapache\u002Fcassandra\u002Fblob\u002Ftrunk\u002F.claude\u002Fskills\u002Fpatch-explainer\u002FSKILL.md",[195],{"categoryNo":171,"categoryName":172,"taxonomyType":21,"taxonomyTypeDesc":22},[197,198,43,175,30,50,199,177,200,179,128,48,46,201,202,203,204,205,206,39,207,33,139],"patch explainer","explainer","visualize","architecture","show me","work","diagrams","show","me","structure","code analysis",{"skillNo":209,"name":210,"nameZh":6,"description":211,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":212,"categories":213,"keywords":215,"publishedAt":51},"01M6ACC7FFFSHENM9P5SGMWGQJ","mega-review","Multi-pass deep code review for large patches (1000+ LOC) that maximizes real bug detection. Orchestrates targeted-review, shallow-review, and deep-review in parallel across all HIGH and MEDIUM risk files and commits: understands the feature holistically, splits by file and commit, runs deep review on every HIGH\u002FMEDIUM file, targeted review across the same scope, and per-commit shallow review, followed by cross-cut consistency checks. Use when: reviewing a large patch (feature branch, multi-commit, or single large diff, 1000+ LOC), doing a thorough pre-merge review, or when shallower reviews miss bugs due to patch size. Triggers on: \"review this branch\", \"review these commits\", \"review this feature\", \"mega review\", \"thorough review\", \"full review of X commits\", or when the user specifies a commit range or feature for review.","https:\u002F\u002Fgithub.com\u002Fapache\u002Fcassandra\u002Fblob\u002Ftrunk\u002F.claude\u002Fskills\u002Fmega-review\u002FSKILL.md",[214],{"categoryNo":171,"categoryName":172,"taxonomyType":21,"taxonomyTypeDesc":22},[30,216,175,217,218,128,180,219,43,42,220,221,39,38,222,138,223,33,224,225,139],"mega review","commit","merge","branch","files","across","cut","full review","pre-merge","merge review",{"skillNo":227,"name":228,"nameZh":6,"description":229,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":230,"categories":231,"keywords":232,"publishedAt":51},"01M6ACC5GEW6PB6RYG58VJ58SQ","heatmap","Use git heatmap analysis to identify high-churn files and lines as candidates for thorough review or bug hunting. Works for PR reviews, security audits, bug hunts, or any code analysis task.","https:\u002F\u002Fgithub.com\u002Fapache\u002Fcassandra\u002Fblob\u002Ftrunk\u002F.claude\u002Fskills\u002Fheatmap\u002FSKILL.md",[],[228,30,233,179,128,234,46,156,42,220,235,187,207,236,237,238,33,239,32],"security","git","task","churn","heatmap analysis","hunting","high"]