Skip to content

Commit ad334f9

Browse files
cliffhallclaude
andcommitted
feat(skills): issue-triage skill and board audit (factory Part 8)
Adds .claude/skills/issue-triage, adapted from the MCP Inspector's for one board (#43) and this repo's community inflow: - step 0 class check for issues (listings, new servers, archived servers, SDK/spec, duplicates, spam, security reports), each with a canned response - pass 1 onto the board as Incoming (no milestone), pass 2 left to a human - the priority rubric with its severity axis reworded for servers, and the posted score comment - outside PRs: snapshot, pre-classify, manifest reviewed by a maintainer, harvest into Incoming issues, paced close, verify (docs/contribution-model.md) - the board audit for #43, with the [GHSA- advisory draft carve-out and an issue --limit above the repo's total issue count, both truncation-checked - eval cases (6 positives, 2 negatives) Retires readme-pr-check.yml on v2/main and folds its behavior into the listing class. The canned PR comments now live only in the skill; contribution-model.md points at them. Skills index row added. Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]> Signed-off-by: cliffhall <[email protected]>
1 parent e75607a commit ad334f9

6 files changed

Lines changed: 677 additions & 148 deletions

File tree

‎.claude/skills/issue-create/SKILL.md‎

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -125,7 +125,9 @@ by impact and urgency, and say in one line why:
125125
| Medium | The default for planned work |
126126
| Low | Nice to have; nothing waits on it |
127127

128-
A scored rubric replaces this table when the `issue-triage` skill lands (#4868).
128+
This table is the short form of the scored rubric in `issue-triage`, which is
129+
how triage prioritizes inflow. When the choice here is not obvious, score it
130+
with that rubric instead.
129131

130132
## 4. Create it
131133

@@ -189,4 +191,4 @@ An issue opened through the GitHub UI, by an outside reporter or by a
189191
maintainer, arrives with **no `v2` label, no milestone and no card**. That is
190192
normal on arrival, not a defect to fix the moment it lands: it is not approved
191193
yet, so it enters the board in **Incoming**, unmilestoned, through triage (the
192-
`issue-triage` skill, #4868), never through this flow.
194+
`issue-triage` skill), never through this flow.

0 commit comments

Comments
 (0)