Skip to content

Pulling base updates

This step is optional and only looked at when needed. When the base (ddakit/scene-studio) adds a new skill or improves a policy, this is the spot for bringing that change into your work. It’s built so you can receive it safely without knowing commands like git rebase.

pull base updates

Or /update-from-base. The first call guides registering the base as a git remote automatically.

An update splits in three by file location.

  • Auto-updated — the skills, agents, hooks, and AI_AUTOMATION.md the base holds. The base manages these, so they get overwritten with the new version.
  • Never touched — every video in progress (_workspace/), the channel identity, the license. Updates don’t overwrite these spots.
  • Asks you — spots like CLAUDE.md and README.md where base and your edits can mix. It doesn’t overwrite automatically; it asks.

Since every video in progress and the channel identity are in safe spots, there’s no worry of an update wiping out a video.

Calling /update-from-base flows roughly like this.

  1. If there are unsaved changes, it tells you to save them first
  2. It pulls the base’s latest changes
  3. It summarizes what changed (N new skills, whether a policy updated, etc.)
  4. If you agree, it applies only the auto-update spots
  5. For the asking spots, you choose what to do one at a time
  6. It verifies after applying and suggests a commit

It usually finishes in 30 seconds to 2 minutes.

When the base tightens the Fair Use bar or the number of transformation duties in license-policy, that change comes in as an auto-update spot. After receiving it, remix videos are verified with the updated policy. Copyright carries legal responsibility, so when the base tightens the policy, it’s safer to receive it.

Which file goes in which column by area is written up in expert updates. At a beginner pace, “videos in progress are safe, base improvements are received automatically, and the confusing spots get asked about” is enough.