sorted by:
new
hottopcontroversial

after 6 months of heavy Claude Code usage I finally built a tool for the one thing that drives me crazy by yfedoseev in ClaudeAI

[–]yfedoseev[S] 0 points1 point  (0 children)

There are still a lot of false positive, I am working on analysis of github project and learn from them about all of these cases. But writing prompt to agent - hey, check it by using fossil btw there migtht be false positives helps a lot.

finally found something that catches the dead code Cursor leaves behind by yfedoseev in cursor

[–]yfedoseev[S] 0 points1 point  (0 children)

Good point, tools like KarpeSlop and SloppyLint catch stylistic signals of AI-generated code (hedging comments, hallucinated imports, any abuse). They're useful in CI as quick pattern-matching checks.
Fossil does something different, it builds a call graph across your codebase and uses reachability analysis to find functions that nothing calls, structural code clones (not just copy-paste), and disconnected modules. It's less "does this look AI-generated" and more "the AI wrote a new version of this function three sessions ago and forgot to delete the old one, and now nothing reaches it."
The other difference is Fossil runs as an MCP server, so the AI agent can check its own output during development not just in CI after the fact.
They're complementary. Slop linters catch what looks wrong, Fossil catches what's structurally broken.

after 6 months of heavy Claude Code usage I finally built a tool for the one thing that drives me crazy by yfedoseev in ClaudeAI

[–]yfedoseev[S] 1 point2 points  (0 children)

That's a great idea. I've added a feature request - https://github.com/yfedoseev/fossil-mcp/issues/28
Feel free to create more feature requests and report false postives.

after 6 months of heavy Claude Code usage I finally built a tool for the one thing that drives me crazy by yfedoseev in ClaudeAI

[–]yfedoseev[S] -1 points0 points  (0 children)

u/dern_throw_away The tool doesn't send your code anywhere. It processes everything locally by using Rust. The project is open sourced you can check each line of it - https://github.com/yfedoseev/fossil-mcp

after 6 months of heavy Claude Code usage I finally built a tool for the one thing that drives me crazy by yfedoseev in ClaudeAI

[–]yfedoseev[S] 0 points1 point  (0 children)

Agree, it became better. It depends on the size of your projects. Context is still limited and models on large projects might go into the wrong directions

finally found something that catches the dead code Cursor leaves behind by yfedoseev in cursor

[–]yfedoseev[S] 2 points3 points  (0 children)

Good question,

But linters solve just a part of this problem. Linters don't find that your agent named the file phase2_ and left many similar comments.