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.
Validates all open GitHub issues, closes invalid ones with documentation, flags complex ones for planning discussion, then fixes and promotes remaining issues.
Install Triage
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill triage -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace triage --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/productivity/claude-workflow-skills/skills/triage .claude/skills/triage && rm -rf skills-srcUse ~/.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/
Install the "triage" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/productivity/claude-workflow-skills/skills/triage into .claude/skills/triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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 install https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/productivity/claude-workflow-skills/skills/triageType 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.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill triage -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace triage --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/productivity/claude-workflow-skills/skills/triage .agents/skills/triage && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "triage" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/productivity/claude-workflow-skills/skills/triage into .agents/skills/triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill triage -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace triage --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/productivity/claude-workflow-skills/skills/triage .cursor/skills/triage && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "triage" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/productivity/claude-workflow-skills/skills/triage into .cursor/skills/triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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 https://github.com/jeremylongshore/tons-of-skills-marketplace.git --path plugins/productivity/claude-workflow-skills/skills/triage--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill triage -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace triage --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/productivity/claude-workflow-skills/skills/triage .gemini/skills/triage && rm -rf skills-srcUse ~/.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/
Install the "triage" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/productivity/claude-workflow-skills/skills/triage into .gemini/skills/triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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.
$ gh skill install jeremylongshore/tons-of-skills-marketplace triageInstalls 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).
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill triage -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/productivity/claude-workflow-skills/skills/triage .github/skills/triage && rm -rf skills-srcUse ~/.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/
Install the "triage" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/productivity/claude-workflow-skills/skills/triage into .github/skills/triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill triage -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace triage --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/productivity/claude-workflow-skills/skills/triage .opencode/skills/triage && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "triage" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/productivity/claude-workflow-skills/skills/triage into .opencode/skills/triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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
triage- GitHub stars
- 2.8k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 438 words
- Files
- 1
- Skills in repo
- 3,342
- Repo updated
- First seen
- Licence
- MIT
At a glance
Validates all open GitHub issues, closes invalid ones with documentation, flags complex ones for planning discussion, then fixes and promotes remaining issues.
- Works in 7 steps: Pre-flight check → Fetch all open issues → Classify each issue → …
- The user says triage issues
- SKILL.md covers Step 0: Pre-flight check, Step 1: Fetch all open issues, Step 2: Classify each issue and Step 3: Close invalid issues, plus 3 more sections
- Calls gh, git and bash
What it does
Triage is an agent skill from jeremylongshore/tons-of-skills-marketplace. Validates all open GitHub issues, closes invalid ones with documentation, flags complex ones for planning discussion, then fixes and promotes remaining issues. Use when the user says triage issues, validate issues, fix issues, or work through the backlog.
Its SKILL.md is about 1.1k 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 and Git. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.
When your agent uses it
- The user says triage issues
- Validate issues
- Work through the backlog
Example prompts
- “Use the triage skill to validate all open GitHub issues, closes invalid ones with documentation, flags complex ones for planning discussion, then…”
- “/triage”
Requirements
- Pre-approved tools (allowed-tools): Read, Glob, Grep, Bash, Edit, Write
Workflow steps
7 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadGlobGrepBashEditWrite
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
ghgitbash
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh and git, 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
Triage loads about 1.1k tokens when it runs. Until then it costs about 66 tokens; SKILL.md has 438 words of instructions outside code blocks.
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: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
allowed-tools: Read, Glob, Grep, Bash, Edit, Write
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 jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 438 words, ~1,142 tokens.
Download SKILL.mdSave it as
.claude/skills/triage/SKILL.md (or your agent's skills folder).- name
- triage
- description
- Validates all open GitHub issues, closes invalid ones with documentation, flags complex ones for planning discussion, then fixes and promotes remaining issues. Use when the user says triage issues, validate issues, fix issues, or work through the backlog.
- allowed-tools
- Read, Glob, Grep, Bash, Edit, Write
- disable-model-invocation
- true
Triage
Project: !basename $(git rev-parse --show-toplevel 2>/dev/null) 2>/dev/null || basename $PWD
Branch: !git branch --show-current 2>/dev/null || echo "unknown"
Open issues: !gh issue list --state open --json number,title --jq '.[] | "#\(.number) \(.title)"' 2>/dev/null || echo "none"
Last tag: !git describe --tags --abbrev=0 2>/dev/null || echo "none"
Recent commits: !git log --oneline -5 2>/dev/null || echo "none"
Validates every open GitHub issue, closes those that are invalid, surfaces complex ones for planning discussion, then fixes and promotes all remaining actionable issues.
Step 0: Pre-flight check
gh auth status 2>&1 || { echo "ERROR: gh is not authenticated. Run: gh auth login"; exit 1; }Step 1: Fetch all open issues
gh issue list --state open --limit 100 --json number,title,body,labels,createdAt \
--jq '.[] | {number, title, labels: [.labels[].name], createdAt, body}'Read the full body of any issues where context is needed:
gh issue view <number> --json number,title,body,labels,commentsAlso read the project files to understand current state before assessing anything:
README.md— stated purpose and feature setCLAUDE.md— current status, known decisions, next steps
Step 2: Classify each issue
For every open issue, classify it as one of:
- Invalid — already fixed, a duplicate, not reproducible, out of scope, or based on a misunderstanding. Evidence must be clear.
- Complex — valid but requires significant design decisions, breaking changes, or multi-step implementation that warrants planning discussion before proceeding.
- Actionable — valid, well-scoped, and fixable now without further input.
Build a classification table before taking any action:
| # | Title | Classification | Reason |
|---|---|---|---|
| N | ... | Invalid/Complex/Actionable | ... |
Step 3: Close invalid issues
For each invalid issue, post a closing comment that explains why it is being closed, then close it:
gh issue comment <number> --body "$(cat <<'EOF'
Closing as invalid: <specific reason — already fixed in <commit/PR>, duplicate of #N,
not reproducible because <evidence>, or out of scope because <reason>>.
<If already fixed: reference the commit or PR that resolved it.>
<If duplicate: reference the canonical issue.>
EOF
)"
gh issue close <number> --reason "not planned"Use --reason "completed" if the issue was already resolved in code.
Step 4: Surface complex issues for planning
Stop and present complex issues to the user before proceeding. Format clearly:
Complex issues — planning needed before proceeding:
For each complex issue:
- #N:
<title>- Why it's complex: <design decision, breaking change, or scope concern>
- Options to consider:
<brief list of approaches> - Suggested next step: defer to backlog / spike / discuss now
Wait for the user's direction on each complex issue before moving to Step 5. If running non-interactively (no terminal), stop here and output the complex issues report.
if [ ! -t 0 ]; then
echo "Non-interactive mode: stopping after complex issue report. Review and re-run interactively."
exit 0
fiShow full SKILL.md (144 more words)Show less
Step 5: Fix actionable issues
Work through each actionable issue. For each one:
Read the relevant source files before making any changes.
Implement the fix — prefer the minimal correct change; don't refactor beyond the scope of the issue.
Verify the fix with any available linting or syntax checks:
bash bash -n <script.sh> # syntax check for shell scripts markdownlint '**/*.md' # markdown lintingStage the change:
bash git add -u
Record each fix with its issue number so the commit and PR can reference them.
Step 6: Promote
Once all actionable issues are fixed, run:
/promoteThe promote skill will commit, push, create and merge a PR (referencing fixed issue numbers
via Closes #N in the commit message), tag a release, and clean up.
When composing the commit message for the promote step, include Closes #N for every
issue fixed in Step 5.
© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in plugins/productivity/claude-workflow-skills/skills/triage of jeremylongshore/tons-of-skills-marketplace.
Open the folder on GitHubat commit cfae287
Compare with similar skills
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Triage this skilljeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.1k | Automated safety check: Notes | MIT | |
| Pre-Release PR Triagejamiepine/voicebox | 57k | — | ~3.1k | Automated safety check: Pass | MIT | |
| TiXL Ticket Processortixl3d/tixl | 5.1k | — | ~2.6k | Automated safety check: Pass | MIT | |
| RTK Issue Triagertk-ai/rtk | 83k | — | ~3k | Automated safety check: Notes | Apache-2.0 | |
| PR Triagertk-ai/rtk | 83k | — | ~2.5k | Automated safety check: Notes | Apache-2.0 | |
| Read-Only GitHub Triagecode-yeongyu/oh-my-openagent | 70k | — | ~4.3k | Automated safety check: Pass | Custom licence |
Similar skills
TiXL Ticket Processor
tixl3d/tixl
Works through the In progress column of the TiXL road-map board unattended, turning simple tickets into git stashes and writing plans for the rest under .agentic/Plans.
RTK Issue Triage
rtk-ai/rtk
Audits open GitHub issues, categorizes them, flags duplicates and linked PRs in three phases, with optional deep analysis and comments posted only after validation.
PR Triage
rtk-ai/rtk
Audits a repository's open pull requests, deep-reviews chosen ones and drafts review comments that are only posted after you approve them.
Read-Only GitHub Triage
code-yeongyu/oh-my-openagent
Fans out one background subagent per open GitHub issue or pull request to write an evidence-backed report, never commenting, closing or merging anything.
Setup Matt Pocock Skills
vinvcn/mattpocock-skills-zh-CN
为此仓库配置 engineering skills：设置其 issue tracker、triage labels 词汇与 domain docs 布局。在首次使用其他 engineering skills 前运行一次。
More from jeremylongshore/tons-of-skills-marketplace
All 3,342 skills in this repoPerforming Security Code Review
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.
Adapting Transfer Learning Models
jeremylongshore/tons-of-skills-marketplace
Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.
Agent Context Loader
jeremylongshore/tons-of-skills-marketplace
Execute proactive auto-loading: automatically detects and loads agents.md files.
Aggregating Performance Metrics
jeremylongshore/tons-of-skills-marketplace
Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.
Analyzing Capacity Planning
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.
Analyzing Database Indexes
jeremylongshore/tons-of-skills-marketplace
Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.
Related
Categories
Questions about Triage
What does Triage do?
Validates all open GitHub issues, closes invalid ones with documentation, flags complex ones for planning discussion, then fixes and promotes remaining issues. Triage is an agent skill from jeremylongshore/tons-of-skills-marketplace. Validates all open GitHub issues, closes invalid ones with documentation, flags complex ones for planning discussion, then fixes and promotes remaining issues.
When should I use Triage?
Triage fits situations like: the user says triage issues; validate issues; work through the backlog.
How do I install Triage in Claude Code?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill triage -a claude-code`. Or copy the skill folder (plugins/productivity/claude-workflow-skills/skills/triage in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/triage in your project. Claude Code loads it when a task matches its description.
How do I install Triage in Codex?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill triage -a codex`. Or copy the skill folder (plugins/productivity/claude-workflow-skills/skills/triage in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/triage in your project. Codex loads it when a task matches its description.
Can I use 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 jeremylongshore/tons-of-skills-marketplace --skill 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/triage, .gemini/skills/triage, .github/skills/triage and .opencode/skills/triage in your project.
What does Triage need to run?
Going by SKILL.md and its folder, Triage needs the command-line tools its instructions call (gh, git and bash). Its frontmatter pre-approves these tools: Read, Glob, Grep, Bash, Edit, Write.
Does Triage access the network?
SKILL.md contains no URLs. Its commands use gh and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Triage safe to install?
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Triage use?
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 Triage use?
About 1.1k tokens (SKILL.md is roughly 4.6k 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 Triage?
Skills that share tags, products or a category with Triage: Pre-Release PR Triage (jamiepine/voicebox, 57k stars), TiXL Ticket Processor (tixl3d/tixl, 5.1k stars), RTK Issue Triage (rtk-ai/rtk, 83k stars) and PR Triage (rtk-ai/rtk, 83k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Triage?
jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.
Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.