Skill

Issue & PR Triage

From iyu

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".

Install

npx claudepluginhub iyulab/claude-plugins --plugin iyu

Tool Access

This skill uses the workspace's default tool permissions.

Preview

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.

SKILL.md

Similar Skills

using-git-worktrees

Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.

superpowers

169.2k

subagent-driven-development

3 files

Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.

superpowers

169.2k

dispatching-parallel-agents

Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.

superpowers

169.2k

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitMar 9, 2026

Actions

View Source View Plugin View on GitHub View README

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