# Triage

Find worthwhile FastMCP issues to work on in a backlog or release window, verify...

- Repository: https://github.com/PrefectHQ/fastmcp (28267 stars)
- Category: Git and review
- License: Apache-2.0
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add PrefectHQ/fastmcp --skill triage -g -a claude-code -y`
Codex: `npx skills add PrefectHQ/fastmcp --skill triage -g -a codex -y`
Cursor: `npx skills add PrefectHQ/fastmcp --skill triage -g -a cursor -y`
Gemini CLI: `npx skills add PrefectHQ/fastmcp --skill triage -g -a gemini-cli -y`

## Description

Find worthwhile FastMCP issues to work on in a backlog or release window, verify promising candidates, and present concrete picks with existing PR links.

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

# Find worthwhile work

Read AGENTS.md and the contribution policy in [the development guide](../../../docs/development/contributing.mdx). Honor the requested scope. For "since the last patch," identify the release timestamp, then look for open issues created or substantively updated afterward. Use a bounded inventory internally; report truncation if it affects coverage.

Start from an inventory, then link each candidate to the PRs that mention it:

```bash
gh release list --repo PrefectHQ/fastmcp --limit 1
gh issue list --repo PrefectHQ/fastmcp --state open --limit 30 \
  --json number,title,author,createdAt,updatedAt,labels,comments
gh pr list --repo PrefectHQ/fastmcp --state all --search "<issue-number> in:body" \
  --json number,title,state,author
```

Where `search`, GraphQL or `--paginate` are blocked (cloud sessions), page repo-scoped REST by hand (`gh api "repos/PrefectHQ/fastmcp/pulls?state=all&per_page=100&page=N"`), dump it once, and join locally.

Pick work with concrete user impact, a supported contract being violated, a tractable causal fix, and a change FastMCP wants to carry. Apply [triage and merge decisions](../../../docs/development/contributing.mdx#triage-and-merge-decisions) before ranking anything: labels and confident diagnoses are claims, and the behavior may already be fixed or decided. Mark each pick want / marginal / don't want. Do not rank solely by recency, comment count, or how small a proposed patch looks. Automated dashboard churn is not itself useful work.

For promising candidates:

The rest: https://github.com/PrefectHQ/fastmcp/blob/HEAD/.agents/skills/triage/SKILL.md