-
Notifications
You must be signed in to change notification settings - Fork 343
Move triage instructions to a gemini skill #8736
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from 1 commit
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -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) | ||
|
helin24 marked this conversation as resolved.
Outdated
|
||
| - 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. | ||
This file was deleted.
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.