hogsend patch
Patch a @hogsend/* package in place using pnpm's native patch flow — extract, edit, and commit a persistent patch.
A thin wrapper over pnpm's native patch flow. Runs pnpm patch <package>, which extracts the package into a temp dir and prints the path to edit. After editing, commit the patch with the command pnpm prints (pnpm patch-commit <dir>).
hogsend patch <package> [--cwd <dir>]Patch is the middle rung of the Extend → Patch → Eject editability ladder — use it for small, surgical changes to a package without owning its full source. See Upgrading & Customizing for the full ladder.
This does not replace scripts/patch-check.sh (the patch re-apply contract).
The patch flow
- Run
hogsend patch <package>— this callspnpm patch <package>, which extracts the package into a temp directory and prints that path. - Edit the files in the printed temp directory.
- Commit the patch with the command pnpm prints:
pnpm patch-commit <dir>. pnpm records the diff and re-applies it on every install.
Options
| Option | Description |
|---|---|
--cwd <dir> | Project root to run pnpm in (defaults to the current directory). |
-h, --help | Show this help. |
Examples
hogsend patch @hogsend/enginehogsend eject
Vendor a @hogsend/* package's source into vendor/<name> and rewrite the consumer dependency to a local file: reference.
Hogsend for AI agents
The agent-ready surface — 14 vendorable Claude Code skills in every scaffolded app, the hogsend skills CLI, and /llms.txt as the stable machine entrypoint.