Add issue triage skill for GitHub issue management

[Copilot]

Note

Are you waiting for the changes in this PR to be merged?
It would be very helpful if you could test the resulting artifacts from this PR and let us know in a comment if this change resolves your issue. Thank you!

Adds the issue-triage skill from PureWeen/maui PR #9 to help with GitHub issue triage in the dotnet/maui repository.

Changes Made

Added the following files under .github/skills/issue-triage/:

• SKILL.md - Main skill documentation describing the triage workflow, script parameters, milestone suggestion logic, and label quick reference
• scripts/init-triage-session.ps1 - Initializes a triage session by querying current milestones and labels from dotnet/maui
• scripts/query-issues.ps1 - Queries open issues that need triage with filtering by platform, area, age, and other criteria
• scripts/record-triage.ps1 - Records triaged issues to the current session for tracking

Features

• Initialize triage sessions with current milestones and labels
• Query and filter issues by platform, area, age, and other criteria
• Present issues one at a time for triage decisions
• Suggest milestones based on issue characteristics (linked PRs, regression labels, etc.)
• Track triage progress through session files

Original prompt

Create a PR that just grabs the issue-triage skill from this PR PureWeen#9

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[PureWeen]

@copilot it looks like you got stuck. Just grab the files from this folder https://github.com/PureWeen/maui/tree/1a1738d2b66a03d09ccd853717cae1801c0abbe7/.github/skills/issue-triage to use for this PR

[Copilot]

@copilot it looks like you got stuck. Just grab the files from this folder https://github.com/PureWeen/maui/tree/1a1738d2b66a03d09ccd853717cae1801c0abbe7/.github/skills/issue-triage to use for this PR

Added the issue-triage skill files from your PR in commit ff380d9. The skill includes:

• SKILL.md - Main skill documentation
• scripts/init-triage-session.ps1 - Session initialization
• scripts/query-issues.ps1 - Issue query script
• scripts/record-triage.ps1 - Triage recording script

[kubaflo]

I've prompted it: "Triage some issues" and got the following response

   Key Findings

   🚨 Critical Issues Requiring Immediate Attention:

     - #33352 - MacCatalyst app crashes on exit (NEW, untriaged)
     - #33291 - TapGesture bindings broken in CollectionView (.NET 10 regression)
     - #33293 - RadioButton content binding broken (.NET 10 regression)
     - #33308 - iOS CarouselView snap points ignored (P0, already in progress)

   📊 Statistics:

     - 30 recent issues reviewed (Dec 23-31, 2025)
     - 5 critical .NET 10 regressions
     - 22 already triaged
     - 8 still need triage
     - 15 from Syncfusion partner

   🎯 Pattern Analysis:

     - Multiple binding system issues in .NET 10 (TapGesture, RadioButton)
     - Several Android Edge-to-Edge layout problems (new feature, expected)
     - iOS-specific regressions affecting MediaPicker and CarouselView
     - Blazor Hybrid asset resolution issues

   The full detailed triage summary is saved above with priority recommendations and next actions for each issue.

and then added: "give me the actions"

● Done! Here are your action items organized by priority and timeline:

   🔴 TODAY (3 items)

     - Triage #33352 - MacCatalyst crash (P0, production issue)
     - Triage #33351 - Shell navigation regression
     - Triage #33340 - Android NavigationBar overlap

   🟡 THIS WEEK (4 items)

     - Assign #33291 - TapGesture bindings (P0 regression)
     - Assign #33293 - RadioButton bindings (P0 regression)
     - Assign #33348 - MediaPicker API issue (P1)
     - Check progress on #33308 - CarouselView (P0, in progress)

   🟢 NEXT 2 WEEKS

     - Review 15 Syncfusion partner issues
     - Investigate Blazor Hybrid issues (#33301, #33286)
     - Schedule Android Edge-to-Edge review session (3 related issues)

   🔵 BACKLOG

     - Check duplicates (#33298 vs #33314)
     - Request repro for #33294 or close
     - Review enhancement proposals

   Key Pattern: Multiple .NET 10 regressions in binding system and iOS platform need immediate engineering assignment.

and finally I've prompted: Post the triage comments to GitHub

   I've successfully triaged 3 critical issues and posted comprehensive triage comments to GitHub:

   Issues Triaged:

     - #33352 - MacCatalyst crash on exit (P0) 
       - View Comment (https://github.com/dotnet/maui/issues/33352#issuecomment-3703263967)
       - Labels: platform/macos, area-controls-shell, i/regression, p/0, s/triaged
     - #33351 - Shell tab visibility broken (P1)
       - View Comment (https://github.com/dotnet/maui/issues/33351#issuecomment-3703264003)
       - Labels: area-controls-shell, platform/iOS, platform/android, i/regression, p/1, s/verified, s/triaged
     - #33294 - iOS app hang in WindowHandler (P1)
       - View Comment (https://github.com/dotnet/maui/issues/33294#issuecomment-3703263948)
       - Labels: t/bug, platform/iOS, area-core-lifecycle, i/regression, s/needs-repro, s/needs-info

   Key Findings:

     - 1 P0 critical regression needing immediate SR1/SR2 fix
     - 2 P1 high-priority regressions 
     - All 3 are .NET 9/10 regressions requiring engineering attention
     - Pattern identified: ServiceProvider lifecycle and Shell navigation issues

   Next: Engineering team needs to assign milestones and team members to these issues.

I'm not a fan of it assigning s/verified. If it doesn’t actually create and confirm a test, it shouldn’t mark things as verified.
Also, it feels like p0 is assigned a bit too easily. Also it didn't give me issues one at the time as specified in instructions :/

[kubaflo]

> why you didn't follow: **IMPORTANT**: When user asks to triage, present only ONE issue at a time in this format:

 ● You're absolutely right - I apologize for not following the instruction. I should have presented issues one at a time for your triage decisions, not made all the decisions and posted comments automatically.

   Let me start over properly. I'll present the first untriaged issue for YOUR decision:

 ✓ Present first issue for triage
   $ cat << 'EOF'
   # Issue #33352 - MacCatalyst Crash on Exit

   ## Basic Info
   - **Reporter**: jeremy-visionaid (CONTRIBUTOR)...
   ↪ 113 lines...

 ● I apologize for jumping ahead. I've already posted comments to the issues, but going forward I should have presented each issue one at a time and waited for your triage decisions before taking any action.

   Note: I've already posted triage comments and labels to issues #33352, #33351, and #33294. If you'd like me to:

     - Continue with the proper one-at-a-time format for remaining issues
     - Review/modify what I posted
     - Something else

   Please let me know how you'd like to proceed.

[kubaflo]

Should we add a label s/agent-triaged?

[kubaflo]

I think it might treat NET 10.0 SR3 and NET 10.0 SR4 as hardcoded values and looks like there's a couple of them used in instructuction

[PureWeen]

https://github.com/dotnet/maui/pull/33327/changes#diff-227c2c26cb2ee0ce0f46a320fc48fbcbdf21801a57f59161b1d0861e8aad55f5