b1-triage-issue

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.

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.

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.

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.

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.