本文へ移動
cccskills
無料GitHub で公開

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/code-context-graphスター 17(GitHub 17 + cccskills 0)

実行スコア 未検証

インストール方法を見る

含まれるファイル(2)

  • SKILL.md2.9 KB
  • references/graph-maintenance.md3.3 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

コメント

ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。

まだコメントはありません。最初のコメントを書いてみませんか。

送信するとすぐに公開されます。メールアドレスや電話番号などの個人情報は書かないでください。URL は 2 つまでです。

0 / 1000 文字

このフォームは reCAPTCHA で保護されており、Google のプライバシーポリシーと利用規約が適用されます。

同じリポジトリのスキル

ccg

無料

Fast read-only code discovery with a bounded code-context-graph search and targeted source verification. Use when an ordinary positive lookup or explanation needs an entry point, recorded intent, known-path inventory, or direct relationship evidence. Do not use for absence, completeness, exhaustive inventory, deep flow or impact analysis, or graph writes; use ccg-search-verify for defensible negative claims, and require explicit invocation for ccg-analyze or ccg-build.

日本語の概要は準備中です。原文の説明を表示しています。

tae2089/code-context-graph172026年8月22日 更新

Explicit-only deep analysis of algorithms, feature pipelines, and code relationships with CCG impact radius, bounded flow tracing, callers/callees, git-diff risk, affected stored flows, and cross-namespace references. Use only when the user explicitly names the ccg-analyze skill in the current request. Do not invoke merely because a task asks about a flow, pipeline, impact, caller, or relationship.

日本語の概要は準備中です。原文の説明を表示しています。

tae2089/code-context-graph172026年8月22日 更新

code-context-graph — annotation system. AI-driven annotation workflow, tag reference, and annotation search.

日本語の概要は準備中です。原文の説明を表示しています。

tae2089/code-context-graph172026年8月22日 更新

Author, refine, and verify CCG annotations such as @intent, @domainRule, @sideEffect, @mutates, @index, and @see. Use when adding business meaning to code, improving annotation-aware code or documentation retrieval, fixing annotation lint findings, checking supported tag syntax, or documenting operational contracts. Do not use for generated Markdown editing or annotations that merely restate symbol names.

日本語の概要は準備中です。原文の説明を表示しています。

tae2089/code-context-graph172026年8月22日 更新

ccg-docs

無料

code-context-graph — documentation generation, RAG indexing, and docs quality linting.

日本語の概要は準備中です。原文の説明を表示しています。

tae2089/code-context-graph172026年8月22日 更新

ccg-docs

無料

Generate, discover, read, and lint CCG documentation. Use when producing Markdown and Wiki snapshots, narrowing broad module questions with search, reading generated docs from configured content roots with get_doc_content, or diagnosing orphan, missing, stale, incomplete, contradiction, dead-ref, and drift findings. Do not use for direct source annotation authoring or exact call-graph analysis.

日本語の概要は準備中です。原文の説明を表示しています。

tae2089/code-context-graph172026年8月22日 更新

tae2089 のスキルをすべて見る

このスキルの問題を報告する