agentleFS
Sign inStart free
MicrosoftKnown publishermicrosoft-foundry/foundry-agent-webapp/.github/skills/triaging-issues/SKILL.md

triaging-issues

Skill124 starsChanged 7 months agoMITView on GitHub

Provides issue triage workflow, priority definitions, and report format. Use when analyzing GitHub issues and PRs, assessing priority, or generating triage reports.

5 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use github-linear-bridging and writing-quality.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • SentrySkill

    github-linear-bridging

    Conventions for bridging GitHub and Linear: creating Linear issues from GitHub issues, cross-referencing the two trackers, and checking whether a GitHub issue is already tracked in Linear. Load when asked to create Linear issues from GitHub issues, link the trackers in either direction, or report tracking status. Not needed for work that stays inside one tracker.

    Also in 3 projects that use this

  • SentrySkill

    writing-quality

    Writing-quality guardrails for any prose the agent drafts or edits: pull request descriptions, issue comments, review reports, Linear replies. Use this skill whenever writing or revising content meant for humans to read, to keep the prose natural, plain, and free of AI-sounding phrasing. Not needed for code, queries, or tool plumbing.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before deep-diving into an issue, search for duplicates:

    line 86
  2. Very specific:

    Use gh issue list --search "<keywords>" with key terms from the issue title and body.

    line 88
  3. Very specific:

    Check closed issues too: gh issue list --state closed --search "<keywords>".

    line 89
  4. Distinctive:

    If a duplicate exists, note it in the triage report with a cross-reference.

    line 90

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Issue Triage Guidance

Gather open issues and PRs, analyze them, and recommend next steps. Search the codebase to identify affected components — don't rely on hardcoded file mappings.

Priority Definitions

PriorityCriteria
🔴 CriticalProduction broken, security issue, data loss
🟠 HighMajor feature broken, blocking users
🟡 MediumFeature degraded, workaround exists
🟢 LowMinor issue, cosmetic, nice-to-have

Complexity Scale

SizeEstimate
SHours
M1-2 days
L3-5 days
XL1+ week

Label Taxonomy

PrefixValues
area:backend, frontend, auth, streaming, infra, docs
type:bug, feature, enhancement, chore, docs
priority:critical, high, medium, low

Triage Report Format

Open Issues Summary

#TitlePriorityTypeComplexity

Per Issue — #[number]: [title]

  • Priority / Type / Complexity
  • Affected Areas: checklist of areas
  • Relevant Files: table with file + reason
  • Suggested Labels: using taxonomy above
  • Recommended Next Steps: numbered list

Open PRs Summary

#TitleAuthorStatusFiles Changed

Per PR — #[number]: [title]

  • Status: Draft | Ready for review | Changes requested | Approved
  • Review Notes: concerns or things to check

gh CLI Commands for Read-Only Analysis

# List open issues
gh issue list --state open

# Search for potential duplicates
gh issue list --search "keyword"

# View issue details
gh issue view <number>

# List open PRs
gh pr list --state open

# View PR details and diff
gh pr view <number>
gh pr diff <number>

Duplicate Detection

Before deep-diving into an issue, search for duplicates:

  1. Use gh issue list --search "<keywords>" with key terms from the issue title and body.
  2. Check closed issues too: gh issue list --state closed --search "<keywords>".
  3. If a duplicate exists, note it in the triage report with a cross-reference.

Constraints

  • ❌ Read-only — do NOT modify issues or PRs
  • ❌ No gh issue edit, gh issue close, gh issue label
  • ❌ No gh pr merge, gh pr close, gh pr review --approve
  • ✅ Only use read commands: list, view, search, diff

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free