# Review PR

Assess a FastMCP pull request for justified behavior, compatibility, and correctness...

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

## Description

Assess a FastMCP pull request for justified behavior, compatibility, and correctness, then follow CI and review feedback to a revision-specific verdict. Use for draft or ready PRs and self-review before publication.

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

# Review a FastMCP PR

Review whether the change should ship, with evidence for its intended behavior as well as its implementation. Use the same procedure for maintainer, contributor, and agent drafts. For an unpublished change, record the base and local diff and skip GitHub-only steps. For an external contributor's assignment decision, start with [review-issue](../review-issue/SKILL.md).

For review-only tasks, assess and report; repair, push, and monitoring steps apply only when that follow-through is in scope. Automated reviewers use the same substantive checks and their required findings format. Do not wait for your own bot review or manage the PR lifecycle. If the review environment cannot run tests or delegate an adversarial pass, state that limit rather than claiming those checks passed.

## Procedure

1. **Establish the scope.** Read AGENTS.md, the contribution policy in [the development guide](../../../docs/development/contributing.mdx), the issue's full discussion, the entire diff against the merge base, and prior review threads and replies. Record the base and head revisions. Find related issues and PRs in all states, and inspect open PRs touching the same files for overlapping lines or behavior even when they do not link the issue. Distinguish released behavior, fixes already on main, and competing proposals. When proposals compete, record the issue reporter, original implementation author, maintainer direction, correctness, and distinct coverage. Recommend which proposal should survive and preserve carried-forward credit; submission order and green CI do not select the winner. Call a sound overlapping proposal redundant rather than spurious.

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