From 2a513fd5756b5cd3393cffc4b6f54f5487fe8090 Mon Sep 17 00:00:00 2001 From: Coco Sheng Date: Wed, 6 May 2026 16:28:57 -0400 Subject: [PATCH] docs: clarify that the prompt should command Gemini to both label the issue and modify its body/title on github --- scripts/backlog-analysis/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/scripts/backlog-analysis/README.md b/scripts/backlog-analysis/README.md index 9a8eb2b60e..effeae05dd 100644 --- a/scripts/backlog-analysis/README.md +++ b/scripts/backlog-analysis/README.md @@ -40,12 +40,12 @@ python3 fetch_from_url.py "https://github.com/google-gemini/gemini-cli/issues/?q If you have a list of uncategorized issues fetched from GitHub, your first step should be to classify them. You can use the Gemini CLI directly in your terminal -to classify them in the local file and label them on GitHub. +to classify them in the local file and modify them on GitHub. **Example command:** ```bash -gemini "Read data/uncategorized.json. For each issue, determine if it is a bug or a feature request. 1. Update the JSON object in the file to include a 'type' field set to 'bug' or 'feature'. 2. Use the gh CLI tool to add either the 'type/bug' or 'type/feature' label directly to the issue on GitHub." +gemini "Read data/uncategorized.json. For each issue, determine if it is a bug or a feature request. 1. Update the JSON object in the file to include a 'type' field set to 'bug' or 'feature'. 2. Use the gh CLI tool to act on the GitHub issue: (a) Add the 'type/bug' or 'type/feature' label, and (b) Edit the issue body or title to explicitly denote the type." ``` _Note: Make sure your `gemini-cli` has permission to execute shell commands if