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.
Labels
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.
reads a blog draft from disk and critiques it for technical errors
The fixes shown were written and applied by the author, so check each suggestion yourself.
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.
A developer built a custom Gemini CLI command
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.
The “Material” label failed its quality check and is not used for selection.
Details
- Agents
- Gemini
- Source
- blog
- Source date
- undated
- Accounts
- 1
- In registry since
- Oct 12, 2026