VidBee Issue Triage

Perform lightweight triage so users receive actionable documentation guidance, duplicate discussions converge on a canonical issue, and development work retains clear reproduction evidence. The default repository is nexmoe/VidBee. Maintain #247, VidBee issue triage dashboard as the primary dashboard.

Scope and execution mode

• Requests to screen, analyze, suggest actions, or work read-only authorize reading and drafting without GitHub changes. Requests to process, clean up, execute, or explicitly use this skill to handle issues authorize comments, label and title updates, consolidation of confirmed duplicates, and synchronization of actual results to #247 within the requested scope. Follow narrower user constraints and do not ask again for authorization already given.
• When no issue range is specified, review open issues and search both open and closed history for comparison. Treat historical closed issues as read-only by default; do not reopen or rewrite them in bulk.
• Write new GitHub titles, comments, label descriptions, and maintained repository triage records in English. Keep public issue comments short (see Comment style). Report to the current user in the conversation's language. Preserve reporters' original text.
• Prefer gh and specify the repository explicitly with --repo in every repository command. Use local command help to check supported flags.
• Creating or editing this skill does not initiate live issue processing. This workflow covers screening and routing, including read-only repository code search for preliminary bug judgment. It does not implement fixes, commit application code, open fix PRs, create upstream issues, or publish website documentation.

1. Read reports and consult current documentation