Content & CreativeDone with Gemini 2026-10-12
Critique blog post drafts for technical errors
A developer built a custom Gemini CLI command that reads a blog draft from disk and critiques it for technical errors, used in an iterative editing loop.
- What They Did
- Connie Leung had Gemini CLI generate a critique.toml custom command from a natural-language prompt, then refined it by hand and saved it in .gemini/commands. The prompt casts the model as a DevRel editor. She runs it on a draft by piping the file or referencing it with @draft.md, using Gemini 3 Pro Preview, then applies the fixes and reruns.
- How It Went
- The critique flagged three problems in her Angular/Firebase project: a white screen on initialization failure, a fetch interval that was too long in dev mode, and validation that stopped at the first missing environment variable. She fixed all three. No timing figures are given.
- Worth Knowing
- The command flags issues in the code inside the post. The fixes shown were written and applied by the author, so check each suggestion yourself.
Try it yourself with Gemini
Create a custom Gemini CLI command called /critique that reads the blog draft at [path to draft file] and reviews it for technical errors, such as wrong facts, incorrect code, outdated advice and unclear explanations. It should return a numbered list of issues, each with the quoted passage, why it is wrong and a suggested fix. Do not edit the draft file; just report findings so I can revise and run it again.