Triage Issues

Analyze open GitHub issues and produce a sequenced implementation plan — grouping issues into parallel batches, ordering those batches, and tagging each issue with its recipe route. Use when user says "triage issues", "prioritize issues", or "plan issue order".

5 stars 1 forksGit & Code Review

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add TalonT-Org/AutoSkillit --skill triage-issues
Manual install
git clone --depth 1 https://github.com/TalonT-Org/AutoSkillit.git /tmp/AutoSkillit
mkdir -p ~/.claude/skills
cp -r /tmp/AutoSkillit/src/autoskillit/skills_extended/triage-issues ~/.claude/skills/triage-issues

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Issue Triage Skill

Analyze open GitHub issues, classify each into a recipe route, group them into parallel implementation batches, and produce a structured triage report.

## When to Use

- User says "triage issues", "prioritize issues", or "plan issue order"
- Before starting a multi-issue implementation batch
- When a backlog needs sequencing into implementable batches
- As input to a pipeline that processes issues in batch order

## Critical Constraints

**NEVER:**
- Modify any source code files
- Create or edit Python, YAML, or config files
- Guess recipe classification when confidence is low — escalate to user
- Apply GitHub labels when `--no-label` is passed
- Skip human escalation for ambiguous issues
- Add useless comments to the codebase — do not use the codebase as a notepad
- Create files outside `{{AUTOSKILLIT_TEMP}}/triage-issues/` directory
- Use `--body` shell substitution (`--body "$(...)`) for `gh issue edit` — always write to
  `{{AUTOSKILLIT_TEMP}}/triage-issues/edit_body_{timestamp}.md` and use `--body-file`
- Run subagents in the background (`run_in_background: true` is prohibited)

**ALWAYS:**
- Use `model: "sonnet"` when spawning all subagents via the Task tool
- Pause for human input on ambiguous classifications
- Write the triage report and manifest to `{{AUTOSKILLIT_TEMP}}/triage-issues/` (relative to the current working directory)
- Use `gh` CLI for all GitHub operations (not raw API calls)
- Include rationale for every recipe classification
Read the full skill on GitHub

Details

Skill name
triage-issues
Path
src/autoskillit/skills_extended/triage-issues/SKILL.md
License
MIT
Repo updated
8 November 2026

FAQ

What does the Triage Issues skill do?

Analyze open GitHub issues and produce a sequenced implementation plan — grouping issues into parallel batches, ordering those batches, and tagging each issue with its recipe route. Use when user says "triage issues", "prioritize issues", or "plan issue order".

How do I install the Triage Issues skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add TalonT-Org/AutoSkillit --skill triage-issues. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Triage Issues popular?

It lives in TalonT-Org/AutoSkillit, which has 5 GitHub stars and 1 forks.

Related skills

Analyze Prs

5

TalonT-Org/AutoSkillit

Analyze all open PRs targeting a base branch — determine merge order, identify file overlaps, and tag each PR as simple or needs_check for complexity. Use at the start of a PR consolidation workflow.

Git & Code Review

Arch Lens C4 Container

5

TalonT-Org/AutoSkillit

Create C4 Container architecture diagram showing static structure, building blocks, and technology choices. Anatomical lens answering "How is it built?

Software Development

Arch Lens Concurrency

5

TalonT-Org/AutoSkillit

Create Concurrency architecture diagram showing parallel execution patterns, thread pools, synchronization, and barriers. Physiological lens answering "How does parallelism work?

Software Development

Contributor Experience Review

1

priyank766/OpenSource-SKILL

Review of a first-time or early-stage contributor's pull request, where the technical bar stays fixed but the sequencing, batching, and supplied context change. Use when GitHub labels the author a first-time contributor, when the PR comes from a newcomer to this repo, when it arrives via Hacktoberfest, GSoC, Outreachy, or a good-first-issue, when the change is technically close but procedurally messy (missing DCO, wrong base branch, unsigned commits, failing lint), or when the PR must be declined and the decline needs to not cost the project a future contributor. Applies a raised severity floo

Git & Code ReviewIn 1 list

Run Experiment

5

TalonT-Org/AutoSkillit

Execute a designed experiment in a worktree and collect structured results. Supports --adjust retry mode.

Git & Code Review

Dependency Review

1

priyank766/OpenSource-SKILL

Supply-chain review of dependency and CI changes in an open-source pull request. Use when a PR adds or bumps a dependency, changes a lockfile, introduces a build or postinstall script, edits a GitHub Actions workflow, changes a container base image, or when a bot-generated dependency bump needs human judgement before merge. Covers install-time code execution, package-identity and typosquat checks, artifact provenance, transitive footprint, license class, and workflow privilege changes. Ecosystem-agnostic — npm, PyPI, Go, Cargo, RubyGems, Composer, containers. Do NOT use for routine patch bumps

Git & Code ReviewIn 1 list

Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.