Graphify Impact Context

Graphify gives VibePro code-graph context for impact-scope discovery. It is optional, but it is useful when a change may affect shared functions, cross-file behavior, or hidden dependencies.

Run or import Graphify output

Run Graphify through VibePro:

PATH="$HOME/.local/bin:$PATH" vibepro graph . --run-graphify

Import an existing Graphify output directory:

vibepro graph . --from .vibepro/graphify

If graphify is installed outside your shell PATH, expose it before running VibePro. A common local install path is $HOME/.local/bin/graphify.

What VibePro stores

The imported files live under:

.vibepro/graphify/
  graph.json
  graph.html
  GRAPH_REPORT.md

Use GRAPH_REPORT.md to find major hubs, communities, and surprising connections. Use graph.html when you need a visual graph.

How to read the result

Graphify output is context, not final truth. Treat it as a map that helps decide where to inspect next.

Good uses:

• identify shared functions or modules touched by a small-looking change
• find test and implementation links that should be included in a review
• inform story derive, story diagnose, and PR scope review
• support architecture and regression-risk checks

Bad uses:

• accepting inferred edges as proof without source inspection
• replacing Story or Spec with generic graph findings
• assuming every connected node must be changed

Story and Spec context matter. If the repository has no clear Story or Spec, Graphify may only produce generic task discovery. In that case, create or select a Story first, then rerun:

vibepro story diagnose . --id <story-id> --run-graphify