agentleFS
Sign inStart free
ThakurvaibhavThakurvaibhav/platform-agent-harness/skills/graphify/SKILL.md

graphify

Skill2 starsChanged 6 days agoApache-2.0View on GitHub

Build and query a repository knowledge graph for architecture and dependency questions. Use when the user asks how something connects, where something is implemented, or any question that would otherwise require reading many files.

115 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use remotion-maps, remotion-saas and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • OpenAISkill

    remotion-maps

    Remotion Map animation knowledge

    Also in 4 projects that use this

  • OpenAISkill

    remotion-saas

    Build an app with Remotion

    Also in 4 projects that use this

  • royaluniondesign-sysSkill

    deployment-patterns

    Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications.

    Also in 4 projects that use this

  • mstuder-slalomSkill

    django-verification

    Verification loop for Django projects: migrations, linting, tests with coverage, security scans, and deployment readiness checks before release or PR.

    Also in 3 projects that use this

  • ttmouseSkill

    prompt-master

    提示词主控 - 智能选择合适的领域skill并生成提示词，支持自动领域分类和调度

    Also in 4 projects that use this

  • seikaikyoSkill

    doubt-driven-development

    對非平凡決策啟動新鮮 context 對抗審查（找碴不背書），在修正還便宜的時候抓出錯誤方向。適用：高風險改動（production、資安敏感邏輯、不可逆操作）、不熟的程式碼、要宣稱「這樣是安全的 / 可行的」之前。機械性操作與一行修改不適用。

    Also in 6 projects that use this

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 113 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use results to select the smallest set of files to actually read.

    line 45
  2. Distinctive:

    Read the user's question.

    line 49
  3. Very specific:

    If graphify-out/graph.json exists, query it.

    line 50
  4. Distinctive:

    Read those files (not the entire directory).

    line 52
  5. Very specific:

    Never publish a real private-repo graph or GRAPH_REPORT.md.

    line 65

“Common” is measured: kept by at least 6 in 10 of the 113 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Graphify

Turn any folder of code, docs, papers, or images into a queryable knowledge graph. Querying a graph typically costs ~70x fewer tokens than file-by-file reading.

Upstream: https://github.com/safishamsi/graphify

When to use

  • Architecture questions: "How does X connect to Y?"
  • Dependency tracing: "Which charts reference this Service?"
  • God-node detection: "Which file has the most incoming edges?"
  • Migration planning: "What breaks if I rename this CRD?"

Build a graph

cd <repo>
graphify . --no-viz

Output lands in graphify-out/. The harness .gitignore excludes this directory — never commit a real private-repo graph.

Inspect the build report for god nodes and surprising connections:

cat graphify-out/GRAPH_REPORT.md

Query

graphify query "How does deployment config flow to workloads?"
graphify path "HelmChart" "ArgoCDApplication"
graphify explain "ServiceAccount"

Use results to select the smallest set of files to actually read. The graph guides exploration; source files remain the final authority.

Pattern: graphify-first, source-of-truth-second

  1. Read the user's question.
  2. If graphify-out/graph.json exists, query it.
  3. From the result set, pick the 3–10 most relevant files.
  4. Read those files (not the entire directory).
  5. Answer with citations to the actual files — not to graph nodes.

When to rebuild

  • Significant repo restructuring.
  • New chart / module added.
  • Renames of frequently referenced symbols.

Otherwise, the existing graph is usually good enough for weeks.

Safety

  • Never publish a real private-repo graph or GRAPH_REPORT.md.
  • For public examples, use a sanitized sample graph or commit only graphify-out/.gitkeep.

Memory

bd remember "graphify build for <repo>: <god nodes / community summary>" --key <repo>/tool/graphify

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free