b1-triage-issue

Evaluate GitHub issues by applying labels, assessing complexity, and identifying risks.

6|Updated Jun 14, 2026

Search Tags:#code review #github #risk assessment #issue triage #automated labeling

Ready to run

npx skills add https://github.com/jporre/sveltekit-verticalslices --skill b1-triage-issue

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: b1-triage-issue
Source: https://github.com/jporre/sveltekit-verticalslices/tree/main/skills/b1-triage-issue
Command: npx skills add https://github.com/jporre/sveltekit-verticalslices --skill b1-triage-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the triage process for GitHub issues, including label application, complexity evaluation, and risk assessment, saving developers time and reducing the likelihood of misclassifying issues.

Core Features & Use Cases

Automated Issue Triage: Evaluates and labels GitHub issues based on predefined criteria.
Complexity Evaluation: Determines the level of complexity based on the number of files involved.
Risk Assessment: Flags potential risks like security issues and data integrity concerns.
Use Case: When you receive a new GitHub issue, use this Skill to quickly assess its readiness for development, ensuring proper categorization and understanding of the task.

Quick Start

Run the b1-triage-issue skill on a new GitHub issue to evaluate and label it automatically.

Frequently Asked Questions about b1-triage-issue

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

FAQPage Schema

How do I automate GitHub issue triage with risk assessment and complexity evaluation?▼

Automating GitHub issue triage involves evaluating issues by applying labels, assessing complexity based on file involvement, and identifying risks like security concerns. This process requires the GitHub CLI to manipulate issues and operates within a forked worktree context to safely assess issue readiness without impacting the main codebase.

What is issue triage in code review and when do I need automated labeling?▼

Issue triage in code review is the process of categorizing new GitHub issues by applying predefined labels, determining complexity, and flagging risks. You need automated labeling when you receive new issues and want to quickly assess their readiness for development to ensure proper categorization and reduce misclassification time.

Do I need the GitHub CLI to perform automated issue triage and risk assessment?▼

Yes, you need the GitHub CLI installed to perform automated issue triage. The Skill requires the CLI to manipulate issues directly, apply labels, and operate within a forked worktree environment to ensure the main codebase remains unaffected during the evaluation process.

Can I evaluate GitHub issues without impacting my main codebase?▼

Yes, you can evaluate GitHub issues without impacting your main codebase by operating within a forked worktree. The issue triage Skill safely runs its complexity evaluation and risk assessment processes within this isolated environment, ensuring your primary repository remains untouched during issue manipulation.

What's the best way to assess issue complexity and identify security risks in GitHub?▼

The best way to assess issue complexity and identify security risks is using an automated triage Skill that determines complexity based on the number of files involved and flags potential data integrity concerns. This structured evaluation ensures proper categorization and readiness assessment for development.