Automated triage system to move GitHub issues through standardized states.

Install

mkdir -p .claude/skills/github-triage && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/11248" && unzip -o skill.zip -d .claude/skills/github-triage && rm skill.zip

Installs to .claude/skills/github-triage

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Triage GitHub issues through a configurable label-based state machine. Use when user wants to triage incoming issues, prepare issues for an autonomous agent, or move an issue between workflow states. Repo inferred from `git remote`; all GitHub calls go through `gh`.
266 chars✓ has a “when” triggerlonger than Claude Code's old 250-char listing cap (fine on current versions)
Intermediate

Key capabilities

  • →Triage incoming GitHub issues using a state machine
  • →Map repository labels to abstract workflow states
  • →Prepare issues for autonomous agent processing
  • →Enforce mandatory AI disclaimers on all comments
  • →Group open issues by triage status

How it works

It uses a state-machine approach to transition issues between labels like triage_pending and ready_for_agent, ensuring every interaction includes a mandatory AI disclaimer.

Inputs & outputs

You give it
GitHub issue URL or repository context
You get back
Labeled issue with updated state and AI disclaimer

When to use github-triage

  • →Triage incoming issue reports
  • →Prepare issues for agent processing
  • →Standardize issue status transitions

About github-triage

Uses a state-machine approach to label and manage GitHub issues. Enforces AI disclaimers and maps repository labels to clear workflow states.

Triage GitHub issues through a configurable label-based state machine. Use when user wants to triage incoming issues, prepare issues for an autonomous agent, or move an issue between workflow states. Repo inferred from `git remote`; all GitHub calls go through `gh`.

When not to use it

  • →When state semantics need to deviate from the predefined machine

Limitations

  • →State semantics are not configurable
  • →Requires exactly one category and one state label per issue

How it compares

It automates the triage process through a configurable label map rather than requiring manual label management for every issue.

Compared to similar skills

github-triage side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
github-triage (this skill)05moNo flagsIntermediate
triage-issue18moReviewIntermediate
proof-of-work18moNo flagsIntermediate
checkpointing07moNo flagsIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

triage-issue

mysticaltech

Use when triaging a GitHub issue - analyzes issue, checks for duplicates, categorizes, and drafts response

12

proof-of-work

MadAppGang

Proof artifact generation patterns for task validation. Covers screenshots, test results, deployments, and confidence scoring.

10

checkpointing

arugo11

Run full session checkpointing from Codex without Claude dependencies. Collect git and CLI activity, generate checkpoint files, update session history, and analyze reusable skill patterns.

00

label-issue

chagong

Classify and label GitHub issues based on repository-specific labeling instructions. Use when (1) auto-labeling new issues, (2) classifying issue types (bug, feature, etc.), (3) adding priority or area labels, (4) applying consistent labeling rules. Triggers on requests like "label issue", "classify

00

resolve-conflicts

antinomyhq

Use this skill immediately when the user mentions merge conflicts that need to be resolved. Do not attempt to resolve conflicts directly - invoke this skill first. This skill specializes in providing a structured framework for merging imports, tests, lock files (regeneration), configuration files, and handling deleted-but-modified files with backup and analysis.

81334

git-advanced-workflows

wshobson

Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.

1197

Search skills

Search the agent skills registry