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

DevShared prompt

Prompt for Organizing Error Descriptions into Issues with Reproduction Conditions

The author reports that Grok Bot asks questions about missing information in error descriptions and is requested to review related code to draft a GitHub issue.

Grok Bot

How it works

  1. The author instructs Grok Bot to ask about what happened, the expected behavior, and the starting point, one at a time.
  2. If repository access is available, the author reports that Grok Bot reads related code and existing issues and attempts to reproduce the problem. The author requests a draft that marks any unchecked parts and asks for approval before posting.

Results

The author aims to produce an issue draft that includes a summary, current and expected behavior, reproduction steps, and completion criteria. This is the goal of the public request, and it is not a report of execution results.

Notes

This is a shared prompt introduced in awesome-grok-bot as an idea by @nate-stellar. The actual availability and execution results of the connected service must be checked separately.

Source

GitHub Original post ↗

Example prompt · Grok Bot

Goal: Organize a brief error description into an issue with reproduction conditions.

Input/Environment: [Error description], [Permitted GitHub repository], [Execution environment], [Reproduction materials], [Issue writing rules].

Reference original: https://github.com/Anil-matcha/awesome-grok-bot#github-issue-drafter

Please set up Grok Bot to assist with drafting GitHub issues. Ask for missing information in the necessary order, and read related code, tests, and existing issues to match project terminology. Clearly distinguish whether reproduction was successful, and organize the summary, reproduction steps, expected behavior, and completion criteria in Markdown. Before posting the issue, let me review the draft and labels, and if you cannot post directly, provide a document for me to paste.

Do not speculate about account connection methods or results not in the original; first, provide the required setup and execution steps. Start from a working copy that preserves existing materials, and mark any items you cannot access as needing confirmation.

Verification: Check for duplicates with existing issues and ensure you do not claim to have reproduced anything that was not actually reproduced. Distinguish between feature requests and bug reports, and do not create public issues before my approval.

Along with the deliverable, organize the input used, execution logs, and confirmed results. Clearly separate incomplete or unexecuted parts from completed work.