update-muthur

Syncs vendored agent infrastructure from an upstream repository by triaging and porting commits.

Updated Nov 17, 2025
One-click install
npx skills add https://github.com/vzakharov/vovazakharov.com --skill update-muthur-vzakharov
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-muthur
Source: https://github.com/vzakharov/vovazakharov.com/tree/main/.claude/skills/update-muthur
Command: npx skills add https://github.com/vzakharov/vovazakharov.com --skill update-muthur-vzakharov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Repositories that vendor their agent infrastructure (CLAUDE.md, .claude/ skills, scripts) from an upstream source repo drift out of date as the source keeps evolving, and manually tracking which upstream commits apply is error-prone and repetitive. ## Core Features & Use Cases - Watermark-tracked sync: Reads .claude/skills/update-muthur/watermark.json to find the source repo and last synced SHA, then diffs only the adopted paths commit by commit. - Commit triage workflow: Classifies each candidate commit as take, translate, or one of several skip verdicts, with new skills offered exactly once and decisions recorded in the watermark. - Intent-based porting: Re-expresses upstream changes in the local repo's vocabulary rather than applying patches, ending with a consistency sweep and a final watermark bump. - Use Case: A maintainer says "sync muthur" and the skill clones vzakharov/muthur with a blobless partial clone, lists commits since the last sync touching adopted paths, triages each by rationale, ports the applicable ones as separate local commits, and advances the watermark. ## Quick Start Say "update muthur" or "sync the source" to pull the latest agent-infrastructure changes from the upstream repository and port the ones that apply.

Frequently Asked Questions about update-muthur

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

FAQPage Schema
How do I sync vendored files from an upstream GitHub repository?

Track the source repo and last synced SHA in a watermark file, clone the source with a blobless partial clone, and run git log over the adopted paths to list candidate commits. Triage each commit by its rationale, port the applicable ones by intent, and bump the watermark as the final commit.

How do I update Claude agent infrastructure copied from another repo?

Invoke the sync skill with a phrase like "update muthur" or "sync the source". It reads the watermark, diffs the upstream repo since the last sync, triages commits as take, translate, or skip, and re-expresses applicable changes in your repo's vocabulary.

Why not use git cherry-pick or git apply to port upstream changes?

Cherry-pick and git apply fail because local files are de-vendored rewrites, not copies, so every hunk conflicts. The correct approach is reading the upstream diff to understand intent and re-expressing it in the local repo's file layout and vocabulary.

What happens if the watermark file itself gets synced from upstream?

Syncing the watermark overwrites your repo's source pointer and last synced SHA with foreign values, causing an unresolvable SHA failure on the next sync. The watermark file must be excluded unconditionally, even though it lives inside an adopted directory.

When should a skipped upstream commit be reconsidered?

Declined paths whose recorded reason no longer holds should be re-offered on every sync, since most decline reasons are conditions that can flip. Only reasons explicitly marked as permanent are exempt from re-reading.