priorizar

To automatically triage GitHub issues, this Skill scans open issues without labels and assigns categories like 'app:client', 'area:*', and 'bug' based on their titles and bodies. It then routes them to designated project backlogs for streamlined organization.

Yes, you can use GitHub CLI to organize issues into project backlogs. This Skill integrates directly with the GitHub CLI to list, edit, and add issues to specific project boards like 'Backlog CLIENTE' or 'Backlog NEGOCIO', updating their status efficiently.

The best way to manage a large backlog of unlabelled issues is through automated mass triaging. This Skill processes open unlabelled issues in bulk, determining appropriate labels and backlog destinations to make accumulated items quickly actionable.

Yes, automated issue labeling requires the 'gh' dependency. The Skill relies entirely on the GitHub CLI to interact with repositories, list open issues, apply labels, and manage project board integrations.

Automated issue categorization determines labels by analyzing the text within issue titles and bodies. Based on the content, it assigns relevant labels such as 'bug', 'enhancement', or 'documentation' and routes them to the appropriate Frontend or Backend backlog.

You should avoid using automated triage if your repository lacks established label schemas or designated project backlogs. The Skill requires pre-existing label categories and target boards to accurately categorize and route unlabelled issues.