# Issue Create

Create a tracked issue in this repo end to end, version label, type label, milestone...

- Repository: https://github.com/modelcontextprotocol/inspector (11208 stars)
- Category: Engineering
- License: see repository
- Last updated: 2026-10-29
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add modelcontextprotocol/inspector --skill issue-create -g -a claude-code -y`
Codex: `npx skills add modelcontextprotocol/inspector --skill issue-create -g -a codex -y`
Cursor: `npx skills add modelcontextprotocol/inspector --skill issue-create -g -a cursor -y`
Gemini CLI: `npx skills add modelcontextprotocol/inspector --skill issue-create -g -a gemini-cli -y`

## Description

Create a tracked issue in this repo end to end, version label, type label, milestone, board card, Status and Priority. Use when asked to file, create, open or raise an issue; when picking its labels or its milestone; when checking whether one already exists; or when work discovered mid-task needs an issue of its own.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Creating an issue

An issue **you** create is not "created" until every step below that applies to
its version is done. A label is a repo tag, the milestone is a release bucket,
and the board is a separate org project, `--label v2` does **not** add a board
card, and adding a card does **not** set a Status or a Priority.

| # | Step | v2 | v1 |
| --- | --- | --- | --- |
| 1 | **Version label**, exactly one of `v1` / `v2` | ✅ | ✅ |
| 2 | **Type label**, exactly one of `bug` / `enhancement` / `documentation` / `chore` / `question` | ✅ | ✅ |
| 3 | **Milestone** | ✅ | ❌, every milestone is a v2 release bucket, so there is none to take |
| 4 | **A card on the board for that version**, `v2` → #28, `v1` → #11 | ✅ | ✅ |
| 5 | **Status** on that card | ✅ | ✅ |
| 6 | **Priority** on that card | ✅ | ❌, board #11 has no such field |

The two ❌ rows are not oversights to fix later: the field does not exist for
that line, and `AGENTS.md` states both exceptions (Copilot).

Set the labels and milestone at **create time**, never by backfilling: an
unlabeled issue belongs to no version line and appears in no version-filtered
query, and an unmilestoned one drops out of release planning silently.

**Never create a duplicate.** Check the board for a matching item first.
**Never create a draft card** (a board card with no issue number), every board
item is a real GitHub issue. The single exception is a **GitHub security
advisory**, which is private until it is published and so cannot be tracked by
an issue at all; see `/security-advisory`. Nothing you reach through *this*
flow is that case.

## 0. Check the board first

Search **all** states, not just open. A closed issue is still a duplicate, it
may have been completed, rejected, or filed and superseded, and refiling it
loses that history. When one matches, the call is whether to reopen it or file
genuinely new work; either way you need to have seen it (Copilot).

The rest: https://github.com/modelcontextprotocol/inspector/blob/HEAD/.claude/skills/issue-create/SKILL.md