AI Agent Use Cases
Views —

AI Agent Use Cases

Added today

44All 189

Prompt to Prepare a Shopping Cart from a Recipe Photo

The author reports that Grok Bot receives a recipe photo, organizes the ingredients and quantities, and creates a shopping list by excluding ingredients already available at home.

Grok Bot
Life & Hobbies

1–20 of 189

Marketing & Design

Finding Code Errors in a Technical Blog Draft

They created a command to read a blog draft with the Gemini CLI and find code issues. The author applied the fixes themselves and reviewed the draft again.

Gemini

How it works

  1. They had Gemini CLI generate a custom command file, critique.toml, to review the blog draft. If a file path is given, it reads the file; if a plain string is given, it reviews that string itself.
  2. After refining how arguments are handled, they saved the file as .gemini/commands/critique.toml. The prompt uses {{args}} to receive input and is set up to point out code errors, technical accuracy, explanation flow, and title structure in Markdown.
  3. In the directory with the draft, they opened Gemini CLI and ran /critique @draft.md. The original also shows how to pipe file contents and specify the gemini-3-pro-preview model in the command.
  4. They selected actual items to fix from the review results. After addressing issues like blank screens from app initialization failure, Remote Config refresh intervals during development, and missing environment variable checks, they reviewed the draft again.
Command shared in the source
gemini -m gemini-3-pro-preview
/critique @draft.md

Results

They found and fixed issues with initialization failure handling, data request intervals during development, and environment variable checks.

Notes

The command uses the model name as in the original. You must save critique.toml first to use /critique. The full config file and code fix examples are in the original. The AI's suggestions were not automatically applied as-is.

Source

DEV Community Original post ↗

Example prompt · Gemini

Create a custom Gemini CLI command to check the code and explanations in a technical blog draft.

Input: draft [file], related project [path], used versions [list], review scope [criteria]. Prepare a command to save in .gemini/commands/critique.toml and handle file paths and direct string input according to the current CLI syntax.

Check for code execution errors, missing settings, mismatches between explanation and code, and dependencies needed for reproduction. If you can read files or run tests, record the evidence location and actual results; if not, mark code as reviewed by reading only.

For each issue, note the location, reproduction conditions, impact, and a fix suggestion. Do not change the author's writing style or add new features without reason. Leave fixes as suggestions until separately requested, and distinguish between publishable facts and claims needing verification.

Deliverables: command file, usage instructions, sample review report. Test with a valid draft, a draft with code errors, a nonexistent file, and plain string input, and verify you can recheck the same location.