git-issue-labeler

Automates assignment of relevant labels to GitHub issues based on content analysis.

4|4|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/darellchua2/opencode-config-template --skill git-issue-labeler
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-issue-labeler
Source: https://github.com/darellchua2/opencode-config-template/tree/main/skills/git-issue-labeler
Command: npx skills add https://github.com/darellchua2/opencode-config-template --skill git-issue-labeler

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintains consistent issue triage by automatically applying GitHub default labels to issues, reducing manual labeling time and human error.

Core Features & Use Cases

  • Analyze issue content to determine the most appropriate default labels (bug, enhancement, documentation, duplicate, good first issue, help wanted, invalid, question, wontfix).
  • Apply one or more labels to issues using the GitHub CLI and update label descriptions for reviewers.
  • Generate label assignment reports to aid maintainers and new contributors in understanding labeling decisions.
  • Ideal for large repositories or teams with strict labeling standards, enabling scalable triage workflows.

Quick Start

Install and authenticate the GitHub CLI, ensure you have write access to the target repository, then run the labeling workflow against issues to auto-apply labels based on content.

Frequently Asked Questions about git-issue-labeler

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

FAQPage Schema
How do I automatically label GitHub issues for triage?

You can automatically label GitHub issues by analyzing issue content and applying standard default labels like bug, enhancement, or documentation using keyword patterns. This automated issue triage reduces manual effort and maintains consistent categorization across repositories.

Can I categorize GitHub issues as bugs or enhancements without manual review?

Yes, you can categorize GitHub issues automatically by analyzing issue content against keyword patterns to determine appropriate default labels such as bug, enhancement, or question. This generates review-ready label reports for maintainers without requiring manual intervention.

Do I need the GitHub CLI to auto-apply default labels to issues?

Yes, you need the GitHub CLI installed and authenticated with write access to the target repository to auto-apply default labels to issues. The CLI queries existing repository labels and updates them to ensure accurate triage and categorization.

What is the best way to scale issue triage for a large GitHub repository?

Scaling issue triage for large GitHub repositories is best handled by automating default label application based on issue content analysis. This approach applies standard labels like duplicate or good first issue, reducing manual labeling time and human error.

How does automated issue labeling handle existing repository labels?

Automated issue labeling queries existing repository labels via the GitHub CLI and updates label descriptions for reviewers. It assigns one or more standard default labels to issues by matching content keyword patterns, ensuring accurate and consistent triage.

When should I not use automated labeling for GitHub issues?

You should avoid automated labeling for GitHub issues when repositories require highly custom, non-standard labels outside the default set like bug or enhancement. The mechanism relies on keyword patterns and standard default labels, which may not fit specialized triage workflows.