使用方法
- 复制安装命令，在自己的智能体环境安装前先检查源码包。
- 从原始文档核对所需工具、凭据和支持的宿主。
- 说明输入材料与期望交付物，并对照来源检查输出。
npx skills add https://github.com/nextwork-projects/ai-video-editor-cooked --skill update开始前需了解
- 安装不包含模型订阅、API 额度或访问文件的权限。
- 仓库星数和安装量反映活跃情况，不等于独立质量或安全测试。
按源仓库内容呈现，保留标题、案例、代码、表格、链接以及原文引用的演示图片。
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 runsclaude 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
upstreamso updates
can come from it?" (Yes, add it (Recommended) / No). On yes: python3 "$U" add-upstream.
2. Check
python3 "$U" checkTell 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" verifyIt 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" rollbackIt aborts an unfinished merge or moves the branch back to the backup. No branch is deleted.
