llama-stage-patch-changes

Regenerate the llama-stage.cpp patch queue and update the upstream SHA pin.

3.1k|376|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/Mesh-LLM/mesh-llm --skill llama-stage-patch-changes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: llama-stage-patch-changes
Source: https://github.com/Mesh-LLM/mesh-llm/tree/main/.agents/skills/llama-stage-patch-changes
Command: npx skills add https://github.com/Mesh-LLM/mesh-llm --skill llama-stage-patch-changes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Maintains the llama-stage.cpp patch queue and the upstream pin so that local changes remain aligned with the official llama-stage upstream and do not drift.

Core Features & Use Cases

  • Patch queue maintenance: Keep patches organized in third_party/llama-stage.cpp/patches and regenerate them from upstream.
  • Upstream pin management: Track the pinned upstream SHA and update it consistently.
  • Safe editing discipline: Avoid editing the .deps patch base directly; perform updates via the patch queue workflow.
  • Scope aware: Focuses on the stage ABI surface, patches, and related hooks while preserving overall mesh-llm behavior.

Quick Start

Run the patch workflow to prepare and maintain the llama-stage patch queue.

Frequently Asked Questions about llama-stage-patch-changes

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

FAQPage Schema
How do I maintain a patch queue for upstream C++ library changes?

Maintaining a patch queue involves keeping durable patch files organized in a patches directory and using a preparation script to regenerate them. This workflow ensures local changes remain aligned with the official upstream and do not drift.

What is the best way to update an upstream SHA pin without breaking ABI compatibility?

Updating an upstream SHA pin requires tracking the pinned commit and regenerating the patch queue via a preparation script. This approach ensures the stage ABI surface remains compatible and local changes do not drift from the official upstream.

Can I edit the patch base directly when updating third_party library files?

You should not edit the patch base directly when updating third_party library files. Instead, perform updates through the patch queue workflow to maintain safe editing discipline and preserve overall repository behavior.

How does a patch queue workflow keep local C++ changes from drifting upstream?

A patch queue workflow keeps local changes from drifting by pinning a specific upstream SHA and storing modifications as durable patch files. Running a preparation script regenerates the queue to maintain alignment across the repository.

When do I need to regenerate a patch queue for an ABI surface?

You need to regenerate a patch queue for an ABI surface when applying updates to third_party library files or modifying stage hooks. Running the preparation script ensures patches and upstream pins remain consistent across the mesh repository.