Index of every page on this site: llms.txt
All skills
a2ui-project avatar

/a2ui-issue-triage

@6bf4cc2
by A2UIa2ui-project/a2ui18k stars
1,430
Run it yourself

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.

Use this Skill: https://skilld.dev/gh/a2ui-project/a2ui/a2ui-issue-triage

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencestriage_criteria.md

≈960 tokens on demand. Your agent reads this file only when SKILL.md points to it.

A2UI Issue Triage Criteria & Guidelines

This document defines the operational execution rules for classifying issues, assigning priorities, recommending owners, and drafting responses.


Canonical Sources of Truth

Refer directly to the project documentation for authoritative definitions and canonical response templates:


Issue Classification & Operational Action Flows

All triaged issues must be tagged with the status: first-line-handled label.

1. Bug Reports

  • Analysis:
    • Reproduction: Do not attempt local reproduction unless the steps are simple, clear, and the environment can be set up immediately. If you need to check out the branch or clone the PR repo to reproduce the issue, do it in a temporary clone or git worktree (e.g. in <appDataDir>/brain/<conversation-id>/scratch/issue_12345_repro/).
    • Static Analysis: For complex bugs, analyze the logs, stack traces, and relevant specification files (e.g., JSON schemas in specification/) to diagnose the issue.
  • Action:
    • If reproduction steps or logs are missing, set action to needs_info, apply the status: waiting-for-author-response label, and use the Requesting information template.
    • If verified, suggest the appropriate priority (P0 to P3) and recommend the owner of the affected component based on path mapping (e.g., paths with typescript/renderers/lit belong to the Lit renderer maintainer, specification/ to the specification maintainer) and file commit history (git log -n 5 --format="%ae" <file>).
    • Clean up any temporary files, worktrees, or clones when finished.

2. Feature Requests

  • Analysis:
    • Verify if the request aligns with the A2UI roadmap and design philosophy for the affected components.
  • Action:
    • If aligned, set action to backlog with priority P2 or P3 and suggest component/type labels (e.g., component: standard catalog specification, type: feature/enhancement).
    • If out of scope, set priority to None and action to close_invalid (closes the issue as not planned). Draft the response using the Out of Scope template.

3. Support Requests and Questions

  • Analysis:
    • Identify if the issue is a question about usage or setup rather than a bug.
  • Action:
    • Set action to close_resolved or close_invalid.
    • Answer the question directly or provide links to relevant guides (e.g., quickstart.mdx) or GitHub Discussions, then close the issue.

Response Guidelines

When drafting replies, always copy the exact response text from docs/contributing/triage/templates.md.

  • Be direct: State the action being taken or what is needed immediately.
  • Eliminate fluff: Do not use conversational filler (e.g., "I hope this helps").
  • Refer to templates: Keep draft comments synchronized with canonical templates.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

2 warnings3mo3 checks · Risk SAFE
  • Gen Agent Trust Hub3mo

    This skill automates the triage of GitHub issues for a specific repository. It includes tools to fetch issues, suggest labels/assignees via AI or git history, and provides a local web dashboard for human review before applying changes back to GitHub. The code follows secure practices, such as using DOMPurify for the dashboard and adhering to local gRPC credential policies.

  • Socket3mo

    2 alerts: gptAnomaly

  • Snyk3mo

    Risk: MEDIUM · 2 issues

Signed by skilld at 6bf4cc2. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated last week
metadata
{
  "internal": true
}

README badge

README badge for a2ui-project/a2ui/a2ui-issue-triage