From 49baa4ed90032296f12215c1a548a43237386518 Mon Sep 17 00:00:00 2001 From: Helin Shiah Date: Wed, 28 Jan 2026 10:08:16 -0800 Subject: [PATCH 1/3] Move triage instructions to a gemini skill --- .gemini/skills/triage/SKILL.md | 21 +++++++++++++++++++++ tool/triage/GEMINI.md | 10 ---------- 2 files changed, 21 insertions(+), 10 deletions(-) create mode 100644 .gemini/skills/triage/SKILL.md delete mode 100644 tool/triage/GEMINI.md diff --git a/.gemini/skills/triage/SKILL.md b/.gemini/skills/triage/SKILL.md new file mode 100644 index 000000000..e8b85c6e3 --- /dev/null +++ b/.gemini/skills/triage/SKILL.md @@ -0,0 +1,21 @@ +--- +name: triage-helper +description: Assistance with triage of unprioritized issues. Use when the user asks for help with triage. +--- + +When a user asks for help in the CLI: +- Find the latest open issues in the flutter/flutter-intellij repo that don't have a priority label. +- (Prompt the user for their personal access token if needed) +- Consider the most recently updated issues first. Start presenting issues one at a time to the user, with the issue URL and other relevant information. +- For each issue, give suggestions such as: + - Close the issue if it's not relevant anymore (e.g. it's been fixed, the code it's referencing is outdated, etc.) + - Suggest how to reproduce if it looks like it may be easy to reproduce locally + - Ask for a reproduction with a small project if reproduction may be hard locally + - Ask for more information and apply a waiting for response label + - Note a code pointer for the issue if it could be a good first issue for an external contributor + - Suggest a priority and other labels that may be relevant along with reasoning for the priority +- Then wait for user feedback before continuing on to the next issue. + + + +Avoid executing tasks on GitHub directly, such as making comments, applying labels, or closing issues. \ No newline at end of file diff --git a/tool/triage/GEMINI.md b/tool/triage/GEMINI.md deleted file mode 100644 index 31f84e187..000000000 --- a/tool/triage/GEMINI.md +++ /dev/null @@ -1,10 +0,0 @@ -Steps for triage when a user asks for help in the CLI: -- Find the latest open issues in the flutter/flutter-intellij repo that don't have a priority label. -- Consider the most recently updated issues first. Start presenting issues one at a time to the user. -- For each issue, give suggestions such as: - - Close the issue if it's not relevant anymore (e.g. it's been fixed, the code it's referencing is outdated, etc.) - - Suggest how to reproduce if it looks like it may be easy to reproduce locally - - Ask for a reproduction with a small project if reproduction may be hard locally - - Ask for more information and apply a waiting for response label - - Note a code pointer for the issue if it could be a good first issue for an external contributor - - Suggest a priority and other labels that may be relevant along with reasoning for the priority From cb310354637bf75437c75d976e2299fed5074da8 Mon Sep 17 00:00:00 2001 From: Helin Shiah Date: Thu, 29 Jan 2026 10:47:19 -0800 Subject: [PATCH 2/3] Refer to triaging doc in skill and vice versa --- .gemini/skills/triage/SKILL.md | 6 +++--- docs/Triaging.md | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/.gemini/skills/triage/SKILL.md b/.gemini/skills/triage/SKILL.md index e8b85c6e3..649540518 100644 --- a/.gemini/skills/triage/SKILL.md +++ b/.gemini/skills/triage/SKILL.md @@ -4,7 +4,7 @@ description: Assistance with triage of unprioritized issues. Use when the user a --- When a user asks for help in the CLI: -- Find the latest open issues in the flutter/flutter-intellij repo that don't have a priority label. +- Find the latest open issues in the https://github.com/flutter/flutter-intellij/ repo that don't have a priority label. - (Prompt the user for their personal access token if needed) - Consider the most recently updated issues first. Start presenting issues one at a time to the user, with the issue URL and other relevant information. - For each issue, give suggestions such as: @@ -16,6 +16,6 @@ When a user asks for help in the CLI: - Suggest a priority and other labels that may be relevant along with reasoning for the priority - Then wait for user feedback before continuing on to the next issue. +Avoid executing tasks on GitHub directly, such as making comments, applying labels, or closing issues. - -Avoid executing tasks on GitHub directly, such as making comments, applying labels, or closing issues. \ No newline at end of file +There is additional context on our issue triage process in docs/Triaging.md. \ No newline at end of file diff --git a/docs/Triaging.md b/docs/Triaging.md index 77b19e53d..ec54c29a7 100644 --- a/docs/Triaging.md +++ b/docs/Triaging.md @@ -68,7 +68,7 @@ Once in the gemini CLI, you can say something like "help me with triage". Exampl ``` Notes: -- There are instructions for gemini in the `tool/triage/GEMINI.md` file, and gemini should be able to access this whenever you start +- There is a triage skill for gemini in the `.gemini/skills` directory, and gemini should be able to access this whenever you start `gemini` in the flutter-intellij directory. - This extension can also help with reviewing PRs, or any other tasks that require context from GitHub. From 46561de3d512dd43f4a465a366dbb82d624efd1d Mon Sep 17 00:00:00 2001 From: Helin Shiah Date: Wed, 4 Feb 2026 09:06:28 -0800 Subject: [PATCH 3/3] Add more specific instructions for auth --- .gemini/skills/triage/SKILL.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/.gemini/skills/triage/SKILL.md b/.gemini/skills/triage/SKILL.md index 649540518..4ef538ed3 100644 --- a/.gemini/skills/triage/SKILL.md +++ b/.gemini/skills/triage/SKILL.md @@ -5,7 +5,8 @@ description: Assistance with triage of unprioritized issues. Use when the user a When a user asks for help in the CLI: - Find the latest open issues in the https://github.com/flutter/flutter-intellij/ repo that don't have a priority label. -- (Prompt the user for their personal access token if needed) +- If you encounter authentication issues, guide the user to check their `github-mcp-server` setup or `gh auth status` depending on available tools. +- Reference `docs/Triaging.md` for detailed setup instructions. - Consider the most recently updated issues first. Start presenting issues one at a time to the user, with the issue URL and other relevant information. - For each issue, give suggestions such as: - Close the issue if it's not relevant anymore (e.g. it's been fixed, the code it's referencing is outdated, etc.)