Skip to content

graphify indexes its own installed skill files as project content #4057

Description

@Mpasha17

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

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions