personal-issue-triage

name	personal-issue-triage
description	Automated issue triage for Flutter teams based on docs/triage/README.md. Fetches issues for a specific team, recommends team assignment or priority, and provides a summary report.

Personal Issue Triage

This skill automates the routine triage of incoming GitHub issues by following the living standards in docs/triage/README.md. It can be used by any subteam to process their specific triage queue.

Workflow

1. Automated Analysis & Querying

• Automated Triage Execution: Run the automated Python triage script, specifying the target team (e.g., framework or engine):

  python3 .agents/skills/personal-issue-triage/scripts/triage_issues.py --team framework
  

• Under-the-Hood Processing: The script automatically parses docs/triage/README.md to locate the team's incoming issue query, retrieves the issues, runs dart analyze syntax checks on any provided reproduction blocks, scans for duplicates, and mathematically suggests a baseline priority:
  • P2 is assigned as the default baseline for standard valid bugs.
  • P3 is assigned as the default baseline for new feature requests/proposals.
  • P1/P0 are assigned for critical regressions, crashes, or release blockers.

2. Review & Refine Triage Draft

• Report File Placement: Always write/save the final report file directly in the user's workspace root (e.g. issue_triage_report_framework.md) so the user has immediate access to review it in their editor.
• Priority Grouping: Always organize issues in the report by priority level after the 🚨 Urgent Attention section. Group the 📥 Standard Queue into subsections for P0, P1, P2, P3, and Routing / Other Teams rather than mixing priorities together.
• Succinct Formatting: Keep issue entries clean and succinct. Use at most two sub-bullet points per issue: one for the 1-sentence Summary, and one combined line for Action, Verification Status, and Duplicates. Omit repetitive boilerplate rationale strings.
• Summary Polishing: For each issue, write a brief 1-sentence explanation of the problem statement.
• Verify Linter Warnings: If the linter reported structural syntax errors under Verification Status, confirm if it is a user code error and note it.
• Deduplication Validation: Review the automatically appended Potential Duplicates links to check if this is indeed a duplicate of an existing issue.

3. User Approval & Label Application

• Present the completed Issue Triage Report to the user for review (providing a link to the workspace file file:///.../issue_triage_report_<team>.md).
• Once approved, apply the priority and triage labels using:

  gh issue edit <ISSUE_NUMBER> --add-label "<LABEL_1>,<LABEL_2>"
  

• Provide a final summary of actions.

References

• docs/triage/README.md - Living triage standards and search links.
• references/priority.md - Local P0-P3 definitions and urgency signals.