القائمة
code-context-graph — impact analysis, flow tracing, dead code, architecture. Use when answering "what's affected", "how does X flow", "what's unused", "module structure".
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Analyze code relationships with CCG impact radius, flow tracing, callers/callees, git-diff risk, and affected stored flows. Use when a task asks what a change affects, how a call path flows, who calls a symbol, or which flows recent changes touch. Do not use for simple text lookup, documentation generation, or annotation authoring.
Isolate CCG graph build, search, documentation discovery, and analysis by namespace. Use when working across multiple repositories or services, preventing cross-project graph leakage, listing populated namespaces, or applying one namespace consistently across MCP and CLI operations. Do not use for ordinary single-repository work that fits the default namespace.
Author and refine 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, or documenting operational contracts. Do not use for generated Markdown editing or annotations that merely restate symbol names.
Build, update, inspect, and search code-context-graph graphs and route to specialized CCG workflows. Use when a task needs CCG setup, graph freshness, exact symbol or relationship lookup, annotation-aware full-text search, MCP graph queries, or selection among CCG analysis, docs, annotation, and namespace skills. Do not use for a simple file or string lookup when grep/read is sufficient.
Generate, discover, read, and lint CCG documentation. Use when producing Markdown and Wiki snapshots, narrowing broad module questions with search_docs, reading generated docs 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.
code-context-graph — documentation generation, RAG indexing, and docs quality linting.
استنادا إلى تصنيف SOC المهني
| name | ccg-analyze |
| description | code-context-graph — impact analysis, flow tracing, dead code, architecture. Use when answering "what's affected", "how does X flow", "what's unused", "module structure". |
Graph-based analysis for change impact, call flow, dead code, module structure — anything about "relationships."
| User intent | Tool | Notes |
|---|---|---|
| "Impact of changing this function?" | get_impact_radius (start with depth 3) | Widen to depth 5 if too narrow |
| "Trace call flow from this function" | trace_flow | If broken at interfaces, see workaround below |
| "Who calls this function?" | query_graph (callers_of) | |
| "What does this function call?" | query_graph (callees_of) | |
| "Risk of this change" | detect_changes + get_affected_flows | git diff-based |
If trace_flow returns only 1–2 starting nodes, it broke at an interface dispatch boundary (Go's h.deps.X.Method(), Python duck typing, etc.).
Workaround:
1. Confirm starting point via trace_flow
2. Manually expand graph with callers_of / callees_of
3. When you hit interface methods:
- Find the interface via search
- Reverse-trace implementations with callers_of
Latest ccg added an interface dispatch resolver, but it doesn't cover every pattern. If results look thin, fall back to this manual pattern.
If results are huge, the change scope is likely too wide. Reconsider the change unit based on node count.
fallback_calls are treated as best-effort when present in graph data; strict workflows should treat them as noisy signals.fallback_calls can hide unresolved edges when strict call resolution is too strict, but they increase false-positive risk.
ccg build/ccg update was run without --fallback-calls, treat missing flow paths as strict failures first.--fallback-calls, validate critical paths by filtering for kind=calls edges only (if tooling allows), or re-run with strict mode for confirmation.fallback_calls only for recovery hypotheses.| Tool | One-liner |
|---|---|
get_impact_radius | BFS blast radius |
trace_flow | Call chain trace |
detect_changes | Git diff risk score |
get_affected_flows | Flows affected by change |
list_flows | Stored flow list |
For detailed parameters, see MCP schema.
Requires ccg build . first. Schema error → ccg migrate, retry. (See /ccg skill.)