Updating the Framework

The public repository gets updated — improved thinking process skills, refined rules, new documentation. Your system is separate, so updates do not happen automatically.

Check your version

cat FRAMEWORK_VERSION

Compare against the repository. Different means an update is available.

Set up the upstream remote — once

git remote add upstream https://github.com/lesixcompanies/90mm-real-estate-bos.git

Pull the update

Easiest: tell Claude Code “Update the base framework from the upstream repository and push the changes to my GitHub.”

By hand:

git fetch upstream
git checkout upstream/main -- .claude/skills/ .claude/rules/ .claude/agents/ .claude/settings.json templates/session-summary.md README.md LICENSE FRAMEWORK_VERSION FRAMEWORK_FILES.md .gitignore
git add -A
git commit -m "Updated framework to latest version"
git push

That long list of paths is doing the important work: it names exactly what gets replaced. Nothing outside it is touched.

What changes, and what never does

Updated	Never touched
Thinking process skills	Your `CLAUDE.md`
Rules and methodology	Context files
Agent documentation	Pipeline, processes, diagnostics
Session summary template	Decisions log
README, LICENSE, version files	Projects and archives
	Custom skills and sub-agents
	`soul.md` and `communication-style.md`
	Weekly and monthly review templates

The definitive list for your version is in FRAMEWORK_FILES.md inside your own system.

On your second computer

After updating and pushing on one machine:

git pull

If it fails

A merge conflict here almost always means you edited a framework file — see If You Edited a Framework File.

If You Edited a Framework File