How do I install the Sks Pr Triage skill?

Run npx skillmds@latest add shikanime-labs/sks-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.

What does the Sks Pr Triage skill do?

Use when triaging an existing shikanime org PR: labels, assignee, milestone, and reviewers. It is listed under Coding & Dev Tools on SkillMD.

Is Sks Pr 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 Sks 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 Sks Pr Triage free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published Sks Pr Triage?

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

Sks Pr Triage by shikanime-labs — Agent Skill

Name: Sks Pr Triage
Author: shikanime-labs

File contents

Shikanime PR Triage

Triage a PR in shikanime-labs/*/shikanime-studio/*: fill every metadata field empty on the PR and derivable from its own content. English; never invent a missing repo value; triage never closes PRs.

When to Use

"Triage an existing shikanime org PR."
"Assign metadata (labels, assignee, milestone, project, reviewers)."
"Link issue ↔ PR."
A bug-labelled PR's fix cites no root cause → flag for sks-investigate before approving.

Prereqs: gh authed vs the canonical org repo; target it directly.

Inputs: N PR number; R=OWNER/REPO, default cwd origin, must be under shikanime-labs/ or shikanime-studio/ else ask.

1. Fetch

gh pr view "$N" --repo "$R" --json number,title,body,labels,assignees,milestone,reviewRequests

2. Metadata source of truth

gh label list --repo "$R" --limit 200 --json name,description
gh api repos/"$R"/milestones?state=open --jq '.[] | "\(.number)\t\(.title)"'
gh project list --owner "${R%/*}"
gh api repos/"$R"/assignees --jq '.[].login'

3. Decide (apply only if empty + value exists in repo)

labels: match title/body meaning to step-2 list (defect→bug, capability→enhancement, docs→documentation); add area label from touched paths only if it exists. Never invent; drop anything absent from the list.
assignee: if none, ASSIGNEE=$(gh api user --jq .login).
milestone: bug→highest open patch on current minor (max Z); enhancement→next minor/major.
project: if repo boards and PR unboarded, --add-project <number>; skip if ambiguous.
reviewers: if no review requests, add one collaborator/team member; skip if none obvious.

4. Apply (additive only: `--add-label`/`--add-assignee`, never `--label`)

gh pr edit "$N" --repo "$R" --add-label "bug" --add-label "area/..."
gh pr edit "$N" --repo "$R" --add-assignee "$ASSIGNEE"
gh pr edit "$N" --repo "$R" --milestone <num>
gh pr edit "$N" --repo "$R" --add-reviewer <login>

5. Link issue ↔ PR

If title/body cites #M (open, unlinked issue), ensure body has Related: #M (prepend if absent).

6. Verify

gh pr view "$N" --repo "$R" --json number,title,labels,assignees,milestone,reviewRequests

Verification

gh pr view "$N" --repo "$R" --json number,title,labels,assignees,milestone,reviewRequests
# title/body cites an open issue via Related: #M if applicable

---name: sks-pr-triagedescription: Use when triaging an existing shikanime org PR: labels, assignee, milestone, and reviewers.license: Apache-2.0---# Shikanime PR TriageTriage a PR in `shikanime-labs/*`/`shikanime-studio/*`: fill every metadatafield **empty on the PR** and **derivable from its own content**. English; neverinvent a missing repo value; triage never closes PRs.## When to Use- "Triage an existing shikanime org PR."- "Assign metadata (labels, assignee, milestone, project, reviewers)."- "Link issue ↔ PR."- A bug-labelled PR's fix cites no root cause → flag for `sks-investigate` before approving.Prereqs: `gh` authed vs the canonical org repo; target it directly.Inputs: `N` PR number; `R`=`OWNER/REPO`, default cwd `origin`, must be under`shikanime-labs/` or `shikanime-studio/` else ask.## 1. Fetch```bashgh pr view "$N" --repo "$R" --json number,title,body,labels,assignees,milestone,reviewRequests```### 2. Metadata source of truth```bashgh label list --repo "$R" --limit 200 --json name,descriptiongh api repos/"$R"/milestones?state=open --jq '.[] | "\(.number)\t\(.title)"'gh project list --owner "${R%/*}"gh api repos/"$R"/assignees --jq '.[].login'```### 3. Decide (apply only if empty + value exists in repo)- **labels**: match title/body meaning to step-2 list (defect→`bug`, capability→`enhancement`, docs→`documentation`); add area label from touched paths only if it exists. Never invent; drop anything absent from the list.- **assignee**: if none, `ASSIGNEE=$(gh api user --jq .login)`.- **milestone**: bug→highest open **patch** on current minor (max `Z`); enhancement→next minor/major.- **project**: if repo boards and PR unboarded, `--add-project <number>`; skip if ambiguous.- **reviewers**: if no review requests, add one collaborator/team member; skip if none obvious.### 4. Apply (additive only: `--add-label`/`--add-assignee`, never `--label`)```bashgh pr edit "$N" --repo "$R" --add-label "bug" --add-label "area/..."gh pr edit "$N" --repo "$R" --add-assignee "$ASSIGNEE"gh pr edit "$N" --repo "$R" --milestone <num>gh pr edit "$N" --repo "$R" --add-reviewer <login>```### 5. Link issue ↔ PRIf title/body cites `#M` (open, unlinked issue), ensure body has `Related: #M`(prepend if absent).### 6. Verify```bashgh pr view "$N" --repo "$R" --json number,title,labels,assignees,milestone,reviewRequests```## Verification```bashgh pr view "$N" --repo "$R" --json number,title,labels,assignees,milestone,reviewRequests# title/body cites an open issue via Related: #M if applicable```## See also- `sks-investigate` — root-cause research before any fix.

Frequently asked questions

Sks Pr Triage