Understand Diff

Before you start: read this whole install prompt, tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead before you do anything else. Prerequisites — Use-time prerequisite, disclosed up front: this skill is one of the Understand-Anything plugin's skills. It assumes the Understand-Anything plugin is installed and its core is built (pnpm install in the plugin, then building packages/core, the @understand-anything/core package) — installing this listing only copies the skill folder below; it does not install or build the plugin. The skill works locally on the knowledge graph in your project's data directory (.ua/knowledge-graph.json, or the legacy .understand-anything/knowledge-graph.json when that directory already exists). No account, key or payment is needed to install this listing. Install "Understand Diff" for me. It analyzes the current code changes against the knowledge graph produced by the separate understand skill: it lists the changed files from git, checks the graph's freshness, finds the graph nodes for the changed files and their one-hop neighbours (the affected components), identifies the touched architectural layers, and produces a structured analysis (changed components, affected components, affected layers, risk assessment). It then writes a diff-overlay.json into the project's data directory so the dashboard can visualize the change. If no graph exists, it tells you to run /understand first. Its folder is a single SKILL.md file. Repository: https://github.com/Egonex-AI/Understand-Anything (the skill is the whole understand-anything-plugin/skills/understand-diff/ folder at the pinned commit: SKILL.md, 1 file in total) Pinned version: install the code at commit e24fcf6d371bcfa529bc110bacb1bb43de1b8d33 exactly. Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Clone https://github.com/Egonex-AI/Understand-Anything into a temporary folder, check out commit e24fcf6d371bcfa529bc110bacb1bb43de1b8d33, and copy the understand-anything-plugin/skills/understand-diff/ folder from that checkout. Then compare every file in the folder with the fingerprints recorded for this listing on 2026-10-22: [FINGERPRINTS] - SKILL.md: SHA-256 fc8dc1b216ee1a480daff421c41c27218d7a0db881d35d0c22e9858de5189379 If a file does not match, it changed since the listing was prepared: do not install it yet, tell me what you found and let me decide. 2. Read SKILL.md in full, and tell me in plain words: what the skill does when used, what it connects to, whether it reads or sends any personal information or credentials, and anything that seems unusual. Stop on any red flag and tell me before going further. Confirm these points from the files: - The folder holds 1 file only: SKILL.md (5,781 bytes, frontmatter name understand-diff). There is no script, no companion file and no other code in it. - Nothing is sent anywhere during installation itself; the only download at install time is the skill folder from GitHub at the pinned commit. - At use time it works locally on my own repository: git diff commands to list changed files, reads of the knowledge graph in my project's data directory (.ua/knowledge-graph.json, or legacy .understand-anything/knowledge-graph.json) produced beforehand by the separate understand skill, and one write — the diff-overlay.json it generates in that same data directory for the dashboard. It reads no personal information or credentials and sends nothing anywhere. - Do not analyze any diff, do not read any graph, and do not use the skill in any way during this install: using it is a separate step that only starts when I ask for it later. 3. When I say "yes, install", install it as a skill: copy the whole understand-diff folder into the agent's skills directory, in a folder named exactly "understand-diff", keeping its 1 file in their original relative layout (SKILL.md at its root). 4. Verify with no network calls: frontmatter valid (name: understand-diff), the 1 file in place with matching fingerprints. Do not run anything from the folder and do not use the skill to verify. 5. Report what was installed, where, and what I still need to do myself (for example: that the Understand-Anything plugin must be installed with its core built (pnpm install plus building packages/core), that a knowledge graph must already have been produced by the separate understand skill, and that using this skill is a separate step that only starts when I ask for it later). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.