Skip to content

chore(graphify): set up graphify on Development-Everflow - #19

Draft
real-limitless wants to merge 2 commits into
Development-Everflowfrom
system/graphify-setup-ae42
Draft

real-limitless wants to merge 2 commits into
Development-Everflowfrom
system/graphify-setup-ae42

Conversation

@real-limitless

Copy link
Copy Markdown
Owner

Summary

Sets up graphify (the graphifyy knowledge-graph CLI + skill) on Development-Everflow (the runnable monorepo), matching the rollout across the flow repos.

What changed

  • graphify skill registered (project-scoped) for Agents, OpenCode, and Cursor: .agents/skills/graphify/, .opencode/ (plugin + skill + opencode.json), .cursor/rules/graphify.mdc, and a ## graphify section appended to AGENTS.md.
  • .graphifyignore + graphify-out/ in .gitignore.
  • .cursor/environment.json (install.cursor/install.sh provisions the graphify CLI; start.cursor/strip-cursor-attribution.sh runs per-boot attribution hygiene). Commands self-locate the script from the repo root, workspace parent, or the absolute /agent/repos/projecteverflow path.

Validation

  • graphify CLI installs and resolves.
  • Built the knowledge graph over the monorepo (platform-api, platform-ui, sandbox-agent, edge, mcp, toolkits): 10,383 nodes / 33,399 edges / 341 communities.
  • Graph output stays under the gitignored graphify-out/.
  • Commits carry zero Cursor attribution (authored by the repo owner).
Open in Web Open in Cursor 

…rsor

Adds the graphify knowledge-graph skill (project-scoped) plus .graphifyignore
and a graphify-out/ gitignore entry, and wires the graphify section into
AGENTS.md so agents use the graph for codebase questions.
…tall + attribution hygiene)

install: provisions the graphify CLI (graphifyy) on PATH.
start: per-boot hygiene that strips Cursor co-author git hooks, installs a
commit-msg strip hook, overrides a Cursor git identity, and runs a reaper.
Both commands self-locate the script from repo root, workspace parent, or the
absolute /agent/repos path.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant