How do I install the Issue Pr Triage skill?

Run npx skillmds@latest add tomevault-io/issue-pr-triage in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Issue Pr Triage safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Issue Pr Triage?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Issue Pr Triage free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Issue Pr Triage?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Issue Pr Triage by tomevault-io — Agent Skill

Name: Issue Pr Triage
Author: tomevault-io

Issue Pr Triage

Use when discussing whether to accept, reject, or redirect an external issue or PR. Triggers on "triage this issue", "evaluate this feature request", "should I accept/merge this", "is this in scope", "review this PR/contribution", "how should I respond to this issue".

tomevault-io Updated Sep 17, 2026

File contents

Issue & PR Triage Framework

Evaluate external Issues/PRs against project philosophy. The goal is not just to decide on the request — it's to discover latent work the request reveals.

Core Philosophy

"Every issue is an opportunity" — Even declines improve documentation or reveal API gaps.
"Think 10 from 1" — One request implies ten insights. What's missing? What should change?
"Every contribution is a gift" — Honor the contributor's time.
"Mentor, not gatekeeper" — Help them succeed.

Philosophy Alignment

Dimension	Question
Core Mission Fit	Serves project's core purpose?
Scope Alignment	Library vs application responsibility?
Pattern Consistency	Consistent with existing architecture?
User Base Impact	Benefits majority or niche?

Overall: High (4-5 avg) / Medium (3-3.9) / Low (1-2.9)

Issue Decision Matrix

                 | Philosophy HIGH | Philosophy LOW  |
-----------------|-----------------|-----------------|
Feasibility HIGH | ACCEPT          | REDIRECT        |
Feasibility MED  | ADAPT           | DEFER/REDIRECT  |
Feasibility LOW  | DEFER           | DECLINE         |

PR Decision Matrix

                 | Quality HIGH         | Quality LOW          |
-----------------|----------------------|----------------------|
Philosophy HIGH  | APPROVE              | MERGE_WITH_FIXES     |
Philosophy MED   | APPROVE_WITH_NOTES   | REQUEST_CHANGES      |
Philosophy LOW   | REDIRECT             | DECLINE              |

Verdicts

Issues: ACCEPT / ADAPT / DEFER / REDIRECT / DECLINE PRs: APPROVE / APPROVE_WITH_NOTES / MERGE_WITH_FIXES / REQUEST_CHANGES / REDIRECT / DECLINE

Severity (PR Review)

Bug Risk (Issue Triage)

Commands

/iyu:issue <url | file | "text">      # Full triage
/iyu:issue <input> --quick             # Decision only
/iyu:pr <pr-url | #number>            # Full review
/iyu:pr <input> --quick               # Blockers only

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: issue-pr-triagedescription: Use when discussing whether to accept, reject, or redirect an external issue or PR. Triggers on "triage this issue", "evaluate this feature request", "should I accept/merge this", "is this in scope", "review this PR/contribution", "how should I respond to this issue".---# Issue & PR Triage FrameworkEvaluate external Issues/PRs against project philosophy. The goal is not just to decide on the request — it's to **discover latent work** the request reveals.## Core Philosophy- **"Every issue is an opportunity"** — Even declines improve documentation or reveal API gaps.- **"Think 10 from 1"** — One request implies ten insights. What's missing? What should change?- **"Every contribution is a gift"** — Honor the contributor's time.- **"Mentor, not gatekeeper"** — Help them succeed.## Philosophy Alignment| Dimension | Question ||-----------|----------|| Core Mission Fit | Serves project's core purpose? || Scope Alignment | Library vs application responsibility? || Pattern Consistency | Consistent with existing architecture? || User Base Impact | Benefits majority or niche? |**Overall**: High (4-5 avg) / Medium (3-3.9) / Low (1-2.9)## Issue Decision Matrix``` | Philosophy HIGH | Philosophy LOW |-----------------|-----------------|-----------------|Feasibility HIGH | ACCEPT | REDIRECT |Feasibility MED | ADAPT | DEFER/REDIRECT |Feasibility LOW | DEFER | DECLINE |```## PR Decision Matrix``` | Quality HIGH | Quality LOW |-----------------|----------------------|----------------------|Philosophy HIGH | APPROVE | MERGE_WITH_FIXES |Philosophy MED | APPROVE_WITH_NOTES | REQUEST_CHANGES |Philosophy LOW | REDIRECT | DECLINE |```## Verdicts**Issues**: ACCEPT / ADAPT / DEFER / REDIRECT / DECLINE**PRs**: APPROVE / APPROVE_WITH_NOTES / MERGE_WITH_FIXES / REQUEST_CHANGES / REDIRECT / DECLINE## Severity (PR Review)| 🔴 Blocker | 🟠 Major | 🟡 Minor | ✨ Praise (required) |## Bug Risk (Issue Triage)| 🔴 Critical | 🟠 High | 🟡 Medium | 🟢 Low |## Commands```bash/iyu:issue <url | file | "text"> # Full triage/iyu:issue <input> --quick # Decision only/iyu:pr <pr-url | #number> # Full review/iyu:pr <input> --quick # Blockers only```---> Converted and distributed by [TomeVault](https://tomevault.io/claim/iyulab) — claim your Tome and manage your conversions.

Frequently asked questions