mcpField
U
update

update

github.com/nextwork-projectsDevelopment13416 installsUpdated 1d ago
Repository

About update

A Claude skill that guides updates to the ai-video-editor-cooked project across marketplace installs, clones, and forks. It checks incoming changes, merges them while preserving user work, and runs verification with a rollback path.

Key features

  1. 01Identify the installation type
  2. 02Check commits and changelog entries
  3. 03Merge updates while retaining user changes
  4. 04Resolve conflicts file by file
  5. 05Verify changes and roll back if needed

Use cases

  1. 01Update a marketplace installation
  2. 02Bring upstream changes into a fork
  3. 03Review update impact on edited files
  4. 04Recover when update verification fails

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/nextwork-projects/ai-video-editor-cooked --skill update

After installing, type/updatein Claude Code to confirm it loaded.

Bundled filesscripts/update.py

Details

From the project README

Update

Paths: ${CLAUDE_SKILL_DIR} means the folder containing this SKILL.md, and ${CLAUDE_PLUGIN_ROOT} the plugin folder two levels above it.

Every question goes in the question box: the AskUserQuestion tool (2-4 options, recommended first). Only in an agent without it, ask numbered questions in text.

U="${CLAUDE_SKILL_DIR}/scripts/update.py". Run it with python3 on Mac and Linux, py on Windows. Add --repo <folder> when the user's clone is not the folder Claude Code runs in.

Never push, never force-push, never delete a branch, never stash or reset the user's uncommitted work. Pushing to their fork happens only when they ask for it.

1. Which install

python3 "$U" where
  • marketplace: run python3 "$U" market. It runs claude plugin marketplace update nextwork, then claude plugin update for ai-editor@nextwork and creator-teardown@nextwork itself. Then tell them to type /reload-plugins. If it fails, say the lines it prints instead. Their styles, skills and settings live in their own folder and survive (docs/customise.md). Stop here.
  • plain clone: say the three fork steps it prints. Stop here.
  • a fork, run outside its clone: ask for the folder of their clone, then use --repo.
  • fork, upstream missing: ask "Add nextwork-projects/ai-video-editor-cooked as upstream so updates can come from it?" (Yes, add it (Recommended) / No). On yes: python3 "$U" add-upstream.

2. Check

python3 "$U" check

Tell the user in a few lines: how many new commits, the CHANGELOG lines they bring (plain words, the ones they would notice), and which of their changed files the update also touches. Then ask Update now (Recommended) / Not now.

3. Merge

python3 "$U" merge
  • Exit 2, uncommitted changes: show what it printed. Ask Commit them as "my changes" (Recommended) / I'll handle it myself. Commit only on a yes, then merge again. Never stash.
  • Exit 0: go to step 4.
  • Exit 3, conflicts: resolve them file by file. For each file, keep the user's change and take upstream's fix, and say what you did in one line ("captions.tsx: kept your font, took the new safe-zone fix"). When the two really clash and the choice is theirs (both changed the same setting to different values), ask in the question box with each side as an option, theirs first. Then git add each file and git commit --no-edit.

The backup branch is before-update-<date>; say its name once.

4. Verify

python3 "$U" verify

It runs tests/check_plugins.py and tests/demos.sh. Pass: tell them to type /reload-plugins (and, if they installed from their fork on GitHub, that pushing to it and /plugin marketplace update nextwork brings it there, when they want). Fail: show the failing checks and ask Fix them (Recommended) / Go back to before the update. Going back:

python3 "$U" rollback

It aborts an unfinished merge or moves the branch back to the backup. No branch is deleted.

Comments

Markdown supported