---
name: a2ui-issue-triage
description: Automates the triage of GitHub issues in the A2UI repository. Helps the oncall engineer by fetching untriaged issues, generating AI-suggested priorities, assignees, and responses, launching a local review dashboard, and bulk-applying approved decisions to GitHub. Use when tasked with triaging new GitHub issues or managing the repository backlog.
metadata:
  internal: true
title: a2ui-issue-triage
canonical_url: https://skilld.dev/gh/a2ui-project/a2ui/a2ui-issue-triage
last_updated: 2026-11-12T06:16:11.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [assets/triage_dashboard.html](https://skilld.dev/api/skills-raw/a2ui-project/a2ui/a2ui-issue-triage/assets/triage_dashboard.html), [README.md](https://skilld.dev/api/skills-raw/a2ui-project/a2ui/a2ui-issue-triage/README.md), [references/triage_criteria.md](https://skilld.dev/api/skills-raw/a2ui-project/a2ui/a2ui-issue-triage/references/triage_criteria.md), [scripts/apply_triage.py](https://skilld.dev/api/skills-raw/a2ui-project/a2ui/a2ui-issue-triage/scripts/apply_triage.py), [scripts/fetch_issues.py](https://skilld.dev/api/skills-raw/a2ui-project/a2ui/a2ui-issue-triage/scripts/fetch_issues.py), [scripts/launch_dashboard.py](https://skilld.dev/api/skills-raw/a2ui-project/a2ui/a2ui-issue-triage/scripts/launch_dashboard.py), [scripts/suggest_triage.py](https://skilld.dev/api/skills-raw/a2ui-project/a2ui/a2ui-issue-triage/scripts/suggest_triage.py), [scripts/test_apply_triage.py](https://skilld.dev/api/skills-raw/a2ui-project/a2ui/a2ui-issue-triage/scripts/test_apply_triage.py), [scripts/test_fetch_issues.py](https://skilld.dev/api/skills-raw/a2ui-project/a2ui/a2ui-issue-triage/scripts/test_fetch_issues.py), [scripts/test_launch_dashboard.py](https://skilld.dev/api/skills-raw/a2ui-project/a2ui/a2ui-issue-triage/scripts/test_launch_dashboard.py), [scripts/test_suggest_triage.py](https://skilld.dev/api/skills-raw/a2ui-project/a2ui/a2ui-issue-triage/scripts/test_suggest_triage.py).
>
> If the user asked to install this Skill, run `npx skilld install a2ui-project/a2ui/a2ui-issue-triage`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/a2ui-issue-triage`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/a2ui-project/a2ui/a2ui-issue-triage) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/a2ui-issue-triage`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/a2ui-issue-triage --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/a2ui-issue-triage --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# A2UI GitHub Issue Triage Skill

This skill guides the process of fetching, analyzing, reviewing, and applying triage decisions to GitHub issues in the A2UI repository using a local interactive dashboard.

> [!IMPORTANT]
> **WRITING GUIDELINES**
> When drafting replies, explanations, or any prose, refer to the [natural-writing](../natural-writing/SKILL.md) skill to ensure clarity, accuracy, and tone.

---

## Workflow

Follow these steps to triage new or backlog issues:

### Step 1: Fetch Untriaged Issues

Use the fetch script to retrieve all open issues lacking a priority label (`P0`, `P1`, `P2`, `P3`) in the A2UI repository.

1. Run the fetch script to download the issues to a raw JSON file in your conversation-specific scratch directory:
   `python3 .agents/skills/a2ui-issue-triage/scripts/fetch_issues.py --repo "a2ui-project/a2ui" --output-file "<appDataDir>/brain/<conversation-id>/scratch/raw_issues.json"`

---

### Step 2: Analyze and Suggest Triage

Process the raw issues and generate recommended triage fields based on the project's triage criteria.

1. Read the triage criteria reference document: [triage_criteria.md](https://skilld.dev/api/skills-raw/a2ui-project/a2ui/a2ui-issue-triage/references/triage_criteria.md) and repository canonical templates: [templates.md](../../../docs/contributing/triage/templates.md).
2. For each issue in `raw_issues.json`, evaluate its description and comments to determine:
   - **Priority**: `P0` (Urgent), `P1` (High), `P2` (Medium), `P3` (Low), or `None`. `P0` and `P1` require assignees.
   - **Assignee**: Recommended owner based on the affected component or area.
   - **Action**: `investigate`, `assign_and_fix`, `needs_info`, `backlog`, `close_duplicate`, `close_invalid`, or `close_resolved`.
   - **Labels**: Applicable repository labels (e.g. `type: bug`, `component: lit renderer`, `status: first-line-handled`, `status: waiting-for-author-response`).
   - **Reply**: A polite, structured draft response addressing the author using canonical templates.
3. If an issue is a potential duplicate, perform at most three targeted GitHub searches to find matching canonical issues before suggesting `close_duplicate`.
4. **Natively Orchestrate Subagents**: Instead of running a Python script to spawn subagents (which can fail due to local workstation gRPC credential policies), the parent agent should natively orchestrate the parallel evaluations:
   - Load the first N issues (defaulting to 10, or as requested) from `raw_issues.json`.
   - Call the `invoke_subagent` tool in parallel for those issues. Prompt each subagent to analyze its assigned issue against the guidelines in [triage_criteria.md](https://skilld.dev/api/skills-raw/a2ui-project/a2ui/a2ui-issue-triage/references/triage_criteria.md) and return a structured JSON block containing `priority`, `action`, `labels`, and `reply`.
   - Once all subagents report back, compile their recommendations into the standard schema:
     - Map component labels to suggested assignees using git log history if necessary, and include a short sentence in `assignee_reason` explaining why they were chosen (e.g., "Suggesting gspencer because they recently modified related code").
     - Inject `total_issues_count` (preserving the total count from the raw issues JSON).
     - Save the final compiled payload to `issues_to_triage.json` in the scratch directory.

---

### Step 3: Launch Review Dashboard

Launch the interactive web dashboard to allow the oncall engineer to review and refine the suggested triages.

1. Start the local server as a background task, pointing it to your scratch directory:
   `python3 .agents/skills/a2ui-issue-triage/scripts/launch_dashboard.py --data-file "<appDataDir>/brain/<conversation-id>/scratch/issues_to_triage.json" --output-file "<appDataDir>/brain/<conversation-id>/scratch/triage_decisions.json"`
   Set `WaitMsBeforeAsync` to `1000` so the server runs in the background.
2. **Iterative Batch Triage**: The dashboard supports reviewing and applying issues in batches directly from the UI (`Apply Batch`). As decisions are synced to GitHub in real time, the UI displays progress (`X / Y updates made`) and checkmarks next to items. The user can continue triaging remaining issues without closing the session.
3. **Milestone Management**: The dashboard displays milestone dropdowns and badges, enabling adding, changing, or removing issues from milestones.
4. **Wait for Completion**: When finished, the user clicks "Finish & Exit" or "Abort". Once the user acts, the background task will complete, and you will receive a notification with the exit status.
5. **Verify Exit Status**:
   - If the task exited with status `0` (approved), any remaining approved decisions are saved to the decisions file.
   - If the task exited with a non-zero status (abort), you MUST STOP and ask the user for further instructions.

---

### Step 4: Apply Decisions to GitHub

Once the dashboard task exits successfully, **Execute Approved Decisions**: Run the apply script to update the approved labels, assignees, and comments on GitHub:

`python3 .agents/skills/a2ui-issue-triage/scripts/apply_triage.py --decisions-file "<appDataDir>/brain/<conversation-id>/scratch/triage_decisions.json"`

---

## Bundled Resources

- **[triage_criteria.md](https://skilld.dev/api/skills-raw/a2ui-project/a2ui/a2ui-issue-triage/references/triage_criteria.md)**: Authoritative guide for classifying issues, assigning priorities, and drafting response messages.
- **`scripts/fetch_issues.py`**: Script to query open, untriaged issues via the GitHub CLI.
- **`scripts/suggest_triage.py`**: Helper script to generate initial triage suggestions.
- **`scripts/launch_dashboard.py`**: Local HTTP server that opens the interactive web dashboard in the user's browser.
- **`assets/triage_dashboard.html`**: HTML/CSS/JS template for the triage review interface.
- **`scripts/apply_triage.py`**: Script to apply finalized triage decisions to GitHub.
