Agent skill

Issue Triage

by yunshu0909 in yunshu0909/yunshu_skillshub

GitHub Issue 处理协作流程。当用户收到 issue 需要分析和回复时使用。通过"诊断 → 定性 → 决策 → 回复"四步法，从一个 issue 产出准确的根因分析和得体的用户回复，避免误判问题类型或回复不专业。

MITAuto-check passedDevelopment

Install Issue Triage

skills CLI

$ npx skills add yunshu0909/yunshu_skillshub --skill issue-triage -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install yunshu0909/yunshu_skillshub issue-triage --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/yunshu0909/yunshu_skillshub.git skills-src && mkdir -p .claude/skills && cp -r skills-src/coding/issue-triage .claude/skills/issue-triage && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "issue-triage" agent skill from https://github.com/yunshu0909/yunshu_skillshub/tree/master/coding/issue-triage into .claude/skills/issue-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-triage", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/yunshu0909/yunshu_skillshub/tree/master/coding/issue-triage

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add yunshu0909/yunshu_skillshub --skill issue-triage -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install yunshu0909/yunshu_skillshub issue-triage --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/yunshu0909/yunshu_skillshub.git skills-src && mkdir -p .agents/skills && cp -r skills-src/coding/issue-triage .agents/skills/issue-triage && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "issue-triage" agent skill from https://github.com/yunshu0909/yunshu_skillshub/tree/master/coding/issue-triage into .agents/skills/issue-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-triage", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add yunshu0909/yunshu_skillshub --skill issue-triage -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install yunshu0909/yunshu_skillshub issue-triage --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/yunshu0909/yunshu_skillshub.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/coding/issue-triage .cursor/skills/issue-triage && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "issue-triage" agent skill from https://github.com/yunshu0909/yunshu_skillshub/tree/master/coding/issue-triage into .cursor/skills/issue-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-triage", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/yunshu0909/yunshu_skillshub.git --path coding/issue-triage

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add yunshu0909/yunshu_skillshub --skill issue-triage -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install yunshu0909/yunshu_skillshub issue-triage --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/yunshu0909/yunshu_skillshub.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/coding/issue-triage .gemini/skills/issue-triage && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "issue-triage" agent skill from https://github.com/yunshu0909/yunshu_skillshub/tree/master/coding/issue-triage into .gemini/skills/issue-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-triage", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install yunshu0909/yunshu_skillshub issue-triage

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add yunshu0909/yunshu_skillshub --skill issue-triage -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/yunshu0909/yunshu_skillshub.git skills-src && mkdir -p .github/skills && cp -r skills-src/coding/issue-triage .github/skills/issue-triage && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "issue-triage" agent skill from https://github.com/yunshu0909/yunshu_skillshub/tree/master/coding/issue-triage into .github/skills/issue-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-triage", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add yunshu0909/yunshu_skillshub --skill issue-triage -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install yunshu0909/yunshu_skillshub issue-triage --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/yunshu0909/yunshu_skillshub.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/coding/issue-triage .opencode/skills/issue-triage && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "issue-triage" agent skill from https://github.com/yunshu0909/yunshu_skillshub/tree/master/coding/issue-triage into .opencode/skills/issue-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-triage", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: issue-triage
GitHub stars: 768
Used in: 1 other repo
Token cost: ~729 tokens
SKILL.md length: 255 words
Files: 1
Skills in repo: 25
Repo updated: Oct 6, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Works in 3 steps: 用户提供 issue 链接或仓库地址 → 通过 gh issue view 或 WebFetch 获取 issue 详情 → 提取关键信息：用户环境、复现步骤、期望行为、实际行为、用户的猜测
Tasks that involve Issue triage
SKILL.md covers 核心原则, 工作流程 and 过程中的沟通规范
Calls gh

What it does

Issue Triage is an agent skill from yunshu0909/yunshu_skillshub. GitHub Issue 处理协作流程。当用户收到 issue 需要分析和回复时使用。通过"诊断 → 定性 → 决策 → 回复"四步法，从一个 issue 产出准确的根因分析和得体的用户回复，避免误判问题类型或回复不专业。

Its SKILL.md is about 730 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Issue triage. It works with GitHub. The repository describes itself as: 云舒精选的 Claude Code Skills 集合，提升开发和产品管理效率. The licence is MIT.

When your agent uses it

Tasks that involve Issue triage

Example prompts

“诊断 → 定性 → 决策 → 回复”
“/issue-triage”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

用户提供 issue 链接或仓库地址
通过 gh issue view 或 WebFetch 获取 issue 详情
提取关键信息：用户环境、复现步骤、期望行为、实际行为、用户的猜测

What it can do on your machine

Read from SKILL.md and the folder at commit da0d31f. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Issue Triage loads about 729 tokens when it runs. Until then it costs about 31 tokens; SKILL.md has 255 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~31
When it runs · the whole SKILL.md, loaded when a task matches: ~729

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from yunshu0909/yunshu_skillshub at commit da0d31f, republished under its MIT licence (© yunshu0909). 255 words, ~729 tokens.

Download SKILL.mdSave it as .claude/skills/issue-triage/SKILL.md (or your agent's skills folder).

name: issue-triage
description: GitHub Issue 处理协作流程。当用户收到 issue 需要分析和回复时使用。通过"诊断 → 定性 → 决策 → 回复"四步法，从一个 issue 产出准确的根因分析和得体的用户回复，避免误判问题类型或回复不专业。
metadata.status: active
metadata.status_updated_at: 2026-10-06

用户收到了一个 GitHub Issue（bug 报告、疑问、feature request），需要 AI 协助分析问题、判断是否要做、起草回复。AI 全程主导推进，用户只在关键节点做判断。

核心原则

先诊断后开口 — 没看完代码不下结论，没找到根因不定性
对用户诚实 — 是 bug 就认，是架构限制就说清楚，不甩锅也不画饼
量化成本 — "成本高"不是结论，要说清楚高在哪：改几个文件、涉及哪些模块、有没有测试条件
给替代方案 — 不做不等于不管，要告诉用户现在怎么绕过

工作流程

第 1 步：获取 Issue 内容

目标： 拿到 issue 的完整信息。

方法：

用户提供 issue 链接或仓库地址
通过 gh issue view 或 WebFetch 获取 issue 详情
提取关键信息：用户环境、复现步骤、期望行为、实际行为、用户的猜测

输出： 向用户简要转述 issue 内容，确认理解无误。

禁止： 只看标题就开始分析。必须读完 issue 全文。

第 2 步：代码诊断

目标： 在代码中找到根因。

方法：

从 issue 描述中提取关键词（功能名、错误信息、页面名等）
在代码中定位相关链路：从前端入口 → IPC 调用 → 后端处理 → 底层实现
画出完整调用链，标注每个环节的文件和行号
确认根因：代码哪里出了问题，或者代码为什么不支持用户的场景

输出： 向用户展示：

完整调用链（文件 + 行号）
根因的一句话总结
必要时附关键代码片段

禁止：

没读代码就猜原因
只看一个文件就下结论（要追完整条链路）

第 3 步：定性

目标： 判断这个 issue 属于哪种类型。

类型	判断标准	应对策略
Bug	在产品设计范围内，行为不符合预期	排期修复
架构限制	用户场景超出产品的设计前提	解释现状，评估是否值得扩展
Feature Request	产品本身没问题，用户想要新能力	评估成本和优先级
使用问题	用户操作方式不对，但产品可以做得更友好	回复指引，考虑优化体验

关键判断： 区分"该做但做错了"（bug）和"没打算做"（架构限制/feature）。

输出： 向用户说明定性结论和理由，等用户确认后再往下走。

第 4 步：决策（做还是不做）

目标： 基于根因和定性，给出做/不做的建议。

评估四个维度

改动范围 — 改几行 / 改一个模块 / 新增一个模块
影响面 — 只动一个文件 / 要改多个文件的调用链 / 要重构
测试条件 — 有没有环境能复现和验证（没环境 = 高风险）
用户绕过成本 — 用户自己能不能用其他方式解决

决策矩阵

改动范围	有测试条件	用户可绕过	建议
小（几行）	有	—	直接修
中（一个模块）	有	—	排期做
大（新模块/重构）	有	否	评估后排期
大（新模块/重构）	没有	是	记下需求，暂不做
任意	没有	是	告知绕过方案，需求记下

输出： 向用户说明建议和理由。如果建议不做，要量化成本（改几个文件、涉及哪些模块、为什么没法测）。

等用户确认决策后，再进入回复环节。

第 5 步：起草回复

目标： 写一条专业、得体、有信息量的 issue 回复。

回复结构（三层）

解释场景定位 — 这个功能是为什么场景设计的，让用户理解"为什么当前不支持"
给出实际影响 — 对用户来说，没有这个功能影响大不大，有没有替代方案
说明后续计划 — 如果做，给方向；如果不做，诚实说明成本和原因

语气原则

感谢反馈 — 用户花时间提 issue 值得尊重
不甩锅 — 不说"你用错了"，说"这个场景我们还没覆盖到"
给具体建议 — 不只说"不行"，要告诉用户现在怎么办
量化成本 — 让用户理解不是不想做，是客观上成本高

回复模板

Hi @{用户名}，感谢反馈！

**1. 功能定位**
{这个功能是为什么场景设计的，为什么当前不支持用户的场景}

**2. 对你的实际影响**
{用户现在能不能绕过，怎么绕过，核心功能是否受影响}

**3. 关于{用户期望的能力}**
{成本说明 + 后续计划}

输出： 回复草稿，等用户确认后发布。

禁止：

不经用户确认就直接发布到 GitHub
用技术黑话回复非技术用户
只说结论不解释原因

第 6 步：发布

用户确认回复内容后：

通过 gh issue comment 发布评论
根据定性结果打标签（bug / enhancement / wontfix / question）
如果需要记录为需求，提醒用户是否要加到需求池

过程中的沟通规范

AI 主导的节奏

每一步完成后主动推进到下一步
关键结论让用户确认后再往下走（定性、决策、回复内容）
技术细节 AI 自己搞定，只向用户展示结论

必须等用户确认的节点

步骤	确认什么
第 1 步	"issue 内容我理解的对吗？"
第 3 步	"这个定性你认同吗？"
第 4 步	"这个决策你同意吗？"
第 5 步	"回复内容可以发吗？"

不需要问用户的

事项	直接做
代码怎么查	AI 自己追链路
根因怎么分析	AI 自己判断
成本怎么量化	AI 自己评估

Files

Just SKILL.md in coding/issue-triage of yunshu0909/yunshu_skillshub.

Open the folder on GitHubat commit da0d31f

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in yunshu0909/yunshu_skillshub, which our catalogue first saw on October 7, 2026.

aiskillstore/marketplaceskills/yunshu0909/issue-triage

Compare with similar skills

Issue Triage next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Issue Triage compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Issue Triage this skillyunshu0909/yunshu_skillshub	768	1 repos	~729	Automated safety check: Pass	MIT	4 days ago
Setup Matt Pocock Skillsbestofjs/bestofjs	3.1k	20 repos	~1.7k	Automated safety check: Pass	MIT	6 days ago
Windows App SDK Issue Triage Reportmicrosoft/WindowsAppSDK	4.7k	—	~3.4k	Automated safety check: Pass	Apache-2.0	yesterday
Exposed Bug Fix WorkflowJetBrains/Exposed	9.3k	—	~3.8k	Automated safety check: Pass	Apache-2.0	yesterday
Pre-Release PR Triagejamiepine/voicebox	57k	—	~3.1k	Automated safety check: Pass	MIT	4 days ago
WinAppSDK Triage Meeting Prepmicrosoft/WindowsAppSDK	4.7k	—	~2.8k	Automated safety check: Pass	Apache-2.0	yesterday

Similar skills

Setup Matt Pocock Skills
bestofjs/bestofjs
Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout.
3.1k GitHub starsUsed in 20 repos~1.7k tokens
DevelopmentAuto-check passed
Windows App SDK Issue Triage Report
microsoft/WindowsAppSDK
Official
Generates GitHub Feature Area Status reports for the Windows App SDK repository, scoring issues so teams can see what needs attention in each area.
4.7k GitHub stars~3.4k tokensUpdated yesterday
DevelopmentAuto-check passed
Exposed Bug Fix Workflow
JetBrains/Exposed
Official
Takes a GitHub or YouTrack issue for the Exposed project through reproduction, a failing test, a fix, validation and a pull request.
9.3k GitHub stars~3.8k tokensUpdated yesterday
DevelopmentAuto-check passed
Pre-Release PR Triage
jamiepine/voicebox
Sorts a backlog of open pull requests into must-merge, candidate, superseded and deferred, writes a triage doc and works the merge loop before a release.
57k GitHub stars~3.1k tokensUpdated 4 days ago
DevelopmentAuto-check passed
WinAppSDK Triage Meeting Prep
microsoft/WindowsAppSDK
Official
Prepares the triage meeting summary for WinAppSDK Needs-Triage issues, with research-backed area suggestions, draft replies and a diff since the last triage.
4.7k GitHub stars~2.8k tokensUpdated yesterday
DevelopmentAuto-check passed
A2ui Issue Triage
a2ui-project/a2ui
Automates the triage of GitHub issues in the A2UI repository.
17k GitHub stars~1.5k tokensUpdated yesterday
DevelopmentAuto-check passed

More from yunshu0909/yunshu_skillshub

All 25 skills in this repo

Dual Agent Collaboration
yunshu0909/yunshu_skillshub
让 Codex 与 Claude Code 通过本机 CLI 组成“主执行者 + 独立审查者”的对称协作闭环。用于用户要求两个模型一起完成、交叉校核、独立审查、修到 ACK，或任务涉及产品需求收敛、复杂方案、跨模块开发、迁移、安全、重要重构和高质量交付时；无论从 Codex 还是 Claude Code 启动，都由当前模型主持，并完整调用另一方完成需求挑战、方案门禁、实现冷审和最终验收。
768 GitHub stars~2.2k tokensUpdated 4 days ago
Auto-check passed
Image Assistant
yunshu0909/yunshu_skillshub
配图助手 - 把文章/模块内容转成统一风格、少字高可读的 16:9 信息图提示词；先定“需要几张图+每张讲什么”，再压缩文案与隐喻，最后输出可直接复制的生图提示词并迭代。
768 GitHub starsUsed in 1 repo~536 tokens
Auto-check passed
Page Solution Design
yunshu0909/yunshu_skillshub
和用户一起敲定一个前端页面的整页方案（三层法：先定这页给用户什么，再定含哪几样怎么排，最后才是长什么样），最后打成一个定稿包（含高保真全状态与交互流程图）交给开发。触发：用户对一个页面说「想重做 / 重新设计 / 整页不对 / 太满 / 说不清具体改哪」，或「我们讨论一下这页怎么设计」。覆盖三种情形：① 已有页面整页重做；②「替换」——新方案占用同一个入口（同一路由 /…
768 GitHub stars~2.7k tokensUpdated 4 days ago
Auto-check passed
Backend Logic Design
yunshu0909/yunshu_skillshub
和用户一起把一个功能「看不见的部分」敲定：数据存哪、谁写谁读、怎么加载、怎么保存、默认值和升级、核心执行规则、出问题时怎么办、旧东西怎么迁。每条规则带编号、案例和状态（已定 / 方案里有但你没拍板 / 待你定 / AI 定），用户只回答带案例的新选择题、过目没拍过板的规则；给用户看的是按「你会问的问题」分组的问答卡片（最绕的逻辑配可点的模拟器）；最后请另一家模型只读查边界，问题闭环后封成后端逻辑…
768 GitHub stars~2k tokensUpdated 4 days ago
Auto-check passed
Article Study
yunshu0909/yunshu_skillshub
带用户精读一篇文章/文档并真正学透（不是出摘要）。五步：抽干货 → 切讲次 → 每讲跑「学-考-讲」循环 → 对号入座 → 实操+测验+讲错题+蒸馏。每讲产出 HTML 课件 + 笔记落盘；讲完必考一次，用户复述后必须挑不精确处拧紧；抽象概念上可交互演示（能点能跑）；全程用用户自己的业务场景当案例；学完出多题型自动判分测验卷，最后把收获蒸馏回用户的工具。核心触发条件是用户要的是"学会"而不是"要…
768 GitHub stars~964 tokensUpdated 4 days ago
Auto-check passed
Issue Pool
yunshu0909/yunshu_skillshub
Issue 池全生命周期管理（开发范式 v1 规划段）。核心是一条 issue 驱动的流程：用户随手丢想法，你把糊的 issue 变成能开工的 task——产出的是“问题定义”，不是“解决方案实现”；载体就是仓库根的 ISSUES.md。五个动作：记、并、拆、转、pending。规划规模只区分 single-task（一个版本能交付）与 roadmap（需要多批滚动），不得使用…
768 GitHub stars~996 tokensUpdated 4 days ago
Auto-check passed

Works with

GitHub

Questions about Issue Triage

What does Issue Triage do?

GitHub Issue 处理协作流程。当用户收到 issue 需要分析和回复时使用。通过"诊断 → 定性 → 决策 → 回复"四步法，从一个 issue 产出准确的根因分析和得体的用户回复，避免误判问题类型或回复不专业。. Issue Triage is an agent skill from yunshu0909/yunshu_skillshub.

When should I use Issue Triage?

Issue Triage fits situations like: tasks that involve Issue triage.

How do I install Issue Triage in Claude Code?

Run `npx skills add yunshu0909/yunshu_skillshub --skill issue-triage -a claude-code`. Or copy the skill folder (coding/issue-triage in yunshu0909/yunshu_skillshub) into .claude/skills/issue-triage in your project. Claude Code loads it when a task matches its description.

How do I install Issue Triage in Codex?

Run `npx skills add yunshu0909/yunshu_skillshub --skill issue-triage -a codex`. Or copy the skill folder (coding/issue-triage in yunshu0909/yunshu_skillshub) into .agents/skills/issue-triage in your project. Codex loads it when a task matches its description.

Can I use Issue Triage in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add yunshu0909/yunshu_skillshub --skill issue-triage -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/issue-triage, .gemini/skills/issue-triage, .github/skills/issue-triage and .opencode/skills/issue-triage in your project.

What does Issue Triage need to run?

Going by SKILL.md and its folder, Issue Triage needs the command-line tools its instructions call (gh).

Does Issue Triage access the network?

SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Issue Triage safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Issue Triage use?

Issue Triage is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Issue Triage use?

About 729 tokens (SKILL.md is roughly 2.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Issue Triage?

Skills that share tags, products or a category with Issue Triage: Setup Matt Pocock Skills (bestofjs/bestofjs, 3.1k stars), Windows App SDK Issue Triage Report (microsoft/WindowsAppSDK, 4.7k stars), Exposed Bug Fix Workflow (JetBrains/Exposed, 9.3k stars) and Pre-Release PR Triage (jamiepine/voicebox, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Issue Triage?

yunshu0909 (a GitHub user) maintains it in yunshu0909/yunshu_skillshub, which has 768 GitHub stars. The repository holds 25 skills in this directory. The repository was last updated on October 6, 2026.

Source: yunshu0909/yunshu_skillshub on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Issue Triage

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

核心原则

工作流程

第 1 步：获取 Issue 内容

第 2 步：代码诊断

第 3 步：定性

第 4 步：决策（做还是不做）

评估四个维度

决策矩阵

第 5 步：起草回复

回复结构（三层）

语气原则

回复模板

第 6 步：发布

过程中的沟通规范

AI 主导的节奏

必须等用户确认的节点

不需要问用户的

Files

Used in 1 other repository

Compare with similar skills

Similar skills

More from yunshu0909/yunshu_skillshub

Related

Questions about Issue Triage