I’ve been messing around with the new workflows in CC today (the ultracode/multi-agent orchestration thingy) and I ended up with something that is not a code review, but a full project health/maintainability review, graded separately for an LLM and human maintainers. First versions were useless. I pointed it at a work repo I know and it gave me vibe results that missed the problems I already knew were there. “There are tests, looks great!”. Yes, 5 tests. It wasn’t looking very deep. So I started iterating - I go back to Claude, tell him “you’re not looking at the data model. You can usually tell a lot from that”. His job is to turn this into a proper wall of text and make a new iteration of the workflow. After a few rounds it started catching useful things I didn’t already know. I’m a big fan of the critic near the end. He runs a pass to ask “what did we not check?” and then spawn investigators that actually go look. In a way he does what I was doing with the iterations, but dynamically. It is multi-repo aware (will consider your frontend and backend together, not separately), and writes a full report once done. You can also export the partial reports from all subagents. Runs in the background, ~20-30 min on my projects. Eats a lot of tokens, but you can confidently run this a few times on max 5x before you hit the session limit. Repo with setup scripts Example output , run against my own VS Code extension submitted by /u/FreHu_Dev
Originally posted by u/FreHu_Dev on r/ClaudeCode