Soham Patankar
fbe1e9977f
All-platform progressive-disclosure skill split + generator (addresses #1106). Splits each platform's skill into a lean core (~615 lines, full default pipeline inline) + on-demand references/, generated from a single source via tools/skillgen with a CI/pre-commit drift gate. 13 hosts split, aider/devin stay monoliths. Also fixes the stale bare-path bugs across the previously hand-maintained variants and moves the always-on blocks into packaged markdown. Verified: all 5 generator guards pass, byte-verbatim load-bearing slices, lean cores self-sufficient on the default path across all 13 split hosts, references gated to non-default branches, description preserves the graphify-out-query-first clause. Supersedes #1119 (Claude-first subset). Known follow-up applied on top: harden _always_on() against a missing packaged file so a partial install can't brick the CLI.
18 lines
1014 B
Markdown
18 lines
1014 B
Markdown
## graphify
|
|
|
|
For any question about this repo's architecture, structure, components, or how to add/modify/find
|
|
code, your first action should be `graphify query "<question>"` when `graphify-out/graph.json`
|
|
exists. Use `graphify path "<A>" "<B>"` for relationship questions and `graphify explain "<concept>"`
|
|
for focused-concept questions. These return a scoped subgraph, usually much smaller than the full
|
|
report or raw grep output.
|
|
|
|
Triggers: "how do I…", "where is…", "what does … do", "add/modify a <component>",
|
|
"explain the architecture", or anything that depends on how files or classes relate.
|
|
|
|
If `graphify-out/wiki/index.md` exists, use it for broad navigation. Read `graphify-out/GRAPH_REPORT.md`
|
|
only for broad architecture review or when query/path/explain do not surface enough context. Only read
|
|
source files when (a) modifying/debugging specific code, (b) the graph lacks the needed detail, or
|
|
(c) the graph is missing or stale.
|
|
|
|
Type `/graphify` in Copilot Chat to build or update the graph.
|