[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M756NCF0HHCSJTMDV85G7KR2":3,"skill-same:01M756NCF0HHCSJTMDV85G7KR2":45},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M756NCF0HHCSJTMDV85G7KR2","understand-diff",null,"Use when you need to analyze git diffs or pull requests to understand what changed, affected components, and risks","Ikeu-1030\u002FiRun","Ikeu-1030","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F229719040?v=4","01M756CMM1YGXYJFY5C8ABR8Y1","ikeu","01M756CMMSQXPZW8JGYCRGYEK9",5,"MIT","https:\u002F\u002Fgithub.com\u002FIkeu-1030\u002FiRun\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Funderstand-anything\u002Funderstand-anything-plugin\u002Fskills\u002Funderstand-diff\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: understand-diff\ndescription: Use when you need to analyze git diffs or pull requests to understand what changed, affected components, and risks\n---\n\n# \u002Funderstand-diff\n\nAnalyze the current code changes against the knowledge graph at `.understand-anything\u002Fknowledge-graph.json`.\n\n## Graph Structure Reference\n\nThe knowledge graph JSON has this structure:\n- `project` — {name, description, languages, frameworks, analyzedAt, gitCommitHash}\n- `nodes[]` — each has {id, type, name, filePath?, summary, tags[], complexity, languageNotes?}\n  - Code node types: file, function, class, module, concept\n  - Non-code node types: config, document, service, table, endpoint, pipeline, schema, resource\n  - Domain\u002Fknowledge node types: domain, flow, step, article, entity, topic, claim, source\n  - IDs use the node type as prefix, e.g. `file:path`, `function:path:name`, `config:path`, `article:path`\n- `edges[]` — each has {source, target, type, direction, weight}\n  - Key types: imports, contains, calls, depends_on, configures, documents, deploys, triggers, contains_flow, flow_step, related, cites\n- `layers[]` — each has {id, name, description, nodeIds[]}\n- `tour[]` — each has {order, title, description, nodeIds[]}\n\n## How to Read Efficiently\n\n1. Use Grep to search within the JSON for relevant entries BEFORE reading the full file\n2. Only read sections you need — don't dump the entire graph into context\n3. Node names and summaries are the most useful fields for understanding\n4. Edges tell you how components connect — follow imports and calls for dependency chains\n\n## Instructions\n\n1. Check that `.understand-anything\u002Fknowledge-graph.json` exists. If not, tell the user to run `\u002Funderstand` first.\n\n2. **Get the changed files list** (do NOT read the graph yet):\n   - If on a branch with uncommitted changes: `git diff --name-only`\n   - If on a feature branch: `git diff main...HEAD --name-only` (or the base branch)\n   - If the user specifies a PR number: get the diff from that PR\n\n3. **Read project metadata only** — use Grep or Read with a line limit to extract just the `\"project\"` section for context.\n\n4. **Find nodes for changed files** — for each changed file path, use Grep to search the knowledge graph for:\n   - Nodes with matching `\"filePath\"` values (e.g., `grep \"changed\u002Ffile\u002Fpath\"`)\n   - This finds file-level nodes (including non-code types) AND function\u002Fclass nodes defined in those files\n   - Note the `id` values of all matched nodes\n\n5. **Find connected edges (1-hop)** — for each matched node ID, Grep for that ID in the edges to find:\n   - What imports or depends on the changed nodes (upstream callers)\n   - What the changed nodes import or call (downstream dependencies)\n   - These are the \"affected components\" — things that might break or need updating\n\n6. **Identify affected layers** — Grep for the matched node IDs in the `\"layers\"` section to determine which architectural layers are touched.\n\n7. **Provide structured analysis**:\n   - **Changed Components**: What was directly modified (with summaries from matched nodes)\n   - **Affected Components**: What might be impacted (from 1-hop edges)\n   - **Affected Layers**: Which architectural layers are touched and cross-layer concerns\n   - **Risk Assessment**: Based on node `complexity` values, number of cross-layer edges, and blast radius (number of affected components)\n   - Suggest what to review carefully and any potential issues\n\n8. **Write diff overlay for dashboard** — after producing the analysis, write the diff data to `.understand-anything\u002Fdiff-overlay.json` so the dashboard can visualize changed and affected components. The file contains:\n   ```json\n   {\n     \"version\": \"1.0.0\",\n     \"baseBranch\": \"\u003Cthe base branch used>\",\n     \"generatedAt\": \"\u003CISO timestamp>\",\n     \"changedFiles\": [\"\u003Clist of changed file paths>\"],\n     \"changedNodeIds\": [\"\u003Cnode IDs from step 4>\"],\n     \"affectedNodeIds\": [\"\u003Cnode IDs from step 5, excluding changedNodeIds>\"]\n   }\n   ```\n   After writing, tell the user they can run `\u002Funderstand-anything:understand-dashboard` to see the diff overlay visually.\n","# \u002Funderstand-diff\n\nAnalyze the current code changes against the knowledge graph at `.understand-anything\u002Fknowledge-graph.json`.\n\n## Graph Structure Reference\n\nThe knowledge graph JSON has this structure:\n- `project` — {name, description, languages, frameworks, analyzedAt, gitCommitHash}\n- `nodes[]` — each has {id, type, name, filePath?, summary, tags[], complexity, languageNotes?}\n  - Code node types: file, function, class, module, concept\n  - Non-code node types: config, document, service, table, endpoint, pipeline, schema, resource\n  - Domain\u002Fknowledge node types: domain, flow, step, article, entity, topic, claim, source\n  - IDs use the node type as prefix, e.g. `file:path`, `function:path:name`, `config:path`, `article:path`\n- `edges[]` — each has {source, target, type, direction, weight}\n  - Key types: imports, contains, calls, depends_on, configures, documents, deploys, triggers, contains_flow, flow_step, related, cites\n- `layers[]` — each has {id, name, description, nodeIds[]}\n- `tour[]` — each has {order, title, description, nodeIds[]}\n\n## How to Read Efficiently\n\n1. Use Grep to search within the JSON for relevant entries BEFORE reading the full file\n2. Only read sections you need — don't dump the entire graph into context\n3. Node names and summaries are the most useful fields for understanding\n4. Edges tell you how components connect — follow imports and calls for dependency chains\n\n## Instructions\n\n1. Check that `.understand-anything\u002Fknowledge-graph.json` exists. If not, tell the user to run `\u002Funderstand` first.\n\n2. **Get the changed files list** (do NOT read the graph yet):\n   - If on a branch with uncommitted changes: `git diff --name-only`\n   - If on a feature branch: `git diff main...HEAD --name-only` (or the base branch)\n   - If the user specifies a PR number: get the diff from that PR\n\n3. **Read project metadata only** — use Grep or Read with a line limit to extract just the `\"project\"` section for context.\n\n4. **Find nodes for changed files** — for each changed file path, use Grep to search the knowledge graph for:\n   - Nodes with matching `\"filePath\"` values (e.g., `grep \"changed\u002Ffile\u002Fpath\"`)\n   - This finds file-level nodes (including non-code types) AND function\u002Fclass nodes defined in those files\n   - Note the `id` values of all matched nodes\n\n5. **Find connected edges (1-hop)** — for each matched node ID, Grep for that ID in the edges to find:\n   - What imports or depends on the changed nodes (upstream callers)\n   - What the changed nodes import or call (downstream dependencies)\n   - These are the \"affected components\" — things that might break or need updating\n\n6. **Identify affected layers** — Grep for the matched node IDs in the `\"layers\"` section to determine which architectural layers are touched.\n\n7. **Provide structured analysis**:\n   - **Changed Components**: What was directly modified (with summaries from matched nodes)\n   - **Affected Components**: What might be impacted (from 1-hop edges)\n   - **Affected Layers**: Which architectural layers are touched and cross-layer concerns\n   - **Risk Assessment**: Based on node `complexity` values, number of cross-layer edges, and blast radius (number of affected components)\n   - Suggest what to review carefully and any potential issues\n\n8. **Write diff overlay for dashboard** — after producing the analysis, write the diff data to `.understand-anything\u002Fdiff-overlay.json` so the dashboard can visualize changed and affected components. The file contains:\n   ```json\n   {\n     \"version\": \"1.0.0\",\n     \"baseBranch\": \"\u003Cthe base branch used>\",\n     \"generatedAt\": \"\u003CISO timestamp>\",\n     \"changedFiles\": [\"\u003Clist of changed file paths>\"],\n     \"changedNodeIds\": [\"\u003Cnode IDs from step 4>\"],\n     \"affectedNodeIds\": [\"\u003Cnode IDs from step 5, excluding changedNodeIds>\"]\n   }\n   ```\n   After writing, tell the user they can run `\u002Funderstand-anything:understand-dashboard` to see the diff overlay visually.\n",{"name":5,"description":7},"main","14d19341a5ae6e5a3c751328fcc273395da5bd21",".claude\u002Fskills\u002Funderstand-anything\u002Funderstand-anything-plugin\u002Fskills\u002Funderstand-diff","https:\u002F\u002Fgithub.com\u002FIkeu-1030\u002FiRun","https:\u002F\u002Fgithub.com\u002FIkeu-1030","Action shatters illusion\u002F","2026-07-02 15:19:58",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add Ikeu-1030\u002FiRun --skill understand-diff",{"tool":37,"command":38},"bunx","bunx skills add Ikeu-1030\u002FiRun --skill understand-diff",{"tool":40,"command":41},"pnpm","pnpm dlx skills add Ikeu-1030\u002FiRun --skill understand-diff","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FIkeu-1030\u002FiRun\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Funderstand-anything\u002Funderstand-anything-plugin\u002Fskills\u002Funderstand-diff\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M756NR65N494G30JZP84MS7R","understand","Analyze a codebase to produce an interactive knowledge graph for understanding architecture, components, and relationships","https:\u002F\u002Fgithub.com\u002FIkeu-1030\u002FiRun\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Funderstand-anything\u002Funderstand-anything-plugin\u002Fskills\u002Funderstand\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M756NPH7BMV8655NPXER0ZAS","understand-onboard","Use when you need to generate an onboarding guide for new team members joining a project","https:\u002F\u002Fgithub.com\u002FIkeu-1030\u002FiRun\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Funderstand-anything\u002Funderstand-anything-plugin\u002Fskills\u002Funderstand-onboard\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M756NM7K2DP7KD475N4S3ZXD","understand-knowledge","Analyze a Karpathy-pattern LLM wiki knowledge base and generate an interactive knowledge graph with entity extraction, implicit relationships, and topic clustering.","https:\u002F\u002Fgithub.com\u002FIkeu-1030\u002FiRun\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Funderstand-anything\u002Funderstand-anything-plugin\u002Fskills\u002Funderstand-knowledge\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M756NJPJADZ13YRP1D9PEVEF","understand-explain","Use when you need a deep-dive explanation of a specific file, function, or module in the codebase","https:\u002F\u002Fgithub.com\u002FIkeu-1030\u002FiRun\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Funderstand-anything\u002Funderstand-anything-plugin\u002Fskills\u002Funderstand-explain\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M756NF79MR3DD69W7XJAT2PB","understand-domain","Extract business domain knowledge from a codebase and generate an interactive domain flow graph. Works standalone (lightweight scan) or derives from an existing \u002Funderstand knowledge graph.","https:\u002F\u002Fgithub.com\u002FIkeu-1030\u002FiRun\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Funderstand-anything\u002Funderstand-anything-plugin\u002Fskills\u002Funderstand-domain\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M756NA0ZYHV493C2DHEGG1TF","understand-dashboard","Launch the interactive web dashboard to visualize a codebase's knowledge graph","https:\u002F\u002Fgithub.com\u002FIkeu-1030\u002FiRun\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Funderstand-anything\u002Funderstand-anything-plugin\u002Fskills\u002Funderstand-dashboard\u002FSKILL.md",[],[]]