codegraph-bootstrap
Skill0 starsChanged 3 days agoMITView on GitHub
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.
- Pipes a download into a shell
In this repository108 other files it gives its agents.
- adaptive-estimationSkill
- adaptive-loop-budgetingSkill
- adopt-and-deleteSkill
- adversarial-reviewSkill
- agent-drives-uiSkill
- agentic-coding-loopSkill
- agent-otel-trajectorySkill
- agents-as-iac-modulesSkill
- ascii-ui-mockupsSkill
- authoring-html-emailSkill
- authoring-skills-vs-mcpSkill
- batched-ssh-enumerationSkill
- c4-architectureSkill
- challenge-the-premiseSkill
- codegraph-worktree-startupSkill
- colocated-pod-tolerationsSkill
- command-creatorSkill
- complexity-budgetsSkill
- connector-readinessSkill
- context-anchored-patchingSkill
- continuous-issue-resolutionSkill
- credential-proxySkill
- criticality-tiered-reportingSkill
- data-connector-buildingSkill
- declarative-firstSkill
- disk-pressure-forensicsSkill
- early-return-over-elseSkill
- email-triageSkill
- enums-codify-behaviorSkill
- ephemeral-workspace-lifecycleSkill
- event-sourcingSkill
- evidence-claim-boundariesSkill
- exhaustive-matchSkill
- feature-coverage-not-just-line-coverageSkill
- full-disk-forensicsSkill
- gate-before-pushSkill
- github-pr-shepherdingSkill
- graceful-shutdown-stateful-agentsSkill
- grounded-generationSkill
- iac-incident-responseSkill
- iac-not-ad-hocSkill
- instrumented-service-scaffoldSkill
- interface-over-conditionalsSkill
- knowledge-routingSkill
- lean-on-oss-standardsSkill
- live-money-disciplineSkill
- live-state-verificationSkill
- loop-governance-and-learningSkill
- low-level-executor-task-specSkill
- map-dispatch-over-conditionalsSkill
- merge-conflict-disciplineSkill
- mermaid-diagramsSkill
- oke-arc-runners-opentofuSkill
- orchestrate-agySkill
- orchestrate-claudeSkill
- orchestrate-codexSkill
- orchestrate-geminiSkill
- otel-emit-at-willSkill
- parameter-designSkill
- parse-dont-validateSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. About 0 are common, 8 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use CodeGraph as the first semantic code-navigation path when it is available.
- Distinctive: line 14
Check for an initialized project index:
- Very specific: line 20
If codegraph exists but the project is not initialized, run:
- Distinctive: line 26
Do this only inside the target repository.
- Very specific: line 30
If codegraph is missing, look for the environment's declared installer or package source before using an ad hoc install command.
- Distinctive: line 44
Not authorized: a production/shared host with no declared installer, a read-only review task, an environment where dependency installation …
- Distinctive: line 48
When authorized, prefer the environment's declared installer.
- Distinctive: line 56
After installation or initialization, prefer:
- Very specific: line 64
If the MCP tool is available, use codegraph_explore instead of the CLI for the same semantic lookup.
- Distinctive: line 69
Keep installation declarative where the environment has a dotfiles, Nix, package-manager, image-build, or IaC source of truth.
- Very specific: line 72
Do not run codegraph install --yes on a host whose agent config is source-controlled unless that mutation is also codified or the …
- Distinctive: line 75
Do not block the task if CodeGraph cannot be installed or initialized.
- Very specific: line 77
Treat .codegraph/ as local generated index state.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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
codegraphexists 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
codegraphis 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/nullInstall 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 | shAfter 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_exploreinstead 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 --yeson 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.
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
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.

