smaqit.utils.triage-issues

Automate GitHub issue triage and categorize issues as Blocking, Advisory, Historical, or Clear.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ruifrvaz/local-image-generator --skill smaqit-utils-triage-issues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: smaqit.utils.triage-issues
Source: https://github.com/ruifrvaz/local-image-generator/tree/main/.github/skills/smaqit.utils.triage-issues
Command: npx skills add https://github.com/ruifrvaz/local-image-generator --skill smaqit-utils-triage-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires curl, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of triaging issues from GitHub repositories, saving time and reducing manual effort.

Core Features & Use Cases

  • Automated Issue Triage: Classifies issues into categories like Blocking, Advisory, Historical, or Clear based on specific criteria.
  • GitHub Integration: Connects to GitHub API to fetch issue details and resolve tool names to owner/repo pairs.
  • Use Case: When starting a task, this Skill checks for open bugs and regressions related to the task, ensuring the task can proceed without issues.

Quick Start

Run the triage command for a specific task ID using: task.triage [id].

Frequently Asked Questions about smaqit.utils.triage-issues

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate issue triage for a GitHub repository?

Automating issue triage classifies open GitHub issues into categories like Blocking, Advisory, Historical, or Clear based on predefined criteria. This Skill resolves tool names to owner/repo pairs from URLs and uses the GitHub API to fetch real-time issue details.

What is the best way to check for blocking bugs before starting a development task?

Checking for blocking bugs involves running an automated triage command against a specific task ID. The process fetches open bugs and regressions from the GitHub API to ensure your task can proceed without encountering unresolved issues.

Does automated issue categorization work with standard GitHub REST API endpoints?

Automated issue categorization works with GitHub REST API endpoints by using curl to fetch data. It resolves repository URLs to owner/repo pairs and queries the API directly to retrieve real-time issue details for classification.

Can I use this issue triage workflow without installing additional dependencies?

You cannot use this triage workflow without curl, as it is the required dependency for making GitHub REST API requests. Ensure curl is installed in your environment to fetch issue details and resolve repository URLs.

Why does GitHub issue classification categorize tickets as Historical or Advisory?

GitHub issue classification uses predefined criteria to sort tickets into Blocking, Advisory, Historical, or Clear categories. This automated triage helps prioritize open bugs and regressions before beginning a new development task.

How do I run an automated triage command for a specific task?

Running an automated triage command for a specific task involves executing `task.triage [id]` with your task identifier. This initiates the GitHub API integration to fetch and classify relevant open issues.