graphify-setup
Installation
SKILL.md
Graphify Setup
Do the requested Graphify work end to end; do not stop after describing commands or installing the CLI. Use the installed CLI's --help and the current official Graphify instructions; never invent commands or flags. Preserve existing configuration, hooks, instructions, and unrelated changes.
Gates for every mode
- Never commit or push without explicit authorization.
- Within
graphify-out/, commit onlygraph.json,GRAPH_REPORT.md, andgraph.html(optional: only when the file exists), by exact path. Never stagemanifest.json, caches, cost records,.graphify_*sidecars, or datedYYYY-MM-DD/backup folders. Commit other setup files (.gitignore,.gitattributes,AGENTS.md,CLAUDE.md, installed skill and config directories) only when the authorization names them. Ignore the installer's broadgit addhint. - Graphify's auto-rebuild git hooks (
post-commit,post-checkout) are not kept. Only thegraph.jsonmerge driver stays; the graph is refreshed before each commit instead (refresh). - Before any
graphify updateorgraphify cluster-only, pass the community-name guard: without Graphify's machine-local label files these commands silently replace curated community names. Stop and ask when the guard says so. - Do not run
graphify hook uninstall(it also removes the merge driver) or a baregraphify install. Never add--forceon your own: when a Graphify command refuses, report its message and ask. - Semantic extraction runs once, through the active host agent. Never use a headless, API-key, or provider-key substitute.
- Routine integration (merges, updates) is one bounded deterministic refresh that reuses valid semantic data and caches. Missing or checkout-specific state, or an installed skill that suggests broader extraction, does not authorize a semantic rebuild; the merge workflow scope and stop conditions govern.
Choose the mode
- Migration: the repository already uses Graphify (
graphify-out/graph.jsonexists) and the user asks to set it up again, update it, or apply the new workflow. Do not reinstall skills, ask for harness selection, or run a full build. Run only the migration steps, then verify and report. For an additional harness, run only section 2 of the setup instructions for that target. - Merge: persistent merge rules, or merging branches in a repository that already uses Graphify. Follow the merge workflow and only its mechanical completion checks. Keep the merge paused until it says recovery is complete. Broader semantic investigation, rebuilding, or enrichment needs separate explicit authorization.
- Initial setup: an explicit request to set up Graphify and build the graph. Follow the steps below.