# Fix Issue

Carry a selected FastMCP bug from reproduction through a scoped fix, compatibility...

- 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 fix-issue -g -a claude-code -y`
Codex: `npx skills add PrefectHQ/fastmcp --skill fix-issue -g -a codex -y`
Cursor: `npx skills add PrefectHQ/fastmcp --skill fix-issue -g -a cursor -y`
Gemini CLI: `npx skills add PrefectHQ/fastmcp --skill fix-issue -g -a gemini-cli -y`

## Description

Carry a selected FastMCP bug from reproduction through a scoped fix, compatibility review, validation, and a monitored pull request.

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

# Fix a selected issue

Read AGENTS.md and the contribution policy in [the development guide](../../../docs/development/contributing.mdx). Read the issue's full discussion, relevant history, and associated PRs in all states. Evaluate existing contributions before writing a competing fix; use [review-issue](../review-issue/SKILL.md) when assignment is the next decision. Preserve contributor authorship when carrying existing work forward.

## Establish the contract

Trace the public request to the failing operation. Confirm supported behavior is broken, not merely surprising. State the scope and compatibility boundary before implementation: which inputs must change, which adjacent behavior must remain, and any migration needed. If the intended contract is unresolved, bring that precise question to the maintainer.

## Red, green, review

Use [python-tests](../python-tests/SKILL.md). Reproduce the failure on unchanged code, confirm it fails for the right reason, then make the smallest causal fix. Test explicit overrides and neighboring supported paths that share the changed branch. Avoid expanding the fix to unrelated standards gaps.

Self-review the full change with [review-pr](../review-pr/SKILL.md), including docs and dependency bounds. Separate necessary compatibility changes from accidental regressions and say whether a breaking change remains. Do not infer compatibility from passing tests.

Run the repository's required dependency sync, full tests, and static checks before committing. Honor branch and attribution conventions. If a required check fails, investigate and report evidence rather than hiding the failure.

## Publish and follow through

Within existing authorization, update the existing PR or open a focused one, using draft status when appropriate. Follow repository PR-body conventions and the user's `pr-body` skill when available. Describe the actual user-visible change and any migration, not the development diary.

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