Complete Partial PR

Use this when a PR or issue patch fixes a small visible failure but may not address the full integration contract. The goal is to turn a narrow contribution into a maintainable Pydantic AI change, or to explain precisely why it should stay narrow.

This is not limited to UI or provider integrations. Apply it to any patch that touches one variant of a broader surface: parse/dump, request/response, streaming/non-streaming, static/dynamic, sync/async, native/provider/local tools, metadata, state machines, durable execution, docs, or tests.

When To Use

• A contributor's PR addresses the immediate error but not the rest of the user's workflow.
• A fix accepts one shape of data but may not preserve roundtrip semantics.
• A provider or external protocol has more states, fields, or variants than the PR covers.
• The user asks "is this enough?", "what did the contributor miss?", "verify this against the spec", or "improve this branch".
• A reviewer suspects the patch contradicts historical decisions or creates future integration debt.

Do not use this as a replacement for /review-branch when the task is only a general code review. If the PR has no local context yet, run /adopt-pr first.

Operating Principle

Separate three things before implementing: