patch

Create, commit, and remove pnpm dependency patches via the pnpm CLI.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/theslashdojo/dojo --skill patch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: patch
Source: https://github.com/theslashdojo/dojo/tree/main/nodes/pnpm/patch
Command: npx skills add https://github.com/theslashdojo/dojo --skill patch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Create, commit, and remove pnpm dependency patches. Use when a registry package must be fixed locally without waiting for upstream, especially for broken transitive dependencies or urgent unblockers.

Core Features & Use Cases

  • Patch a direct or transitive dependency locally
  • Commit a patch file into the repository for repeatable installs
  • Remove obsolete patches after an upstream release lands

Quick Start

Patch a specific dependency using an exact version, edit the extracted directory if needed, then commit or remove the patch to repeat the fix.

Frequently Asked Questions about patch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I patch a broken transitive dependency in pnpm without forking the upstream repository?

To patch a broken transitive dependency in pnpm, extract the exact dependency version, edit the package locally, and commit the generated patch file into your repository to ensure repeatable installs without forking upstream.

What is the best way to fix a direct pnpm dependency locally for an urgent build unblocker?

The best way to fix a direct pnpm dependency locally is to use the pnpm CLI to extract and edit the package, then commit the patch file into your repository to unblock builds repeatably without waiting for an upstream release.

Does pnpm patch require exact version specs for modifying registry packages?

Yes, pnpm patch requires exact version specs. The workflow enforces exact versioning when extracting, editing, and replaying patches to ensure local fixes to registry packages remain reproducible across environments.

How do I remove an obsolete pnpm patch after an upstream release lands?

To remove an obsolete pnpm patch after an upstream release lands, use the designated patch removal workflow via the pnpm CLI to clean up the patch file and restore standard dependency resolution.

Can I use pnpm patch to create repeatable local fixes for broken registry packages?

Yes, you can use pnpm patch to create repeatable local fixes for broken registry packages by extracting, editing, and committing patch files into your repository, ensuring the fixes are applied consistently during future installations.

Why does patching a transitive dependency in pnpm require committing a patch file?

Patching a transitive dependency in pnpm requires committing a patch file to guarantee reproducibility. Replaying the patch during installs ensures the local fix persists across different environments without modifying the upstream package.