Tag: Claude Code
-
Hand Claude a fuzzy issue and it will start editing files in the first thirty seconds and often that’s fine. On anything non-trivial it means the plan gets invented on the fly, half-written into the diff, and you find out what Claude thought the task was only when you read the PR. MoFlo’s new –sdd flag puts a spec…
-
MoFlo gives Claude Code a memory, learned model routing, and repeatable workflows — local-first, no API keys, one npm install.
-
Two new MoFlo skills you cast like spells — one to quicken what drags, one to ward what isn’t tested — and both answer right in your Claude Code session. Good review shouldn’t make you go looking for it. MoFlo 4.11.2 adds two on-demand audits that read exactly what you’re working on and report back in the same conversation — with…
-
MoFlo learns about your project and remembers it across sessions — but the hard-won part of that memory used to be trapped in whatever checkout first learned it. A new git worktree, a fresh machine, a teammate’s clone would reindex your code and guidance on its own, yet start blank on everything you’d actually taught…
-
How MoFlo‘s /distill compares to Claude Code’s built-in /simplify skill. Both can clean up code before a PR; the difference is that /simplify runs the same fixed multi-agent pipeline on every diff, while distill measures the diff first and runs only as much review as the change warrants. Distill: a /simplify for every sized change Claude Code ships a built-in /simplify skill. It’s good. Point it…