[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ACC5GEW6PB6RYG58VJ58SQ":3,"skill-same:01M6ACC5GEW6PB6RYG58VJ58SQ":72},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":48,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":6,"updatedAt":51,"install":52,"resources":65},"01M6ACC5GEW6PB6RYG58VJ58SQ","heatmap",null,"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.","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\u002Fheatmap\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36],"files","for","high","reviews","hunting","heatmap analysis","churn","code analysis","as","task","review","bug","use","analysis","git","code","pr","security","2026-11-10 10:12:30",false,"---\nname: heatmap\nversion: \"1.0.0\"\ndescription: 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.\n---\n\n# Heatmap-Guided Review\n\nUse the bundled `heatmap.py` script to identify the hottest (most frequently and recently changed) code in a repository, then focus review effort on those areas. Hot code is statistically more likely to contain bugs: it changes often, accumulates complexity, and is where active development risk concentrates.\n\n## When to use\n\nInvoke this skill whenever you want to prioritize where to look in a codebase — during PR reviews, bug hunts, security audits, onboarding exploration, or any task where you need to decide which files and lines deserve the closest attention.\n\n## Prerequisites\n\n- Python 3 must be available.\n- The target must be a git repository.\n- The heatmap script is bundled with this skill at `~\u002F.claude\u002Fskills\u002Fheatmap\u002Fheatmap.py`. All commands below use `HEATMAP` as a placeholder:\n  ```bash\n  HEATMAP=\"$HOME\u002F.claude\u002Fskills\u002Fheatmap\u002Fheatmap.py\"\n  ```\n  If `heatmap` is available on PATH, you may use that instead.\n\n## Workflow\n\n### Step 1: Determine the repository path and scope\n\nFigure out the git repository root. If the user provided a repo path, use that. If working in a repo already, use the current directory. If reviewing a PR, determine which files were changed.\n\n```bash\nHEATMAP=\"$HOME\u002F.claude\u002Fskills\u002Fheatmap\u002Fheatmap.py\"\n# Find the repo root\ngit -C \u003Cpath> rev-parse --show-toplevel\n```\n\n### Step 2: Run repo-level heatmap\n\nGet the hottest files in the repository. Use `--json` for machine-readable output. Adjust `--top` based on context (20-50 for a broad scan, more for large repos).\n\n```bash\npython3 \"$HEATMAP\" repo --json --top 50 \u003Crepo_path>\n```\n\nThis returns JSON array of objects with: `path`, `heat`, `commits`, `last_modified_days`.\n\n### Step 3: Cross-reference with the task context\n\n**For PR reviews:** Intersect the heatmap results with the files changed in the PR. Files that are both changed in the PR AND high on the heatmap are the highest-priority review targets — they are already complex\u002Fvolatile and the PR is adding more changes to them.\n\n```bash\n# Get PR changed files\ngit diff --name-only \u003Cbase_branch>...HEAD\n```\n\n**For bug hunts:** The hottest files ARE the candidates — frequent recent changes correlate with bugs. Focus on the top 10-20.\n\n**For security audits:** Filter heatmap results to security-sensitive paths (auth, crypto, input parsing, network, serialization).\n\n**For general exploration:** Use the heatmap as a map of where active development is happening.\n\n### Step 4: Run line-level heatmap on top candidates\n\nFor each high-priority file (typically 3-8 files), run the line-level heatmap to find the hottest regions within those files.\n\n```bash\npython3 \"$HEATMAP\" file --json \u003Cfile_path_relative_to_repo> \u003Crepo_path>\n```\n\nThis returns JSON array of objects with: `line`, `heat`, `content`.\n\n### Step 5: Identify hot zones\n\nFrom the line-level results, identify contiguous regions of high heat. These \"hot zones\" are where to focus review. Look for:\n\n- **Clusters of hot lines** — contiguous blocks of high-heat code indicate areas under active rework. These are prime bug candidates because:\n  - Multiple recent changes suggest the logic is not yet settled\n  - Each change is an opportunity for regression\n  - Complex interactions between recent changes may not be fully tested\n\n- **Hot lines surrounded by cold code** — surgical edits in otherwise stable code may indicate bug fixes, workarounds, or special-case handling that deserves scrutiny.\n\n- **Hot function\u002Fmethod boundaries** — if a method signature or its first few lines are hot, the contract may have changed recently, affecting all callers.\n\n### Step 6: Produce the review focus list\n\nOutput a ranked list of review targets, structured as:\n\n```\n## Heatmap Review Targets\n\n### Priority 1: \u003Cfile_path> (heat: X, commits: Y)\n- **Hot zones**: lines A-B (description of what this code does)\n- **Why it matters**: \u003Ccontext — e.g., \"most changed file in repo AND modified in this PR\">\n- **What to look for**: \u003Cspecific guidance based on the code — race conditions, edge cases, etc.>\n\n### Priority 2: ...\n```\n\n### Step 7: Deep review\n\nFor each priority target, read the hot zones and perform the actual review. The heatmap tells you WHERE to look; your expertise tells you WHAT to look for. Common patterns in hot code:\n\n- **State management bugs**: Hot code often manages complex state. Check for inconsistent updates, missing synchronization, or partial failures.\n- **Edge cases**: Frequent changes often mean edge cases keep being discovered. Look for more.\n- **Regression risk**: If code was recently fixed, check whether the fix is complete and doesn't break other paths.\n- **Missing tests**: Hot code that lacks test coverage is the highest-risk combination.\n\n## Output format\n\nAlways present findings as a prioritized list with:\n1. File path and heat metrics\n2. Specific line ranges to focus on\n3. What the hot code does (brief)\n4. What risks to look for (specific to the code, not generic)\n\n## Tips\n\n- Heat is relative — compare files against each other, not against an absolute threshold.\n- Files with high heat but few commits have large individual changes (risky). Files with high heat and many commits are under constant churn (also risky, differently).\n- `last_modified_days` close to 0 means very recent changes — highest chance of unfound bugs.\n- Use `--since` to adjust the time window. Default is 2 years. For recent bug hunts, try `--since \"6 months ago\"`.\n- The `--no-color` flag is useful when piping output, but prefer `--json` for programmatic use.\n","# Heatmap-Guided Review\n\nUse the bundled `heatmap.py` script to identify the hottest (most frequently and recently changed) code in a repository, then focus review effort on those areas. Hot code is statistically more likely to contain bugs: it changes often, accumulates complexity, and is where active development risk concentrates.\n\n## When to use\n\nInvoke this skill whenever you want to prioritize where to look in a codebase — during PR reviews, bug hunts, security audits, onboarding exploration, or any task where you need to decide which files and lines deserve the closest attention.\n\n## Prerequisites\n\n- Python 3 must be available.\n- The target must be a git repository.\n- The heatmap script is bundled with this skill at `~\u002F.claude\u002Fskills\u002Fheatmap\u002Fheatmap.py`. All commands below use `HEATMAP` as a placeholder:\n  ```bash\n  HEATMAP=\"$HOME\u002F.claude\u002Fskills\u002Fheatmap\u002Fheatmap.py\"\n  ```\n  If `heatmap` is available on PATH, you may use that instead.\n\n## Workflow\n\n### Step 1: Determine the repository path and scope\n\nFigure out the git repository root. If the user provided a repo path, use that. If working in a repo already, use the current directory. If reviewing a PR, determine which files were changed.\n\n```bash\nHEATMAP=\"$HOME\u002F.claude\u002Fskills\u002Fheatmap\u002Fheatmap.py\"\n# Find the repo root\ngit -C \u003Cpath> rev-parse --show-toplevel\n```\n\n### Step 2: Run repo-level heatmap\n\nGet the hottest files in the repository. Use `--json` for machine-readable output. Adjust `--top` based on context (20-50 for a broad scan, more for large repos).\n\n```bash\npython3 \"$HEATMAP\" repo --json --top 50 \u003Crepo_path>\n```\n\nThis returns JSON array of objects with: `path`, `heat`, `commits`, `last_modified_days`.\n\n### Step 3: Cross-reference with the task context\n\n**For PR reviews:** Intersect the heatmap results with the files changed in the PR. Files that are both changed in the PR AND high on the heatmap are the highest-priority review targets — they are already complex\u002Fvolatile and the PR is adding more changes to them.\n\n```bash\n# Get PR changed files\ngit diff --name-only \u003Cbase_branch>...HEAD\n```\n\n**For bug hunts:** The hottest files ARE the candidates — frequent recent changes correlate with bugs. Focus on the top 10-20.\n\n**For security audits:** Filter heatmap results to security-sensitive paths (auth, crypto, input parsing, network, serialization).\n\n**For general exploration:** Use the heatmap as a map of where active development is happening.\n\n### Step 4: Run line-level heatmap on top candidates\n\nFor each high-priority file (typically 3-8 files), run the line-level heatmap to find the hottest regions within those files.\n\n```bash\npython3 \"$HEATMAP\" file --json \u003Cfile_path_relative_to_repo> \u003Crepo_path>\n```\n\nThis returns JSON array of objects with: `line`, `heat`, `content`.\n\n### Step 5: Identify hot zones\n\nFrom the line-level results, identify contiguous regions of high heat. These \"hot zones\" are where to focus review. Look for:\n\n- **Clusters of hot lines** — contiguous blocks of high-heat code indicate areas under active rework. These are prime bug candidates because:\n  - Multiple recent changes suggest the logic is not yet settled\n  - Each change is an opportunity for regression\n  - Complex interactions between recent changes may not be fully tested\n\n- **Hot lines surrounded by cold code** — surgical edits in otherwise stable code may indicate bug fixes, workarounds, or special-case handling that deserves scrutiny.\n\n- **Hot function\u002Fmethod boundaries** — if a method signature or its first few lines are hot, the contract may have changed recently, affecting all callers.\n\n### Step 6: Produce the review focus list\n\nOutput a ranked list of review targets, structured as:\n\n```\n## Heatmap Review Targets\n\n### Priority 1: \u003Cfile_path> (heat: X, commits: Y)\n- **Hot zones**: lines A-B (description of what this code does)\n- **Why it matters**: \u003Ccontext — e.g., \"most changed file in repo AND modified in this PR\">\n- **What to look for**: \u003Cspecific guidance based on the code — race conditions, edge cases, etc.>\n\n### Priority 2: ...\n```\n\n### Step 7: Deep review\n\nFor each priority target, read the hot zones and perform the actual review. The heatmap tells you WHERE to look; your expertise tells you WHAT to look for. Common patterns in hot code:\n\n- **State management bugs**: Hot code often manages complex state. Check for inconsistent updates, missing synchronization, or partial failures.\n- **Edge cases**: Frequent changes often mean edge cases keep being discovered. Look for more.\n- **Regression risk**: If code was recently fixed, check whether the fix is complete and doesn't break other paths.\n- **Missing tests**: Hot code that lacks test coverage is the highest-risk combination.\n\n## Output format\n\nAlways present findings as a prioritized list with:\n1. File path and heat metrics\n2. Specific line ranges to focus on\n3. What the hot code does (brief)\n4. What risks to look for (specific to the code, not generic)\n\n## Tips\n\n- Heat is relative — compare files against each other, not against an absolute threshold.\n- Files with high heat but few commits have large individual changes (risky). Files with high heat and many commits are under constant churn (also risky, differently).\n- `last_modified_days` close to 0 means very recent changes — highest chance of unfound bugs.\n- Use `--since` to adjust the time window. Default is 2 years. For recent bug hunts, try `--since \"6 months ago\"`.\n- The `--no-color` flag is useful when piping output, but prefer `--json` for programmatic use.\n",{"name":5,"version":42,"description":7},"1.0.0","trunk","ae4e78c0ece616138963019388061efa4208f67a",".claude\u002Fskills\u002Fheatmap",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":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add apache\u002Fcassandra --skill heatmap",{"tool":58,"command":59},"bunx","bunx skills add apache\u002Fcassandra --skill heatmap",{"tool":61,"command":62},"pnpm","pnpm dlx skills add apache\u002Fcassandra --skill heatmap","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fapache\u002Fcassandra\u002Fblob\u002Ftrunk\u002F.claude\u002Fskills\u002Fheatmap\u002FSKILL.md",true,[66],{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"heatmap.py","SCRIPT","脚本",24829,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fcassandra\u002Fblob\u002Ftrunk\u002F.claude\u002Fskills\u002Fheatmap\u002Fheatmap.py",[73,104,129,155,181,199],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":84,"publishedAt":37},"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",[79],{"categoryNo":80,"categoryName":81,"taxonomyType":82,"taxonomyTypeDesc":83},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[85,86,87,88,89,90,91,34,92,93,94,30,95,96,97,98,99,100,101,102,20,103],"write reproducer","reproducer","write","writing","workflow","test","bug report","report","repro","minimal","issue","selection","project","full","essential","scenario","trigger","scope","when",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":37},"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",[],[111,112,113,114,115,34,116,117,118,119,120,121,87,31,122,123,124,125,126,20,127,128,103],"tla plus","spec","distributed","create","run","state","protocol","verification","protocols","concurrency","model","compose","algorithms","modeling","state machines","TLA+","bugs","model check",{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":138,"publishedAt":37},"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",[135],{"categoryNo":136,"categoryName":137,"taxonomyType":82,"taxonomyTypeDesc":83},"01JBSEEDCAT000000000000007","代码审查",[29,139,140,141,142,143,35,34,144,32,145,146,147,148,30,149,150,151,152,153,27,102,154],"targeted review","code review","go","change","pr review","deep review","parallel","subagents","only","patch","references","patterns","focus","signals","deep","categories",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":169,"publishedAt":37},"01M6ACCCAA36RCWAA93YDDRBX8","shallow-review","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.","https:\u002F\u002Fgithub.com\u002Fapache\u002Fcassandra\u002Fblob\u002Ftrunk\u002F.claude\u002Fskills\u002Fshallow-review\u002FSKILL.md",[161,164],{"categoryNo":162,"categoryName":163,"taxonomyType":82,"taxonomyTypeDesc":83},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":165,"categoryName":166,"taxonomyType":167,"taxonomyTypeDesc":168},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[29,170,171,172,116,120,32,173,145,148,30,174,175,176,153,98,177,178,179,180,22,20],"shallow review","diffs","triage","api","scan","deeper","pattern","resources","lens","types","quick",{"skillNo":182,"name":183,"nameZh":6,"description":184,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":185,"categories":186,"keywords":188,"publishedAt":37},"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",[187],{"categoryNo":136,"categoryName":137,"taxonomyType":82,"taxonomyTypeDesc":83},[189,190,148,140,29,171,191,142,192,35,34,116,32,193,194,195,196,197,198,153,26,22,103],"patch explainer","explainer","visualize","architecture","show me","work","diagrams","show","me","structure",{"skillNo":200,"name":201,"nameZh":6,"description":202,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":203,"categories":204,"keywords":206,"publishedAt":37},"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",[205],{"categoryNo":136,"categoryName":137,"taxonomyType":82,"taxonomyTypeDesc":83},[29,207,140,208,209,34,144,210,148,30,19,211,153,98,212,102,213,22,214,215,103],"mega review","commit","merge","branch","across","cut","full review","pre-merge","merge review"]