skills.rest
zmerlynn
zmerlynnCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

update-upstream

Bump manifold3d pins and align Rust FFI bindings with upstream changes.

19|5|Updated Apr 8, 2026
Search Tags:#rust#update#bindings#ci#ffi#upstream#manifold3d
One-click install
npx skills add https://github.com/zmerlynn/manifold-csg --skill update-upstream
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: update-upstream
Source: https://github.com/zmerlynn/manifold-csg/tree/main/.claude/skills/update-upstream
Command: npx skills add https://github.com/zmerlynn/manifold-csg --skill update-upstream

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of keeping manifold3d bindings in sync with upstream releases, including pin updates, patch audits, and PR preparation.

Core Features & Use Cases

  • Automates the pin update to upstream manifold3d and updates related FFI wrappers.
  • Audits carry-patches against upstream PRs to prune or adjust patches, ensuring clean merges.
  • Prepares and coordinates a PR with updated bindings, tests, and documentation to release changes.

Quick Start

Run the update-upstream skill to bump the manifold3d pin, bind new C API changes, and open a PR.

Frequently Asked Questions about update-upstream

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

FAQPage Schema
How do I update Rust FFI bindings after an upstream manifold3d release?▼

To update Rust FFI bindings after an upstream manifold3d release, you bump the MANIFOLD_VERSION pin, audit carry-patches against upstream PRs, align the FFI wrappers, and prepare a pull request. This process keeps bindings compatible with new C API changes.

What is the best way to automate manifold3d pin updates and patch auditing?▼

Automating manifold3d pin updates involves bumping the version pin and auditing carry-patches against upstream PRs to prune or adjust them. This ensures clean merges and coordinates a PR with updated bindings, tests, and documentation to release changes.

How do I align Rust bindings with manifold3d upstream C API changes?▼

Aligning Rust bindings with manifold3d upstream C API changes requires updating the FFI wrappers after bumping the upstream pin. You must edit MANIFOLD_VERSION, apply patches, build the project, and run tests to verify compatibility before submitting a PR.

When do I need to audit carry-patches for manifold3d bindings?▼

You need to audit carry-patches for manifold3d bindings after bumping the upstream pin to ensure clean merges. Auditing checks existing patches against upstream PRs to prune or adjust them, preventing conflicts and maintaining binding compatibility.

Can I use this update-upstream workflow for Rust projects without existing carry-patches?▼

This update-upstream workflow for Rust projects focuses on bumping manifold3d pins, updating FFI bindings, and auditing existing carry-patches. If no carry-patches exist, it skips patch pruning and proceeds directly to building, testing, and PR preparation.

Why does updating manifold3d bindings require editing MANIFOLD_VERSION?▼

Updating manifold3d bindings requires editing MANIFOLD_VERSION because this pin specifies the exact upstream release version. Changing it triggers the update process for FFI wrappers and patch audits to align Rust bindings with the new upstream code.

Related Skills

Explore More Software Engineering Skills→
RediSearchRediSearch
6.2k

port-c-module

Port a C module to Rust with crate creation and FFI wrapping.

Official
Advanced
raineraine
2.1k

rebase

Rebase current branch onto main or specified origin branches with conflict resolution.

Community
Basic
AJV009AJV009
1

drupal-contrib-mgmt

Coordinate patch-based upgrades for Drupal contributed modules with Composer and validate compatibility before deployment.

Community
Advanced
novelsaganovelsaga

ffi-diplomat

Expose Rust types to C/C++ and WASM via Diplomat FFI bindings.

Official
Intermediate