How do I install the Ccg Build skill?

Run npx skillmds@latest add tae2089/ccg-build 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 Ccg Build 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 Ccg Build?

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 Ccg Build free to use?

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

Who published Ccg Build?

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

Ccg Build by tae2089 — Agent Skill

Name: Ccg Build
Author: tae2089

Ccg Build

Explicit-only graph ingestion for building, updating, migrating, and postprocessing code-context-graph graphs from source visible to the CCG runtime. Use only when the user explicitly names the ccg-build skill in the current request. Do not invoke merely because a graph is missing or stale, annotations need reindexing, or another workflow would benefit from a refresh.

tae2089 Updated Sep 21, 2026

File contents

ccg-build — Graph Ingestion

Build or refresh graph state only from source paths the executing CCG runtime can read.

Invocation Gate

Proceed only when the user explicitly names ccg-build in the current request. A stale or missing graph, a requested scoped update, another skill's suggestion, or an applicable task description is not invocation. If the name was not explicitly provided, do not load the maintenance reference and do not perform or plan a graph write; report that the user may invoke ccg-build explicitly.

Mandatory Contract

Before any graph write, read references/graph-maintenance.md completely. Resolve the server-visible source path, namespace, update mode, scoped replacement behavior, and required postprocessing before invoking a write.

Ingestion Boundary

Local CLI and stdio MCP may build from a local source path.
A remote HTTP server ingests repositories through its configured Git webhook/sync path by default. Treat Git as the transport and source of truth.
Do not invent or attempt database upload, graph-bundle upload, streaming upload, or client-filesystem transfer. MCP graph-write tools operate on paths already visible to the server; they are not upload APIs.
If a remote server cannot access the source and no admitted Git sync path is available, report the limitation instead of trying a client-local path.

Command Selection

ccg update <dir>  # Ordinary source edits; incremental synchronization
ccg build <dir>   # First use, intentional full rebuild, or recovery
ccg migrate       # Existing database schema upgrade when required

Over MCP:

Use build_or_update_graph with full_rebuild=false for an incremental update.
Use build_or_update_graph with full_rebuild=true for a full rebuild.
parse_project writes parsed graph state without search postprocessing.
run_postprocess refreshes selected derived artifacts after graph changes.

Do not call a write tool merely because it is registered. Confirm that the user authorized graph mutation and that the target path and namespace are the intended ones.

Completion

Report the resolved source path, namespace, Git sync or local ingestion mode, full versus incremental choice, scoped replace behavior, and every failed or skipped postprocess step. State which verification was not run.

---name: ccg-builddescription: Explicit-only graph ingestion for building, updating, migrating, and postprocessing code-context-graph graphs from source visible to the CCG runtime. Use only when the user explicitly names the ccg-build skill in the current request. Do not invoke merely because a graph is missing or stale, annotations need reindexing, or another workflow would benefit from a refresh.---# ccg-build — Graph IngestionBuild or refresh graph state only from source paths the executing CCG runtimecan read.## Invocation GateProceed only when the user explicitly names `ccg-build` in the current request.A stale or missing graph, a requested scoped update, another skill's suggestion,or an applicable task description is not invocation. If the name was notexplicitly provided, do not load the maintenance reference and do not perform orplan a graph write; report that the user may invoke `ccg-build` explicitly.## Mandatory ContractBefore any graph write, read[`references/graph-maintenance.md`](references/graph-maintenance.md) completely.Resolve the server-visible source path, namespace, update mode, scopedreplacement behavior, and required postprocessing before invoking a write.## Ingestion Boundary- Local CLI and stdio MCP may build from a local source path.- A remote HTTP server ingests repositories through its configured Git webhook/sync path by default. Treat Git as the transport and source of truth.- Do not invent or attempt database upload, graph-bundle upload, streaming upload, or client-filesystem transfer. MCP graph-write tools operate on paths already visible to the server; they are not upload APIs.- If a remote server cannot access the source and no admitted Git sync path is available, report the limitation instead of trying a client-local path.## Command Selection```bashccg update <dir> # Ordinary source edits; incremental synchronizationccg build <dir> # First use, intentional full rebuild, or recoveryccg migrate # Existing database schema upgrade when required```Over MCP:- Use `build_or_update_graph` with `full_rebuild=false` for an incremental update.- Use `build_or_update_graph` with `full_rebuild=true` for a full rebuild.- `parse_project` writes parsed graph state without search postprocessing.- `run_postprocess` refreshes selected derived artifacts after graph changes.Do not call a write tool merely because it is registered. Confirm that theuser authorized graph mutation and that the target path and namespace are theintended ones.## CompletionReport the resolved source path, namespace, Git sync or local ingestion mode,full versus incremental choice, scoped `replace` behavior, and every failed orskipped postprocess step. State which verification was not run.

Frequently asked questions