• $ARGUMENTS

  may contain:

  • --full

    — Force a full rebuild, ignoring any existing graph
  • A directory path — Scope analysis to a specific subdirectory

1. Set

   PROJECT_ROOT

   to the current working directory.
2. Get the current git commit hash:
   bash

   git rev-parse HEAD

3. Create the intermediate output directory:
   bash

   mkdir -p $PROJECT_ROOT/.understand-anything/intermediate

4. Check if

   $PROJECT_ROOT/.understand-anything/knowledge-graph.json

   exists. If it does, read it.
5. Check if

   $PROJECT_ROOT/.understand-anything/meta.json

   exists. If it does, read it to get

   gitCommitHash

   .
6. Decision logic:

   Condition	Action
   --full flag in $ARGUMENTS	Full analysis (all phases)
   No existing graph or meta	Full analysis (all phases)
   Existing graph + unchanged commit hash	Report "Graph is up to date" and STOP
   Existing graph + changed files	Incremental update (re-analyze changed files only)

   For incremental updates, get the changed file list:
   bash

   git diff <lastCommitHash>..HEAD --name-only

   If this returns no files, report "Graph is up to date" and STOP.

Scan this project directory to discover all source files, detect languages and frameworks. Project root:

$PROJECT_ROOT

Write output to:

$PROJECT_ROOT/.understand-anything/intermediate/scan-result.json

$PROJECT_ROOT/.understand-anything/intermediate/scan-result.json

• Project name, description
• Languages, frameworks
• File list with line counts
• Complexity estimate

Analyze these source files and produce GraphNode and GraphEdge objects. Project root:

$PROJECT_ROOT

Project:

<projectName>

Languages:

<languages>

Batch index:

<batchIndex>

Write output to:

$PROJECT_ROOT/.understand-anything/intermediate/batch-<batchIndex>.json

All project files (for import resolution):

<full file path list from scan>

Files to analyze in this batch:

1. <path>

   (<sizeLines> lines)

2. <path>

   (<sizeLines> lines) ...

batch-<N>.json

• Combine all

  nodes

  arrays. If duplicate node IDs exist, keep the later occurrence.
• Combine all

  edges

  arrays. Deduplicate by the composite key

  source + target + type

  .

1. Remove old nodes whose

   filePath

   matches any changed file
2. Remove old edges whose

   source

   or

   target

   references a removed node
3. Add new nodes and edges from the fresh analysis

• Remove any edge whose

  source

  or

  target

  references a node ID that does not exist in the merged node set
• Remove duplicate node IDs (keep the last occurrence)
• Log any removed edges or nodes for the final summary

Analyze this codebase's structure to identify architectural layers. Project root:

$PROJECT_ROOT

Write output to:

$PROJECT_ROOT/.understand-anything/intermediate/layers.json

Project:

<projectName>

—

<projectDescription>

File nodes:

json

[list of {id, name, filePath, summary, tags} for all file-type nodes]

Import edges:

json

[list of edges with type "imports"]

$PROJECT_ROOT/.understand-anything/intermediate/layers.json

Create a guided learning tour for this codebase. Project root:

$PROJECT_ROOT

Write output to:

$PROJECT_ROOT/.understand-anything/intermediate/tour.json

Project:

<projectName>

—

<projectDescription>

Languages:

<languages>

Nodes (summarized):

json

[list of {id, name, filePath, summary, type} for key nodes]

Layers:

json

[layers from Phase 4]

Key edges:

json

[imports and calls edges]

$PROJECT_ROOT/.understand-anything/intermediate/tour.json

{
  "version": "1.0.0",
  "project": {
    "name": "<projectName>",
    "languages": ["<languages>"],
    "frameworks": ["<frameworks>"],
    "description": "<projectDescription>",
    "analyzedAt": "<ISO 8601 timestamp>",
    "gitCommitHash": "<commit hash from Phase 0>"
  },
  "nodes": [<all merged nodes from Phase 3>],
  "edges": [<all merged edges from Phase 3>],
  "layers": [<layers from Phase 4>],
  "tour": [<steps from Phase 5>]
}

1. Write the assembled graph to

   $PROJECT_ROOT/.understand-anything/intermediate/assembled-graph.json

   .
2. Dispatch the graph-reviewer agent with this prompt:

   Validate the knowledge graph at

   $PROJECT_ROOT/.understand-anything/intermediate/assembled-graph.json

   . Project root:

   $PROJECT_ROOT

   Read the file and validate it for completeness and correctness. Write output to:

   $PROJECT_ROOT/.understand-anything/intermediate/review.json

3. After the agent completes, read

   $PROJECT_ROOT/.understand-anything/intermediate/review.json

   .
4. If

   approved: false

   :
   • Review the

     issues

     list
   • Apply automated fixes where possible:
     • Remove edges with dangling references
     • Fill missing required fields with sensible defaults (e.g., empty

       tags

       ->

       ["untagged"]

       , empty

       summary

       ->

       "No summary available"

       )
     • Remove nodes with invalid types
   • If critical issues remain after one fix attempt, save the graph anyway but include the warnings in the final report
5. If

   approved: true

   : Proceed to Phase 7.

1. Write the final knowledge graph to

   $PROJECT_ROOT/.understand-anything/knowledge-graph.json

   .
2. Write metadata to

   $PROJECT_ROOT/.understand-anything/meta.json

   :
   json

   {
     "lastAnalyzedAt": "<ISO 8601 timestamp>",
     "gitCommitHash": "<commit hash>",
     "version": "1.0.0",
     "analyzedFiles": <number of files analyzed>
   }

3. Clean up intermediate files:
   bash

   rm -rf $PROJECT_ROOT/.understand-anything/intermediate

4. Report a summary to the user containing:
   • Project name and description
   • Files analyzed / total files
   • Nodes created (broken down by type: file, function, class)
   • Edges created (broken down by type)
   • Layers identified (with names)
   • Tour steps generated (count)
   • Any warnings from the reviewer
   • Path to the output file:

     $PROJECT_ROOT/.understand-anything/knowledge-graph.json

5. Automatically launch the dashboard by invoking the

   /understand-dashboard

   skill.

• If any agent dispatch fails, retry once with the same prompt plus additional context about the failure.
• If it fails a second time, skip that phase and continue with partial results.
• ALWAYS save partial results — a partial graph is better than no graph.
• Report any skipped phases or errors in the final summary so the user knows what happened.
• NEVER silently drop errors. Every failure must be visible in the final report.