aio-patch-setuplisted

Scaffold a new Claude-binary-patching project at CWD (or [target_dir]). Copies generic pipeline tools (extract/build/run, Python pipeline scripts, cli-nav AST navigator) + generic docs/guides into the target. Patches.json starts EMPTY — user fills it in; a reference example from the dirty-claude project is shipped beside it.
aiocean/claude-plugins · ★ 3 · AI & Automation · score 65

Install: claude install-skill aiocean/claude-plugins

# aio-patch-setup — scaffold a new Claude-binary-patching project ## Goal Drop a complete, runnable patching pipeline into the target directory so the user can immediately: 1. Edit `tools/pipeline/patches.json` (start from empty schema or copy from `patches.json.example`) 2. Run `/aio-claude-toolkit:aio-patch-extract` to extract cli.js + natives from their installed claude 3. Run `/aio-claude-toolkit:aio-patch-compile` to apply patches + recompile a custom claude binary 4. Run `/aio-claude-toolkit:aio-patch-run` to exec the patched binary ## What gets copied | Path | Source | User-owned? | |------|--------|-------------| | `tools/extract.sh` | templates/tools/extract.sh (synced from dirty-claude + ARCH patch) | No — generic | | `tools/build.sh` | templates/tools/build.sh | No — generic | | `tools/run.sh` | templates/tools/run.sh | No — generic | | `tools/pipeline/*.py` | dirty-claude pipeline (extract_cli, patch_cli, resolve_symbols, inline_sources, extract_native_modules) | No — generic | | `tools/pipeline/patches.json` | **EMPTY schema template** | **YES — user content** | | `tools/pipeline/patches.json.example` | dirty-claude pinned reference | No — reference | | `tools/pipeline/sources/*.example` | dirty-claude reference patch body | No — reference | | `tools/cli-nav/*.cjs` | AST navigator (acorn-based) | No — generic | | `docs/*.md` | curated generic guides (anchor strategy, drift recovery, etc.) | No — generic | | `.gitignore` | sensible defaults (dist/, *.backup, _