How do I install the Aio Patch Compile skill?

Run npx skillmds@latest add aiocean/aio-patch-compile 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 Aio Patch Compile 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 Aio Patch Compile?

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 Aio Patch Compile free to use?

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

Who published Aio Patch Compile?

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

Aio Patch Compile by aiocean — Agent Skill

Name: Aio Patch Compile
Author: aiocean

Aio Patch Compile

Apply tools/pipeline/patches.json + bun build --compile → patched claude binary at dist/<arch>/claude. Default: current host arch only (fast inner-loop ~1.2s). Opt-in --target=all (4 platforms) or csv list (e.g. --target=darwin-arm64,linux-amd64). If cli.js for a target arch is not yet extracted, transitively calls extract first. Strict by default (fails fast on MISSING patches).

aiocean a4d458d 3 files · 6.5 KB Updated Sep 17, 2026

File contents

aio-patch-compile — apply patches + bun build

Goal

Produce one or more patched claude binaries at dist/<arch>/claude. Inner loop after editing tools/pipeline/patches.json or any tools/pipeline/sources/*.js file.

Usage

/aio-claude-toolkit:aio-patch-compile                                   # current host arch only (default)
/aio-claude-toolkit:aio-patch-compile --target=all                       # all 4 platforms
/aio-claude-toolkit:aio-patch-compile --target=darwin-arm64,linux-amd64  # csv list
STRICT=0 /aio-claude-toolkit:aio-patch-compile                           # ALLOW missing patches (NOT recommended)

Behavior

For each target arch in the list:

If dist/<arch>/cli.js does NOT exist → transitively run ARCH=<arch> ./tools/extract.sh first
Run ARCH=<arch> ./tools/build.sh which: inlines sources/*.js, applies patches.json (strict by default), bun-compiles → dist/<arch>/claude

Requires

Walk-up must find a scaffolded project
bun (>= 1.3 for stable cross-compile)
python3 (for patch + inline scripts)
tools/pipeline/patches.json populated (NOT empty) — compile fails fast on empty patches

Drift recovery

If compile reports MISSING patches (anchors not found in cli.js), Claude version likely shifted:

Read .aio-patch-setup to see the tested-against Claude version
Use /aio-claude-toolkit:aio-patch-anchor find <fragment> to locate new anchor
Update tools/pipeline/patches.json old field with new anchor text
Re-run compile

See docs/repatching-playbook.md (step-by-step re-anchoring recipe) and docs/patches.md (anchor selection strategy).

Implementation

Invokes ${CLAUDE_PLUGIN_ROOT}/skills/aio-patch-compile/scripts/compile.sh "$@".

---name: aio-patch-compiledescription: Apply tools/pipeline/patches.json + bun build --compile → patched claude binary at dist/<arch>/claude. Default: current host arch only (fast inner-loop ~1.2s). Opt-in --target=all (4 platforms) or csv list (e.g. --target=darwin-arm64,linux-amd64). If cli.js for a target arch is not yet extracted, transitively calls extract first. Strict by default (fails fast on MISSING patches).---# aio-patch-compile — apply patches + bun build## GoalProduce one or more patched claude binaries at `dist/<arch>/claude`. Inner loop after editing `tools/pipeline/patches.json` or any `tools/pipeline/sources/*.js` file.## Usage```/aio-claude-toolkit:aio-patch-compile # current host arch only (default)/aio-claude-toolkit:aio-patch-compile --target=all # all 4 platforms/aio-claude-toolkit:aio-patch-compile --target=darwin-arm64,linux-amd64 # csv listSTRICT=0 /aio-claude-toolkit:aio-patch-compile # ALLOW missing patches (NOT recommended)```## BehaviorFor each target arch in the list:1. If `dist/<arch>/cli.js` does NOT exist → transitively run `ARCH=<arch> ./tools/extract.sh` first2. Run `ARCH=<arch> ./tools/build.sh` which: inlines `sources/*.js`, applies `patches.json` (strict by default), bun-compiles → `dist/<arch>/claude`## Requires- Walk-up must find a scaffolded project- `bun` (>= 1.3 for stable cross-compile)- `python3` (for patch + inline scripts)- `tools/pipeline/patches.json` populated (NOT empty) — compile fails fast on empty patches## Drift recoveryIf compile reports MISSING patches (anchors not found in cli.js), Claude version likely shifted:- Read `.aio-patch-setup` to see the tested-against Claude version- Use `/aio-claude-toolkit:aio-patch-anchor find <fragment>` to locate new anchor- Update `tools/pipeline/patches.json` `old` field with new anchor text- Re-run compileSee `docs/repatching-playbook.md` (step-by-step re-anchoring recipe) and `docs/patches.md` (anchor selection strategy).## ImplementationInvokes `${CLAUDE_PLUGIN_ROOT}/skills/aio-patch-compile/scripts/compile.sh "$@"`.

Frequently asked questions