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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Isolate read-only CCG search, documentation discovery, and analysis by namespace. Use when working across multiple repositories or services, preventing cross-project graph leakage, federating supported reads, or traversing materialized cross-namespace references. Do not use for graph writes or scoped updates; the user must explicitly invoke ccg-build for those operations.
日本語の概要は準備中です。原文の説明を表示しています。
Verify read-only code absence and completeness claims with bounded source and code-context-graph evidence. Use when the user asks whether code does not exist, requests exhaustive or complete inventory, or needs a defensible negative result. Do not use for ordinary positive lookup or explanation, deep flow or impact analysis, annotation authoring, documentation generation, or graph writes.
日本語の概要は準備中です。原文の説明を表示しています。
code-context-graph — documentation generation, RAG indexing, and docs quality linting.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
code-context-graph — annotation system. AI-driven annotation workflow, tag reference, and annotation search.
日本語の概要は準備中です。原文の説明を表示しています。