Skill Introduction

Overview

Use when you need to ask questions about a codebase or understand code using a knowledge graph

Core value

Turns reusable Development know-how into an installable skill, helping users complete github, community, antigravity-skills, business-knowledge work faster.

Target users

Developers, testers, and maintainers who handle Development tasks in Focus Code.
Teams that already trust workflows or content from Lum1104.
Users who want standardized prompts, steps, or conventions instead of repeating setup work.

Best practices

Read the skill content first to confirm required inputs, expected outputs, and dependencies.
Try it on a small task before relying on it for critical work.
Add project-specific constraints such as coding style, target platform, test expectations, and delivery format.
For external sources, verify the source link, version, and recent maintenance activity.

Best use cases

Tasks related to github, community, antigravity-skills, business-knowledge that need a reusable execution flow.
Converting a community repo, team convention, or personal workflow into day-to-day assistance.
Starting from a proven skill instead of writing prompts or procedures from scratch.

Limits and boundaries

Results depend on the quality of the original skill content and may need human correction.
It does not replace code review, tests, security review, or professional judgment.
External tools, APIs, account permissions, and local dependencies still need separate setup.

Differentiation

Structured around Development, making it easier to discover and reuse than loose prompt snippets.
Marked as GitHub, which helps users judge trust and maintenance expectations.
Keeps the original source link available for repository, documentation, or discussion follow-up.
Tagged with github, community, antigravity-skills, business-knowledge, so it can be filtered by concrete task intent.

Install and use

Install

Copy Install Command

focus install understand-chat-f0c28a

View source

Detail Preview

SKILL.md

Primary filemarkdown3 KB

name: understand-chat description: Use when you need to ask questions about a codebase or understand code using a knowledge graph argument-hint: [query]

/understand-chat

Answer questions about this codebase using the knowledge graph at .understand-anything/knowledge-graph.json.

Graph Structure Reference

The knowledge graph JSON has this structure:

project — {name, description, languages, frameworks, analyzedAt, gitCommitHash}
nodes[] — each has {id, type, name, filePath, summary, tags[], complexity, languageNotes?}
- Node types: file, function, class, module, concept
- IDs: file:path, function:path:name, class:path:name
edges[] — each has {source, target, type, direction, weight}
- Key types: imports, contains, calls, depends_on
layers[] — each has {id, name, description, nodeIds[]}
tour[] — each has {order, title, description, nodeIds[]}

How to Read Efficiently

Use Grep to search within the JSON for relevant entries BEFORE reading the full file
Only read sections you need — don't dump the entire graph into context
Node names and summaries are the most useful fields for understanding
Edges tell you how components connect — follow imports and calls for dependency chains

Instructions

Check that .understand-anything/knowledge-graph.json exists in the current project root. If not, tell the user to run /understand first.
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).
Search for relevant nodes — use Grep to search the knowledge graph file for the user's query keywords: "$ARGUMENTS"
- Search "name" fields: grep -i "query_keyword" in the graph file
- Search "summary" fields for semantic matches
- Search "tags" arrays for topic matches
- Note the id values of all matching nodes
Find connected edges — for each matched node ID, Grep for that ID in the edges section to find:
- What it imports or depends on (downstream)
- What calls or imports it (upstream)
- This gives you the 1-hop subgraph around the query
Read layer context — Grep for "layers" to understand which architectural layers the matched nodes belong to.
Answer the query using only the relevant subgraph:
- Reference specific files, functions, and relationships from the graph
- Explain which layer(s) are relevant and why
- Be concise but thorough — link concepts to actual code locations
- If the query doesn't match any nodes, say so and suggest related terms from the graph

understand chat