How do I install the Pr Issue Triage skill?

Run npx skillmds@latest add mkurman/pr-issue-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 Pr Issue Triage safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Pr Issue 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 Pr Issue Triage free to use?

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

Who published Pr Issue Triage?

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

Pr Issue Triage by mkurman — Agent Skill

Name: Pr Issue Triage
Author: mkurman

File contents

PR / Issue Triage

User story

I want one triage view across repo review items and issue tracker work, so I can see stale, blocked, and actionable items without manually stitching together GitHub/GitLab and Linear/Jira.

Pack contract

Prerequisites and readiness

Requires one repo connector: github or gitlab
Optionally enriches with one tracker connector: linear or jira
If the tracker is unavailable, the pack still runs as repo-only triage and clearly marks tracker enrichment as degraded.

Inputs and configuration fields

repo_connector: github or gitlab
tracker_connector: linear, jira, or none
owner / repo or equivalent project coordinates
include_writeback_suggestions: boolean
stale_days: integer threshold

Outputs and delivery targets

merged queue showing:
- open PRs / review items
- open issues / work items
- stale items
- blocked items
- suggested next actions
source links should point back to the original PR/issue/tracker item
write-back suggestions must be clearly marked approval-required

Manual run recipe

List repo review items and work items from the chosen repo connector.
If tracker is ready, fetch tracker work items and merge by title/ID/reference where possible.
Summarize stale and blocked items.
Suggest write-backs separately from the read-only report.

Example routine wiring

Schedule as a weekday triage routine or on-demand review block. Example payload description:

Run the canonical PR/Issue Triage pack for the main repo, merge repo/tracker context, and surface approval-gated write-back suggestions.

Example prompt

Run PR/Issue Triage for owner/repo using GitHub plus Linear. Show stale PRs, blocked issues, and suggested labels/comments, but do not perform write-backs without approval.

Failure and recovery behavior

Missing repo connector -> fail closed with setup hint.
Missing tracker connector -> continue with repo-only triage.
Proposed write-back with no approval -> keep suggestion in the report, do not execute it.

Verification checklist

Manual repo-only proof passes.
Manual repo + tracker proof passes.
Missing tracker degrades gracefully.
Write-back suggestions are clearly approval-gated.
Source links are present for triaged items.

---name: pr-issue-triagedescription: Canonical PR/Issue triage pack combining repo review queues with work tracker context and approval-gated write-backs.---# PR / Issue Triage## User storyI want one triage view across repo review items and issue tracker work, so I can see stale, blocked, and actionable items without manually stitching together GitHub/GitLab and Linear/Jira.## Pack contract### Prerequisites and readiness- Requires one repo connector: `github` or `gitlab`- Optionally enriches with one tracker connector: `linear` or `jira`- If the tracker is unavailable, the pack still runs as repo-only triage and clearly marks tracker enrichment as degraded.### Inputs and configuration fields- `repo_connector`: `github` or `gitlab`- `tracker_connector`: `linear`, `jira`, or `none`- `owner` / `repo` or equivalent project coordinates- `include_writeback_suggestions`: boolean- `stale_days`: integer threshold### Outputs and delivery targets- merged queue showing: - open PRs / review items - open issues / work items - stale items - blocked items - suggested next actions- source links should point back to the original PR/issue/tracker item- write-back suggestions must be clearly marked `approval-required`## Manual run recipe1. List repo review items and work items from the chosen repo connector.2. If tracker is ready, fetch tracker work items and merge by title/ID/reference where possible.3. Summarize stale and blocked items.4. Suggest write-backs separately from the read-only report.## Example routine wiringSchedule as a weekday triage routine or on-demand review block. Example payload description:`Run the canonical PR/Issue Triage pack for the main repo, merge repo/tracker context, and surface approval-gated write-back suggestions.`## Example prompt`Run PR/Issue Triage for owner/repo using GitHub plus Linear. Show stale PRs, blocked issues, and suggested labels/comments, but do not perform write-backs without approval.`## Failure and recovery behavior- Missing repo connector -> fail closed with setup hint.- Missing tracker connector -> continue with repo-only triage.- Proposed write-back with no approval -> keep suggestion in the report, do not execute it.## Verification checklist- [ ] Manual repo-only proof passes.- [ ] Manual repo + tracker proof passes.- [ ] Missing tracker degrades gracefully.- [ ] Write-back suggestions are clearly approval-gated.- [ ] Source links are present for triaged items.

Frequently asked questions

Pr Issue Triage