gsd-graphify

Featured

Build, query, and inspect the project knowledge graph in .planning/graphs/

AI & Automation 7,313 stars 501 forks Updated today MIT

Install

View on GitHub

Quality Score: 94/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

**STOP -- DO NOT READ THIS FILE. You are already reading it. This prompt was injected into your context by Claude Code's command system. Using the Read tool on this file wastes tokens. Begin executing Step 0 immediately.** **CJS-only (graphify):** `graphify` subcommands are not registered on `gsd-tools query`. Use the `gsd_run` launcher shim (defined in each bash block below) or invoke the binary directly: `node <runtime-home>/gsd-core/bin/gsd-tools.cjs graphify …` where `<runtime-home>` is your runtime's config directory (e.g. `~/.claude`, `~/.hermes`, `~/.cursor`). See `docs/CLI-TOOLS.md` for details. Other tooling may still use `gsd-tools query` where a handler exists. ## Step 0 -- Banner **Before ANY tool calls**, display this banner: ``` GSD > GRAPHIFY ``` Then proceed to Step 1. ## Step 1 -- Config Gate Check if graphify is enabled by reading `.planning/config.json` directly using the Read tool. **DO NOT use the gsd-tools config get-value command** -- it hard-exits on missing keys. 1. Read `.planning/config.json` using the Read tool 2. If the file does not exist: display the disabled message below and **STOP** 3. Parse the JSON content. Check if `config.graphify && config.graphify.enabled === true` 4. If `graphify.enabled` is NOT explicitly `true`: display the disabled message below and **STOP** 5. If `graphify.enabled` is `true`: proceed to Step 2 **Disabled message:** ``` GSD > GRAPHIFY Knowledge graph is disabled. To activate: node <runtime-home>/gsd-c...

Details

Author
open-gsd
Repository
open-gsd/gsd-core
Created
2 months ago
Last Updated
today
Language
JavaScript
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category