Hey 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 will help (maybe not on a full Unity game) but if you'r building multiple Unity Packages or have existing Unity Packages. Appreciate you sharing this!
Interesting! Have you tried it on any large code bases? I have to wonder if json is going do become unwieldy at the scale of millions of LOC - a SQLite db might be a better choice.
Interesting, thanks.
Seeing agents querying compiled code using reflection to find references looks painful and inefficient. Made me want to help little buddy somehow, but had no idea how
(Microsoft) GitHub Copilot already builds a semantic index of your solution in a cloud cache, which is used to give higher code intelligence than what you can get from Claude Code alone or LLM interfaces which don't have native support for the Roslyn API like GitHub Copilot does.
GitHub Copilot's semantic index can work for any SaaS repo provider (GitLab, Bitbucket, etc.) or any local repos but this requires you to opt into the feature. Repos hosted in GitHub and Azure DevOps do NOT require opting into it since Microsoft already has your code.
Exactly! I'd be more than happy to hand it over to Microsoft to continue maintaining it just to be clear. But MIT licensing it, hopefully the community will help keep it up to date with future C# versions too.
I'm hoping Rider get some support for switching between worktrees efficiently - until then, it becomes a tool only the primary / interactive agent sessions can access.
lol I actually didn't know that. This is MIT licensed though.
EDIT: I think the differentiation is that this isn't MCP based. Dumping a portable json file allows much more flexibility than just having to run Rider IDE in the background with the solution loaded and indexed. e.g. the graph works with jq, CI (gates), arbitrary agents without MCP support, non MCP tools, bulk questions etc.
Love to see C# love. It's a great language. Super underrated in my opinion.
Unions coming in .NET 11 / C# 15 are going to be great.
Very excited to see union types and to see C# on here. C# can feel like a bit of a scarlet letter in the bay.
Hey 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 will help (maybe not on a full Unity game) but if you'r building multiple Unity Packages or have existing Unity Packages. Appreciate you sharing this!
Is this compatible with Graphify-Labs/graphify, w/r/t existing output formats?
Interesting! Have you tried it on any large code bases? I have to wonder if json is going do become unwieldy at the scale of millions of LOC - a SQLite db might be a better choice.
Interesting, thanks. Seeing agents querying compiled code using reflection to find references looks painful and inefficient. Made me want to help little buddy somehow, but had no idea how
I don't understand why Microsoft and JetBrains aren't shipping versions of this. It seems like exactly what Roslyn was designed for
(Microsoft) GitHub Copilot already builds a semantic index of your solution in a cloud cache, which is used to give higher code intelligence than what you can get from Claude Code alone or LLM interfaces which don't have native support for the Roslyn API like GitHub Copilot does.
GitHub Copilot's semantic index can work for any SaaS repo provider (GitLab, Bitbucket, etc.) or any local repos but this requires you to opt into the feature. Repos hosted in GitHub and Azure DevOps do NOT require opting into it since Microsoft already has your code.
Exactly! I'd be more than happy to hand it over to Microsoft to continue maintaining it just to be clear. But MIT licensing it, hopefully the community will help keep it up to date with future C# versions too.
JetBrains provides an MCP server such that agents can query the project index for things like find usages. What's different about this?
I'm hoping Rider get some support for switching between worktrees efficiently - until then, it becomes a tool only the primary / interactive agent sessions can access.
lol I actually didn't know that. This is MIT licensed though.
EDIT: I think the differentiation is that this isn't MCP based. Dumping a portable json file allows much more flexibility than just having to run Rider IDE in the background with the solution loaded and indexed. e.g. the graph works with jq, CI (gates), arbitrary agents without MCP support, non MCP tools, bulk questions etc.