{"id":"understand-chat","name":"understand-chat","summary":"コードベースについて質問したり、ナレッジグラフを使ってコードを理解したいときに使ってください","body":"# /understand-chat\n\nAnswer questions about this codebase using the knowledge graph in the project's data directory (`.ua/knowledge-graph.json`, or the legacy `.understand-anything/knowledge-graph.json` when that directory is present).\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/knowledge 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. **Resolve the data directory `$UA_DIR`.** Run `UA_DIR=$([ -d .understand-anything ] && echo .understand-anything || echo .ua)` — this is the legacy `.understand-anything/` when it already exists, otherwise the new `.ua/`. Check that `$UA_DIR/knowledge-graph.json` exists in the current project root. If not, tell the user to run `/understand` first.\n\n2. **Check graph freshness before using graph-derived context**:\n   - Read `project.gitCommitHash` from the graph metadata as `GRAPH_COMMIT_RAW`. Resolve it as a commit before using it in any Git diff, then compare it with `git rev-parse HEAD` and inspect project-scoped committed and working-tree changes from the project root:\n     ```bash\n     GRAPH_COMMIT=$(git rev-parse --verify --end-of-options \"${GRAPH_COMMIT_RAW}^{commit}\" 2>/dev/null)\n     git rev-parse HEAD\n     git diff --name-only \"$GRAPH_COMMIT\" HEAD -- .\n     git diff --cached --name-only -- .\n     git diff --name-only -- .\n     git ls-files --others --exclude-standard -- .\n     ```\n   - The `-- .` pathspec is required: commits that only touch a sibling monorepo project must not make this graph stale. A hash mismatch alone is not stale when the project diff is empty.\n   - Ignore the selected data directory (`.ua/` or legacy `.understand-anything/`) in every command's output because it contains generated graph artifacts, not project source drift.\n   - If the committed diff or any working-tree command reports project files, warn before answering that graph-derived context may omit those changes. Suggest: Run `/understand` to refresh the graph.\n   - Run the commit diff only when `GRAPH_COMMIT_RAW` resolves successfully. If the graph commit or Git metadata is missing, invalid, or unavailable, give a brief best-effort warning and continue instead of blocking.\n\n3. **Read project metadata only** — use Grep or Read with a line limit to extract just the `\"project\"` section from the top of the file for context (name, description, languages, frameworks).\n\n4. **Search for relevant nodes** — use Grep to search the knowledge graph file for the user's query keywords: \"$ARGUMENTS\"\n   - Search `\"name\"` fields: `grep -i \"query_keyword\"` in the graph file\n   - Search `\"summary\"` fields for semantic matches\n   - Search `\"tags\"` arrays for topic matches\n   - Note the `id` values of all matching nodes\n\n5. **Find connected edges** — for each matched node ID, Grep for that ID in the `edges` section to find:\n   - What it imports or depends on (downstream)\n   - What calls or imports it (upstream)\n   - This gives you the 1-hop subgraph around the query\n\n6. **Read layer context** — Grep for `\"layers\"` to understand which architectural layers the matched nodes belong to.\n\n7. **Answer the query** using only the relevant subgraph:\n   - Reference specific files, functions, and relationships from the graph\n   - Explain which layer(s) are relevant and why\n   - Be concise but thorough — link concepts to actual code locations\n   - If the query doesn't match any nodes, say so and suggest related terms from the graph","author":"@Egonex-AI","ownerProfile":null,"authorContacts":null,"sourceUrl":"https://github.com/Egonex-AI/Understand-Anything/tree/main/understand-anything-plugin/skills/understand-chat","license":"MIT","category":"writing","lang":"en","tokens":1085,"stars":0,"calls30d":2,"claimed":false,"visibility":"public","origin":"crawler","version":"0.1.0","createdAt":"2026-08-22","updatedAt":"2026-08-22","files":[],"requires":{"mcp":[],"tools":[]},"safety":{"flags":[],"scannedAt":"2026-08-22","hasScripts":false,"networkEndpoints":[]}}