Pulling base updates

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

1) Call it

Call it in natural language or with the slash command.

pull base updates

Or /update-from-base. The first call guides registering the base as a git remote automatically, so there’s no need to type it by hand ahead of time.

2) What changes and what stays

An update splits in three by file location.

• Auto-updated — the skills, agents, hooks, AI_AUTOMATION.md, and publish scripts the base holds. The base manages these, so they get overwritten with the new version.
• Never touched — your own posts (_workspace/posts/), blog IDs (.env), credentials (credentials.json, token.json), 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 what to do.

Since your posts and credentials are in spots that stay safe, there’s no worry of an update wiping out a post.

3) What one cycle looks like

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 the publish script 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

Destructive commands aren’t run automatically; they get one more confirmation. It usually finishes in 30 seconds to 2 minutes.

4) Why the publish script is auto-updated

The Blogger publish script (deploy_to_blogger.py) is the spot that enforces the AI-smell gate at the code level. If a user modifies this script, the gate could be neutralized, so the base manages it and updates it automatically. To change publishing behavior, adjust it where it follows the gate policy rather than editing the script directly.

5) The detailed spot

Which file goes in which column by area, and rare situations like a force-push, are written up in expert updates. At a beginner pace, “posts and credentials are safe, base improvements are received automatically, and the confusing spots get asked about” is enough.