tk-studio-base-update
Adopt a new upstream BMad release as one reviewable motion — bump the bmad.lock pin, rerun the upstream installer, open the integration PR. Use when the user says "base update", "bump bmad", "update the base", or "adopt the new BMad release".
- License 许可
- MIT
- 最近更新
- 2026-11-10
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- tk-studio-base-update
- description
- Adopt a new upstream BMad release as one reviewable motion — bump the bmad.lock pin, rerun the upstream installer, open the integration PR. Use when the user says "base update", "bump bmad", "update the base", or "adopt the new BMad release".
02 资源文件 2
- 其他customize.toml495 B
- 脚本scripts/base_update.py14.8 KB
03 SKILL.md 正文
tk-studio-base-update
The only writer of bmad.lock pins (AD-1). The team adopts upstream changes
in lockstep through a reviewable integration PR — never a fork, never an
unreviewed mutation of main.
Behavior (both modes)
-
Determine the target: a new core version (
--core 6.11.0) and/or module pins (--pin tea=v1.20.0, repeatable). Attended, if the operator hasn't named a version, look up the latest upstream release and confirm the target with them first. Headless requires the target in the payload — a missing target isblocked, never a guess (AD-11). -
Run the whole motion through the plugin root, from the studio repo root (this skill operates on the repo that owns
bmad.lock):uv run "${CLAUDE_PLUGIN_ROOT}/skills/tk-studio-base-update/scripts/base_update.py" \ --core <version> [--pin MODULE=TAG ...] --directory <studio-repo-root>The script: preflight (clean tree) → isolated
base-update/*branch → lock bump commit → pinned non-interactive reinstall with verify (emitsinstall-outcome) → churn normalization (provably churn-only files the installer rewrote are reverted; per-class revert counts land in the result JSONnormalized; real changes and unknown churn always show) → sha sync + install-diff commit → push +gh pr create.--dry-runpreviews;--no-prstops after the local commits.A same-version re-affirmation whose install diff is empty after normalization ends complete reporting the verified no-op — no branch pushed, no PR opened, the bump branch dropped (the result JSON says
"outcome": "verified-no-op"):{"status": "complete", "intent": "tk-studio-base-update", "artifacts": [], "reason": null} -
On success, attended: optionally enrich the PR description with a summary of the upstream release notes (
gh pr edit). Nothing merges automatically — say so and stop; review is the membrane (AD-12). -
On installer failure the script has already restored the tree, returned to the starting branch, and left the bump branch for inspection —
install-outcome: failurewas emitted. Report the failing step; end headless runsblocked:{"status": "blocked", "intent": "tk-studio-base-update", "artifacts": [], "reason": "install-at-new-pin failed: <detail>; branch base-update/... left for inspection"}On success:
{"status": "complete", "intent": "tk-studio-base-update", "artifacts": ["bmad.lock", "<pr-url>"], "reason": null}
If the deterministic core is unrunnable — a tool call denied by permissions, uv/python unavailable — end blocked with the status block naming the unrunnable core as reason: never a question, never a headless run that ends without the block (AD-11).
Rules
- Never edit
_bmad/by hand and never bump pins outside this motion (NFR1). - Never merge the PR from this skill; the integration PR is for human review.
- A same-version run (
--coreequal to the current pin) is a legitimate re-affirmation of the motion, not an error.
04 同仓库更多 Skills
tk-studio-track
Tracking verbs on the bound Jira project — `block` moves a story the loop cannot progress, and each dependent story, to "Blocked - Awaiting User" with a comment that @mentions the owner (or, with `--engagement`, one engagement's questions issue, which `close` later moves to "Done"); `reply` posts the owner's answer (or "Done.") with the owner's host-only token and moves the issue to "Block Resolved"; `validate` checks that resolution and passes the issue back to work or re-blocks it with a follow-up. Use when the user says "block this story", "tk track block", "put it in the owner's inbox", "reply to the blocked issue", "validate the resolution", or a supervisor or engagement payload names this skill.
tk-studio-session
Session discipline as a surface — land a boundary handoff (optionally carrying knowledge deltas) and end the session, or resume a fresh session from a run workspace alone. Use when the user says "hand off this run", "tk session", "resume the run", or a boundary/budget trigger says the session must split.
tk-studio-research
Run a chartered research pass — survey the topics a charter scopes, grade every finding by evidence, land the findings in the run workspace, and emit observation events for recommendation-worthy ones. Use when the user says "run the ecosystem watch", "tk research", or a research job's invoke-skill directive names this skill.
tk-studio-report
One-verb human defect report — "the skill did the wrong thing" — recorded as a report event in the local measurement ledger. Use when the user says "tk report", "report a defect", "that skill misbehaved", or "log a studio issue".
tk-studio-playable-judge
The playable-verify leg's screenshot judge (Story 34.3) — reads only a playable run's report.json and its frames, answers the fixed rubric (scene loaded, player visible and framed, no magenta or error overlay, HUD reads, the named moments shown) with pass or fail and findings each naming a frame and a rubric line. Driven headless by the supervisor's host leg on the project's sandbox tier; use when the payload names a playable `media` folder, or the user says "judge the playable frames".
tk-studio-plan-sync
Planning adapter — canonicalize BMad-native planning artifacts (normalize pass, sole id authority) and sync them with the bound planning backend. Use when the user says "sync the plan", "normalize planning artifacts", "tk plan sync", or after stock BMad planning flows produce or change epics/stories.