label-issue

Classify and label GitHub issues using repository-specific rules and content analysis.

1|2|Updated Dec 17, 2025
One-click install
npx skills add https://github.com/chagong/IssueLens --skill label-issue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: label-issue
Source: https://github.com/chagong/IssueLens/tree/main/.github/skills/label-issue
Command: npx skills add https://github.com/chagong/IssueLens --skill label-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the classification and labeling of GitHub issues, ensuring consistency and saving developers time on manual categorization.

Core Features & Use Cases

  • Automated Classification: Automatically assigns labels such as bug, feature, priority, and area based on issue content.
  • Rule-Based Labeling: Leverages repository-specific labeling instructions for accurate and customized labeling.
  • Use Case: When a new bug report is submitted, this skill can automatically label it as 'bug', assign a priority based on keywords like 'crash' or 'broken', and tag it with the relevant component like 'area:ui'.

Quick Start

Label issue #123 in microsoft/vscode with bug and priority:high labels.

Frequently Asked Questions about label-issue

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

FAQPage Schema
How do I automate GitHub issue labeling and triage?

Automate GitHub issue labeling by classifying new issues based on content analysis and repository-specific instructions. This skill assigns types, priorities, and areas to ensure consistent categorization without manual effort.

Can I automatically assign bug and priority labels to new GitHub issues?

Yes, you can automatically assign bug and priority labels to new GitHub issues. The skill analyzes issue content for keywords like 'crash' to apply accurate bug, priority, and area labels.

How does rule-based issue classification work for repositories?

Rule-based issue classification works by leveraging repository-specific labeling instructions to analyze issue content. It applies consistent rules to categorize issues by type, component, and priority automatically.

What's the best way to apply consistent labels to GitHub issues at scale?

The best way to apply consistent labels at scale is using automated content analysis. This skill triggers on requests to label or classify issues, applying customized repository rules to every new submission.

Do I need the requests library to automate issue classification?

Yes, you need the requests library installed to automate issue classification. This Python dependency enables the skill to interact with GitHub issues and apply labels based on content analysis.

Why does automated issue triage fail to tag the correct component area?

Automated issue triage may tag the wrong component area if repository-specific labeling instructions are missing or vague. Accurate area tagging requires defining clear keywords and rules for the skill to match against issue content.