graphify-helperslisted

Use whenever a developer skill needs to search the codebase for symbols, callers, dependents, or paths between symbols. This is the canonical implementation of the Graphify-first protocol — Graphify queries first, grep fallback when any of four trigger conditions hits (empty result, error, not setup, under min_results_threshold). All other dev skills (codebase-scan, code-review-guide, lesson-extraction, tdd-patterns, verification-patterns, complexity-assessment, strategic-analysis, architecture-health-scanner, council, autoskill) consume this skill rather than calling Graphify directly. Skill auto-degrades to grep-only mode when graphify.enabled=false in .devt/config.json — system stays fully functional without Graphify, just less token-efficient.
emrecdr/devt · ★ 0 · AI & Automation · score 75

Install: claude install-skill emrecdr/devt

# Graphify Helpers — Graphify-First Protocol ## Overview devt is Node-stdlib-only. Graphify (`uv tool install graphifyy[mcp]` or equivalent) is an OPTIONAL project-level dependency that supercharges code search by replacing grep's text-match results with AST-anchored symbol nodes from `graphify-out/graph.json`. When enabled, Graphify reduces token cost on typical code-search operations by ~10×; when disabled, devt falls back to grep with identical output shape. **Architecture note**: devt's CLI wrappers read `graphify-out/graph.json` in-process — the `graphify` binary is needed only to regenerate the graph. Detail: `references/graphify-helpers-details.md`. This skill is the canonical wrapper. Other developer skills (codebase-scan, code-review-guide, etc.) MUST route through this skill rather than calling Graphify or grep directly. The skill auto-handles the four fallback triggers and tags every result with its provenance. ## When To Use Trigger on: - Any skill needing to find symbol definitions, callers, dependents, or paths - Code-review tasks that need to enumerate affected callers - Refactor scoping ("how big is the blast radius if I change AuthService?") - TDD pattern lookup ("show me existing tests near this subject") - Architecture health checks needing symbol-anchored boundary verification Skip for: - Pure prose search (config keys in YAML, log message strings, doc text) — use grep directly with `--text-mode`. Graphify-first does not help. - Single-file exac