How do I install the Codegraph Bootstrap skill?

Run npx skillmds@latest add selamy-labs/codegraph-bootstrap in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Codegraph Bootstrap safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Codegraph Bootstrap?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Codegraph Bootstrap free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Codegraph Bootstrap?

selamy-labs (@selamy-labs) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Codegraph Bootstrap by selamy-labs — Agent Skill

Name: Codegraph Bootstrap
Author: selamy-labs

Codegraph Bootstrap

Use when starting code exploration or implementation in a repository where CodeGraph may be available. Ensure CodeGraph is installed/initialized when authorized, then prefer CodeGraph queries for semantic code context.

selamy-labs fbe430a 2.9 KB Updated Sep 17, 2026

File contents

CodeGraph Bootstrap

Use CodeGraph as the first semantic code-navigation path when it is available. The goal is to give the agent indexed symbol, call-path, and impact context before falling back to file-by-file grep/read exploration.

Workflow

Check for an initialized project index:
```
codegraph status .
```
If codegraph exists but the project is not initialized, run:
```
codegraph init .
```
Do this only inside the target repository. Do not initialize a home directory, filesystem root, vendored dependency cache, or generated build directory unless the user explicitly asks.
If codegraph is missing, look for the environment's declared installer or package source before using an ad hoc install command. Check repo docs, bootstrap scripts, dotfiles, Nix flakes, package manifests, container images, or other source-owned provisioning files that already mention CodeGraph.
```
rg -n "codegraph|CODEGRAPH_" . "$HOME/.config" 2>/dev/null
```
Install CodeGraph only when authorized:
- Authorized: the user asked for installation, the task is explicitly a bootstrap/provisioning task, or a source-owned installer exists for the environment.
- Not authorized: a production/shared host with no declared installer, a read-only review task, an environment where dependency installation is disallowed, or any case where the user asked not to change the host.
When authorized, prefer the environment's declared installer. If no declared installer exists but the user explicitly authorizes a direct user-local install, use the upstream installer:
```
curl -fsSL https://raw.githubusercontent.com/colbymchenry/codegraph/main/install.sh | sh
```
After installation or initialization, prefer:
```
codegraph explore "question or symbol area" --path .
codegraph node SymbolName --path .
codegraph impact SymbolName --path .
```
If the MCP tool is available, use codegraph_explore instead of the CLI for the same semantic lookup.

Guardrails

Keep installation declarative where the environment has a dotfiles, Nix, package-manager, image-build, or IaC source of truth. Add or update that source instead of leaving a live-only mutation.
Do not run codegraph install --yes on a host whose agent config is source-controlled unless that mutation is also codified or the host-local file is intentionally outside shared config.
Do not block the task if CodeGraph cannot be installed or initialized. State the reason, then continue with normal repository tools.
Treat .codegraph/ as local generated index state. Do not commit it unless the repository explicitly tracks it.

---name: codegraph-bootstrapdescription: Use when starting code exploration or implementation in a repository where CodeGraph may be available. Ensure CodeGraph is installed/initialized when authorized, then prefer CodeGraph queries for semantic code context.---# CodeGraph BootstrapUse CodeGraph as the first semantic code-navigation path when it is available.The goal is to give the agent indexed symbol, call-path, and impact contextbefore falling back to file-by-file grep/read exploration.## Workflow1. Check for an initialized project index: ```sh codegraph status . ```2. If `codegraph` exists but the project is not initialized, run: ```sh codegraph init . ``` Do this only inside the target repository. Do not initialize a home directory, filesystem root, vendored dependency cache, or generated build directory unless the user explicitly asks.3. If `codegraph` is missing, look for the environment's declared installer or package source before using an ad hoc install command. Check repo docs, bootstrap scripts, dotfiles, Nix flakes, package manifests, container images, or other source-owned provisioning files that already mention CodeGraph. ```sh rg -n "codegraph|CODEGRAPH_" . "$HOME/.config" 2>/dev/null ```4. Install CodeGraph only when authorized: - Authorized: the user asked for installation, the task is explicitly a bootstrap/provisioning task, or a source-owned installer exists for the environment. - Not authorized: a production/shared host with no declared installer, a read-only review task, an environment where dependency installation is disallowed, or any case where the user asked not to change the host.5. When authorized, prefer the environment's declared installer. If no declared installer exists but the user explicitly authorizes a direct user-local install, use the upstream installer: ```sh curl -fsSL https://raw.githubusercontent.com/colbymchenry/codegraph/main/install.sh | sh ```6. After installation or initialization, prefer: ```sh codegraph explore "question or symbol area" --path . codegraph node SymbolName --path . codegraph impact SymbolName --path . ``` If the MCP tool is available, use `codegraph_explore` instead of the CLI for the same semantic lookup.## Guardrails- Keep installation declarative where the environment has a dotfiles, Nix, package-manager, image-build, or IaC source of truth. Add or update that source instead of leaving a live-only mutation.- Do not run `codegraph install --yes` on a host whose agent config is source-controlled unless that mutation is also codified or the host-local file is intentionally outside shared config.- Do not block the task if CodeGraph cannot be installed or initialized. State the reason, then continue with normal repository tools.- Treat `.codegraph/` as local generated index state. Do not commit it unless the repository explicitly tracks it.

Frequently asked questions