The tool recommends you to use this skill https://github.com/zachsaw/graphify-csharp/blob/main/.agents... >, but I wonder if this is the right approach if one just want to use this as a consumer in a .net project. It seems very wordy, but wording like these "Read the relevant design documents under docs/ before changing architecture." makes me think that developing 'graphify the tool' and using 'graphify as a tool' a…
Show HN: Graphify C# – Compiler-accurate Find Usages for coding agents
21–25 of 25 posts
Re: Show HN: Graphify C# – Compiler-accurate Find Usages for coding agents
#22Hey man, just wanted to say thanks! I pulled this down and adapted the skill for Unity development, keeping Graphify C# as an external analysis tool. My adapted skill isn’t publicly available yet, and I'm going to add it into my standard Unity Package development workflow to see if I can find some additional value in how the CLI and structured JSON make semantic information accessible to coding agents. I think this w…
Re: Show HN: Graphify C# – Compiler-accurate Find Usages for coding agents
#23The tool recommends you to use this skill https://github.com/zachsaw/graphify-csharp/blob/main/.agents... >, but I wonder if this is the right approach if one just want to use this as a consumer in a .net project. It seems very wordy, but wording like these "Read the relevant design documents under docs/ before changing architecture." makes me think that developing 'graphify the tool' and using 'graphify as a tool' a…
Very good point! the graphify the tool and using graphify AS A tool have definitely beed mixed up! I'll fix this up. Thanks again and appreciate you looking into it!
Re: Show HN: Graphify C# – Compiler-accurate Find Usages for coding agents
#24The tool recommends you to use this skill https://github.com/zachsaw/graphify-csharp/blob/main/.agents... >, but I wonder if this is the right approach if one just want to use this as a consumer in a .net project. It seems very wordy, but wording like these "Read the relevant design documents under docs/ before changing architecture." makes me think that developing 'graphify the tool' and using 'graphify as a tool' a…