Skip to content

Commit b329c7d

Browse files
authored
Move triage instructions to a gemini skill (#8736)
This is from following https://geminicli.com/docs/cli/skills/ It seems better for organization to have this all in the .gemini folder. <img width="1113" height="445" alt="Screenshot 2026-01-28 at 9 10 26 AM" src="https://github.com/user-attachments/assets/c25fa528-8878-4aff-9a81-105383a3f43d" />
1 parent f7e0f7f commit b329c7d

3 files changed

Lines changed: 23 additions & 11 deletions

File tree

.gemini/skills/triage/SKILL.md

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
---
2+
name: triage-helper
3+
description: Assistance with triage of unprioritized issues. Use when the user asks for help with triage.
4+
---
5+
6+
When a user asks for help in the CLI:
7+
- Find the latest open issues in the https://github.com/flutter/flutter-intellij/ repo that don't have a priority label.
8+
- If you encounter authentication issues, guide the user to check their `github-mcp-server` setup or `gh auth status` depending on available tools.
9+
- Reference `docs/Triaging.md` for detailed setup instructions.
10+
- 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.
11+
- For each issue, give suggestions such as:
12+
- Close the issue if it's not relevant anymore (e.g. it's been fixed, the code it's referencing is outdated, etc.)
13+
- Suggest how to reproduce if it looks like it may be easy to reproduce locally
14+
- Ask for a reproduction with a small project if reproduction may be hard locally
15+
- Ask for more information and apply a waiting for response label
16+
- Note a code pointer for the issue if it could be a good first issue for an external contributor
17+
- Suggest a priority and other labels that may be relevant along with reasoning for the priority
18+
- Then wait for user feedback before continuing on to the next issue.
19+
20+
Avoid executing tasks on GitHub directly, such as making comments, applying labels, or closing issues.
21+
22+
There is additional context on our issue triage process in docs/Triaging.md.

docs/Triaging.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -68,7 +68,7 @@ Once in the gemini CLI, you can say something like "help me with triage". Exampl
6868
```
6969

7070
Notes:
71-
- There are instructions for gemini in the `tool/triage/GEMINI.md` file, and gemini should be able to access this whenever you start
71+
- There is a triage skill for gemini in the `.gemini/skills` directory, and gemini should be able to access this whenever you start
7272
`gemini` in the flutter-intellij directory.
7373
- This extension can also help with reviewing PRs, or any other tasks that require context from GitHub.
7474

tool/triage/GEMINI.md

Lines changed: 0 additions & 10 deletions
This file was deleted.

0 commit comments

Comments
 (0)