How do I install the API Patch Strategies skill?

Run npx skillmds@latest add deangrant/api-patch-strategies in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is API Patch Strategies safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with API Patch Strategies?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is API Patch Strategies free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published API Patch Strategies?

deangrant (@deangrant) published this skill. Their other Agent Skills are listed on their SkillMD profile.

API Patch Strategies by deangrant — Agent Skill

Name: API Patch Strategies
Author: deangrant

API Patch Strategies

Choose JSON Patch (RFC 6902) vs Merge Patch (RFC 7386) for REST PATCH, including media types, null semantics, Accept-Patch, and If-Match concurrency. Use when designing partial updates or reviewing PATCH handlers.

deangrant 5ce7466 4 files · 3.1 KB Updated Sep 17, 2026

File contents

PATCH Strategies: JSON Patch vs Merge Patch

Use this skill when implementing partial updates. Arbitrary partial JSON is ambiguous — use RFC media types; wrong Content-Type → 415.

Advertise supported formats with Accept-Patch (often on OPTIONS).

1. JSON Patch (RFC 6902)

Content-Type: application/json-patch+json — ordered ops; JSON Pointer paths; all-or-nothing.

Ops: add, remove, replace, move, copy, test.

Best for: array element edits, assertions (test), auditability, explicit null.

2. Merge Patch (RFC 7386)

Content-Type: application/merge-patch+json — partial object; null deletes; omit = unchanged; nested objects merge; arrays replace wholesale.

Best for: object-centric local-copy edits from clients.

3. Concurrency and security

Require If-Match (strong ETag) → 412 on mismatch; missing may be 428.
Whitelist patchable paths; cap body size / op count; authz per path.
Never treat PATCH like PUT (omitted fields nulled) unless Merge Patch null rules apply.

4. Quick checklist

One format (or both with distinct media types + 415).
Accept-Patch documented.
Null/omit semantics documented.
If-Match on contested resources.
Path allowlist + size/op caps.
Errors: 400 / 409 / 412 / 415 / 422.

See reference.md and examples.md.

Frequently asked questions