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

DevWalkthrough

Submitting Lint Fixes as a New Branch and Pull Request

This is an example where an agent responsible for lint fixes creates a branch and commit with the repository tools, then submits a pull request (PR).

n8n

How it works

  1. The author connects a GitHub test repository, the target file for modification, and the lint error details.
  2. The agent for fixes is connected to tools for listing and creating branches, creating file blobs, trees, and commits, and for creating pull requests.

Results

In this public example, the intended outcome is a branch with lint fixes and a pull request.

Notes

This is a public implementation example. Despite the name, it does not guarantee that linters for all languages will run or pass. The author reports that public configuration and tool connections were checked, but the process was not executed directly.

Source

n8n 공개 워크플로 #4073 Original post ↗

Example prompt · n8n

Goal: Submit lint fixes as a new branch and pull request.

Input/Environment: [Test repository], [Target branch], [Lint error], [Project validation command].

Reference original: https://n8n.io/workflows/4073-automate-github-pr-linting-with-google-gemini-ai-and-auto-fix-prs/

Prepare the configuration and connections so that a test environment can be created using the public setup from the original. If there are any missing sub-workflows, APIs, or account permissions, mark them as incomplete until actually connected.

Connections and materials to prepare: Connect the GitHub test repository, the file to be modified, and the lint error details.

Agent actions to implement: The fix agent is connected to tools for listing and creating branches, creating file blobs, trees, and commits, and for creating pull requests.

Scope of actions: This is a public implementation example. Despite the name, it does not guarantee that linters for all languages will run or pass.

The result should be a lint fix branch and a pull request. Also summarize the required setup steps and actual execution method. After checking the results returned by the tools, choose the next task, and separately note any materials that could not be accessed or tasks that could not be executed.

Verification: After the fix, run the linter separately to check if it passes, and when retrying, ensure that the same PR or changes are not duplicated. Clearly distinguish between the inputs used for verification, the actual outputs, and any items not yet confirmed.