Hey! I noticed this while adding Grok Build support (#4047), but it's not Grok-specific; it happens on plain v8 too.
After graphify claude install and graphify install --project --platform claude, running graphify update . picks up graphify's own files as if they were part of the project: .claude/skills/graphify/SKILL.md, everything under references/, .claude/CLAUDE.md, CLAUDE.md and AGENTS.md.
To reproduce on 0.9.75, take a fresh repo with one small auth.py (two functions), run the installs above, then run graphify update .. I got 69 nodes, and only 3 of them came from auth.py. The rest were graphify's own skill docs. In a small repo that drowns out the real code in queries and the report.
I'm happy to send a PR. The skill folders and hook files seem easy to skip in detect.py, but AGENTS.md and CLAUDE.md are trickier since they're the user's files and graphify only adds a section. Would you rather skip just the ## graphify section, or leave those files as they are? @safishamsi
Hey! I noticed this while adding Grok Build support (#4047), but it's not Grok-specific; it happens on plain v8 too.
After
graphify claude installandgraphify install --project --platform claude, runninggraphify update .picks up graphify's own files as if they were part of the project:.claude/skills/graphify/SKILL.md, everything underreferences/,.claude/CLAUDE.md,CLAUDE.mdandAGENTS.md.To reproduce on 0.9.75, take a fresh repo with one small
auth.py(two functions), run the installs above, then rungraphify update .. I got 69 nodes, and only 3 of them came fromauth.py. The rest were graphify's own skill docs. In a small repo that drowns out the real code in queries and the report.I'm happy to send a PR. The skill folders and hook files seem easy to skip in
detect.py, butAGENTS.mdandCLAUDE.mdare trickier since they're the user's files and graphify only adds a section. Would you rather skip just the## graphifysection, or leave those files as they are? @safishamsi