build-program-graph
SolidUse when a multi-language program graph is needed for call paths, entrypoints, blast radius, coarse taint reachability, privilege boundaries, or declared cross-system links. Builds the full graph, runs preanalysis, and gates every version-specific query behind a capability probe with bounded security claims. Not for a quick overview; use trailmark-summary. Not for a fixed snapshot payload; use trailmark-structural.
Install
Quality Score: 83/100
Skill Content
Details
- Author
- OutlineDriven
- Repository
- OutlineDriven/outline-driven-development
- Created
- 9 months ago
- Last Updated
- 5 days ago
- Language
- Python
- License
- Apache-2.0
Similar Skills
Semantically similar based on skill content — not just same category
engineer-graph
Plan, validate, and run bounded autonomous engineering graphs. Use for broad work that benefits from decomposition, parallel investigation, independent verification, synthesis, implementation, or a human gate before external or destructive actions.
graphify
Use for tracing how code connects across files - "how does A reach B", "is there a route from X to Y", "what sits between these two modules", "what breaks if I change X" - and for orienting in an unfamiliar or large repo. Builds a queryable call/import graph once (graphify update), then answers with graphify path, affected, explain and query against that graph. Do NOT use when one bounded grep or one Read already answers the question, or on a repo small enough to read into context. Maps CODE structure, not agent workflows.
graphtrail
Use when answering structural code questions in an indexed repo - who calls this, what does this call, what breaks if I change it, what changed between two versions. Reach for it BEFORE grep whenever the question is about relationships between symbols rather than text. Triggers include "who calls", "what uses", "blast radius", "impact of changing", "callers of", "what depends on", and reviewing a diff's structural effect.