repo-graph-init

スター13

フォーク0

更新日2026年7月8日 13:41

Set up or rebuild the structural graph for a repo — on first use, after a big refactor, or to wire repo-graph into a project permanently.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

ソース

James-Chahwan

James-Chahwan/repo-graph

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

repo-graph init

Build the graph so the other skills have something to read.

When to use

First time using repo-graph in a repo (no graph yet).
After a large refactor or branch switch — the graph is stale.

Steps

First use: call refresh (optionally repo_path=<local path or git URL>). It scans with tree-sitter, runs the cross-stack resolvers, and caches the result. (The server also builds the graph automatically on first connect, so this is only needed to force it.)
After code changes: call refresh again — incremental, so only changed files re-parse. Add full=true to force a clean reparse. Routine edits are picked up automatically by the file watcher.

To add repo-graph to a project for good, drop an .mcp.json at the repo root:

{"mcpServers":{"repo-graph":{"command":"uvx","args":["mcp-repo-graph","--repo","."]}}}

Call orient to confirm it loaded.

このリポジトリの他の Skills

同じリポジトリ

repo-graph-debug

James-Chahwan/repo-graph

Start from a failure, not a filename — turn a stacktrace, failing test, or diff into the exact code that matters, then read it. Use when you have an error and need to know where to look.

2026-07-0813

repo-graph-find

James-Chahwan/repo-graph

Locate where a feature or symbol lives — match nodes by name, or pull the related cluster from a seed via spreading activation. Use to scope before reading.

2026-07-0813

repo-graph-impact

James-Chahwan/repo-graph

Blast radius before a change — everything a node affects (forward) or that depends on it (backward), ranked and located, with likely-dead code flagged. Also the one-hop view of direct connections.

2026-07-0813

repo-graph-orient

James-Chahwan/repo-graph

Get oriented in a codebase before reading files — repo shape, entry points, where the graph is blind, and the full structural map. Use at the start of any task in an unfamiliar or large repo.

2026-07-0813

repo-graph-trace

James-Chahwan/repo-graph

Follow the code across boundaries — a feature end-to-end, or the shortest path between two nodes (e.g. a frontend action to its backend handler). Links across the stack in one call instead of grepping both sides.

2026-07-0813

name	repo-graph-init
description	Set up or rebuild the structural graph for a repo — on first use, after a big refactor, or to wire repo-graph into a project permanently.

repo-graph init

Build the graph so the other skills have something to read.

When to use

First time using repo-graph in a repo (no graph yet).
After a large refactor or branch switch — the graph is stale.

Steps

First use: call refresh (optionally repo_path=<local path or git URL>). It scans with tree-sitter, runs the cross-stack resolvers, and caches the result. (The server also builds the graph automatically on first connect, so this is only needed to force it.)
After code changes: call refresh again — incremental, so only changed files re-parse. Add full=true to force a clean reparse. Routine edits are picked up automatically by the file watcher.

To add repo-graph to a project for good, drop an .mcp.json at the repo root:

{"mcpServers":{"repo-graph":{"command":"uvx","args":["mcp-repo-graph","--repo","."]}}}

Call orient to confirm it loaded.