smartworldarafath/rea_skill

understand-chat

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

Ver código-fonte

Como usar

  1. Copie o comando e verifique o pacote antes de instalar no seu ambiente de agente.
  2. Consulte no original as ferramentas, credenciais e ambientes necessários.
  3. Descreva os dados de entrada e a entrega esperada; confira a saída com as fontes.
npx skills add https://github.com/smartworldarafath/rea_skill --skill understand-chat

Antes de começar

  • A instalação não inclui assinatura de modelo, franquia API ou acesso aos seus arquivos.
  • Estrelas e instalações indicam atividade, não um teste independente de qualidade ou segurança.
Documento original do Skill

Renderizado do repositório de origem, preservando títulos, exemplos, código, tabelas, links e imagens.

/understand-chat

Answer 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).

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?}
  • Code node types: file, function, class, module, concept
  • Non-code node types: config, document, service, table, endpoint, pipeline, schema, resource
  • Domain/knowledge node types: domain, flow, step, article, entity, topic, claim, source
  • IDs use the node type as prefix, e.g. file:path, function:path:name, config:path, article:path
  • edges[] — each has {source, target, type, direction, weight}
  • Key types: imports, contains, calls, dependson, configures, documents, deploys, triggers, containsflow, flow_step, related, cites
  • layers[] — each has {id, name, description, nodeIds[]}
  • tour[] — each has {order, title, description, nodeIds[]}

How to Read Efficiently

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

Instructions

  1. 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.
  1. Check graph freshness before using graph-derived context:
  • 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:
bash
     GRAPH_COMMIT=$(git rev-parse --verify --end-of-options "${GRAPH_COMMIT_RAW}^{commit}" 2>/dev/null)
     git rev-parse HEAD
     git diff --name-only "$GRAPH_COMMIT" HEAD -- .
     git diff --cached --name-only -- .
     git diff --name-only -- .
     git ls-files --others --exclude-standard -- .
  • 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.
  • 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.
  • 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.
  • 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.
  1. 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).
  1. 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
  1. 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
  1. Read layer context — Grep for "layers" to understand which architectural layers the matched nodes belong to.
  1. 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
do mesmo repositório

Mais Skills

Todos os Skills
smartworldarafath
Comunidade

agent-introspection-debugging

Structured self-debugging workflow for AI agent failures using capture, diagnosis, contained recovery, and introspection reports. Use when an agent run fails and you need a reproducible diagnosis instead of a retry.

Instalações / 1h
2
GitHub Stars
5
Atualizado
8 de nov.
smartworldarafath
Comunidade

agent-reach

Read-only access to internet platforms (Twitter/X, Reddit, YouTube subtitles, GitHub, LinkedIn, Bilibili, web). Use when the agent needs to search, read web links, retrieve social discussions, CVE/vulnerability intel, or when standard web search/fetch is blocked or insufficient.

Instalações / 1h
2
GitHub Stars
5
Atualizado
8 de nov.
smartworldarafath
Comunidade

agent-sort

Build an evidence-backed ECC install plan for a specific repo by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes. Use when ECC should be trimmed to what a project actually needs instead of loading the full bundle.

Instalações / 1h
2
GitHub Stars
5
Atualizado
8 de nov.
smartworldarafath
Comunidade

anti-ai-slop-writing

Produces human-sounding text that avoids detectable AI writing patterns. Activates on any writing task — tweets, emails, articles, bios, captions, reports, copy, messages, LinkedIn posts, cover letters, README files, or any content where the output must not read as AI-generated. Enforces banned vocabulary, structural variety, punctuation discipline, accuracy rules, and voice calibration. Use when the user says "write," "draft," "rewrite," "make this sound human," "anti-slop," "not AI," or any va

Instalações / 1h
2
GitHub Stars
5
Atualizado
8 de nov.