Agent Skills
› mtarcure/claude-vibe-squad
› cross-file-relationship-synthesis
cross-file-relationship-synthesis
GitHub将独立读取的文件转化为带类型、方向和行锚点的关系映射图，识别调用、导入等边，定位关键切割点、影响范围及孤立节点，确保结论基于可追溯的边而非印象。
Trigger Scenarios
需要分析跨文件依赖关系
评估代码变更的影响范围
梳理复杂系统的控制或数据流
Install
npx skills add mtarcure/claude-vibe-squad --skill cross-file-relationship-synthesis -g -y
SKILL.md
Frontmatter
{
"name": "cross-file-relationship-synthesis",
"audience": "specialist",
"description": "Use when several files have been read independently but a conclusion depends on how control or data crosses them: build a typed, directed, line-anchored map of calls, imports, producer-consumer and config edges; identify cut points, blast radius, orphans, and traversal-backed conclusions. It maps arbitrary repository relationships; it does not settle privacy compliance or prescribe graph surgery."
}
Cross-File Relationship Synthesis
Turn a set of independently-read files into an explicit relationship map, so conclusions rest on traced edges rather than on the impression that the files are related.
Steps
- List the files in scope and give each a one-line role. A file whose role you cannot state in one line has not been understood well enough to relate to others.
- Name the edge kinds you will trace before tracing them — calls, imports, writes-then-reads, schema producer/consumer, config-to-consumer, generator-to-generated. Untyped "related to" edges hide the actual dependency.
- Trace each edge in the direction data or control actually flows, and record the file and line at both ends. An edge without two anchors is a hypothesis.
- Distinguish edges you observed from edges you inferred from naming. Matching names are a lead to verify, never an edge.
- Look specifically for the edges that contradict the obvious structure: the secondary writer, the path that bypasses the abstraction, the consumer nobody registered. These decide correctness more often than the primary path does.
- Identify the cut points — files whose change propagates furthest — and state the blast radius of each as a concrete list of affected files.
- Check the map for orphans and dead ends, and resolve each: either an edge is missing from the map, or the file genuinely is unreachable. Never leave the ambiguity unexplained.
- State the conclusion as a traversal over the map, so a reader can follow the same path and reach the same result.
Acceptance
- Every file in scope has a stated one-line role.
- Every edge is typed, directed, and anchored at both ends with file and line.
- Observed edges and name-inferred edges are visibly separated.
- Cut points are named with an explicit blast-radius file list.
- Orphans and dead ends are each resolved as missing-edge or genuinely-unreachable.
- The final claim is expressed as a walk over recorded edges, not as a summary impression.
Version History
- d5262e2 Current 2026-09-11 11:15
