pocock-sync

Reviews upstream mattpocock/skills commits and adopts fitting changes into adapted mx skills.

3|Updated Jan 10, 2026
One-click install
npx skills add https://github.com/MaxWolf-01/agents --skill pocock-sync-maxwolf-01
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pocock-sync
Source: https://github.com/MaxWolf-01/agents/tree/main/.claude/skills/pocock-sync
Command: npx skills add https://github.com/MaxWolf-01/agents --skill pocock-sync-maxwolf-01

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping a locally adapted fork of Matt Pocock's agent skills current is tedious: you must track which upstream commits matter, translate upstream conventions into local ones, and avoid re-litigating changes you already rejected. This Skill systematizes that review against a recorded baseline commit. ## Core Features & Use Cases - Baseline-tracked review: Walks git log from a recorded baseline commit to upstream HEAD, classifying every commit as mapped-skill change, new upstream skill, or noise. - Explicit skill mapping: Maintains a mapping table between mx skills and upstream skills, including dissolved skills (implement, to-spec, wayfinder) and renamed ones (tdd, ask-matt, domain-modeling). - Approval-gated adoption: Presents per-item tables quoting current vs proposed text with a recommendation, applies only approved changes, and records deliberate rejections in the baseline-bump commit. - Use Case: After a few weeks, ask to check Matt Pocock's latest skill changes; the Skill clones the upstream repo, reviews new commits, and proposes only the diffs relevant to your adapted mx skills. ## Quick Start Ask the agent to check and sync Matt Pocock's latest skill changes against the recorded baseline.

Frequently Asked Questions about pocock-sync

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

FAQPage Schema
How do I sync local agent skills with an upstream repository?

Clone the upstream repo fresh, run git log from your recorded baseline commit to HEAD, and classify each commit by which local skill it affects. Present proposed changes for approval before applying them, then move the baseline forward to the reviewed HEAD.

How to track which upstream commits were already reviewed?

Record the last reviewed upstream commit hash as a baseline line in the SKILL.md file itself. Every sync ends by updating that line to the reviewed HEAD, making it the single source of truth for where review left off.

Can this handle renamed or restructured upstream skills?

Yes, the Skill maintains an explicit mapping covering same-named, dissolved, and renamed upstream skills. For example, upstream tdd maps to local testing material, and dissolved skills like implement map onto the dispatch worker prompt.

Does syncing automatically apply all upstream changes?

No, every substantive change is presented in a per-skill table quoting current versus proposed text with a recommendation. The user approves each item individually, and deliberate rejections are recorded so they are not re-proposed.

What happens when upstream conventions differ from local ones?

Upstream vocabulary is translated before adoption: .scratch/ becomes agent/, /skill becomes /mx:skill, docs/adr/ becomes decisions/, and GitHub issues map to the local tracker conventions. Changes are adapted, never copied verbatim.