Name: triage
Author: accesswatch

Prompt file imported from accesswatch/agent-forge (.github/prompts/triage.prompt.md). Fill in {{scope}} before use. Copyright stays with the author.

Generate a triage dashboard document and save it to the workspace in both markdown and HTML formats.

Steps

Get the authenticated user with #tool:mcp_github_github_get_me.
Load repo scope from .github/agents/preferences.md if present. By default, search ALL accessible repos.
Search for open issues created by or assigned to the user with #tool:mcp_github_github_search_issues. Apply any scope filter provided. If a repo or org is specified, add repo: or org: qualifier; otherwise search cross-repo.
For each issue, fetch full details with #tool:mcp_github_github_issue_read to get comment counts, labels, reactions, and recent activity.
Gather enhanced data:
- Reactions on each issue -- flag as Popular (5+), Controversial, or Quiet
- Release context -- check milestones and upcoming releases
- Discussions -- check for related GitHub Discussions
- Team activity -- who else is involved
Score each issue using the enhanced priority system:
- +3 --> @mentioned in recent comments
- +3 --> Tied to an upcoming release milestone
- +2 --> P0/P1/critical/urgent labels
- +2 --> New comments since last visit
- +2 --> High community interest (5+ positive reactions)
- +1 --> Bug label
- +1 --> Has active related discussion
- -1 --> Wontfix/duplicate labels
- -2 --> Stale (no activity >30 days)
Create BOTH triage dashboard documents:
- Markdown: .github/reviews/issues/triage-{date}.md
- HTML: .github/reviews/issues/triage-{date}.html With sections:
- Needs Immediate Action (score >= 4) -- issues with action items, reactions, release context
- Review When Possible (score 1-3) -- issues with activity
- Active Discussions -- related GitHub Discussions needing attention
- Monitor (score <= 0) -- quiet/stale issues
- Decision checkboxes: Reply, Close, Reassign, Defer
- Quick-action links to each issue on GitHub
- Community reactions summary for each issue
Confirm: "Triage dashboard saved to {md-path} and {html-path} with {N} issues. {X} need immediate action, {Y} are popular with the community."

Generate a triage dashboard document and save it to the workspace in both markdown and HTML formats. {{scope}} ## Steps 1. Get the authenticated user with #tool:mcp_github_github_get_me. 2. Load repo scope from `.github/agents/preferences.md` if present. By default, search ALL accessible repos. 3. Search for open issues created by or assigned to the user with #tool:mcp_github_github_search_issues. Apply any scope filter provided. If a repo or org is specified, add `repo:` or `org:` qualifier; otherwise search cross-repo. 3. For each issue, fetch full details with #tool:mcp_github_github_issue_read to get comment counts, labels, reactions, and recent activity. 4. Gather enhanced data: - **Reactions** on each issue -- flag as Popular (5+), Controversial, or Quiet - **Release context** -- check milestones and upcoming releases - **Discussions** -- check for related GitHub Discussions - **Team activity** -- who else is involved 5. Score each issue using the enhanced priority system: - +3 --> @mentioned in recent comments - +3 --> Tied to an upcoming release milestone - +2 --> P0/P1/critical/urgent labels - +2 --> New comments since last visit - +2 --> High community interest (5+ positive reactions) - +1 --> Bug label - +1 --> Has active related discussion - -1 --> Wontfix/duplicate labels - -2 --> Stale (no activity >30 days) 6. Create BOTH triage dashboard documents: - Markdown: `.github/reviews/issues/triage-{date}.md` - HTML: `.github/reviews/issues/triage-{date}.html` With sections: - **Needs Immediate Action** (score >= 4) -- issues with action items, reactions, release context - **Review When Possible** (score 1-3) -- issues with activity - **Active Discussions** -- related GitHub Discussions needing attention - **Monitor** (score <= 0) -- quiet/stale issues - Decision checkboxes: Reply, Close, Reassign, Defer - Quick-action links to each issue on GitHub - Community reactions summary for each issue 7. Confirm: _"Triage dashboard saved to `{md-path}` and `{html-path}` with {N} issues. {X} need immediate action, {Y} are popular with the community."_

{ "prompt": "Generate a triage dashboard document and save it to the workspace in both markdown and HTML formats.\n\n{{scope}}\n\n## Steps\n\n1. Get the authenticated user with #tool:mcp_github_github_get_me.\n2. Load repo scope from `.github/agents/preferences.md` if present. By default, search ALL accessible repos.\n3. Search for open issues created by or assigned to the user with #tool:mcp_github_github_search_issues. Apply any scope filter provided. If a repo or org is specified, add `repo:` or `org:` qualifier; otherwise search cross-repo.\n3. For each issue, fetch full details with #tool:mcp_github_github_issue_read to get comment counts, labels, reactions, and recent activity.\n4. Gather enhanced data:\n - **Reactions** on each issue -- flag as Popular (5+), Controversial, or Quiet\n - **Release context** -- check milestones and upcoming releases\n - **Discussions** -- check for related GitHub Discussions\n - **Team activity** -- who else is involved\n5. Score each issue using the enhanced priority system:\n - +3 --> @mentioned in recent comments\n - +3 --> Tied to an upcoming release milestone\n - +2 --> P0/P1/critical/urgent labels\n - +2 --> New comments since last visit\n - +2 --> High community interest (5+ positive reactions)\n - +1 --> Bug label\n - +1 --> Has active related discussion\n - -1 --> Wontfix/duplicate labels\n - -2 --> Stale (no activity >30 days)\n6. Create BOTH triage dashboard documents:\n - Markdown: `.github/reviews/issues/triage-{date}.md`\n - HTML: `.github/reviews/issues/triage-{date}.html`\n With sections:\n - **Needs Immediate Action** (score >= 4) -- issues with action items, reactions, release context\n - **Review When Possible** (score 1-3) -- issues with activity\n - **Active Discussions** -- related GitHub Discussions needing attention\n - **Monitor** (score <= 0) -- quiet/stale issues\n - Decision checkboxes: Reply, Close, Reassign, Defer\n - Quick-action links to each issue on GitHub\n - Community reactions summary for each issue\n7. Confirm: _\"Triage dashboard saved to `{md-path}` and `{html-path}` with {N} issues. {X} need immediate action, {Y} are popular with the community.\"_", "variables": [ "scope" ], "notes": "Generate a prioritized triage dashboard document (markdown + HTML) for your open issues across all repos with reactions, release context, and discussion links Tools: github/*, createFile, createDirectory, ask_questions.", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/accesswatch/agent-forge", "path": ".github/prompts/triage.prompt.md", "ref": "18da63278eab6582a48c1df0bf22df93b217d26e", "url": "https://github.com/accesswatch/agent-forge/blob/18da63278eab6582a48c1df0bf22df93b217d26e/.github/prompts/triage.prompt.md", "key": "accesswatch/agent-forge/.github/prompts/triage.prompt.md" } } }

triage

About

Steps

Use it

Manifest

Reviews