Pull latest changes

Pull latest changes in Visual Studio Code — with the four heights of help laid out: do it now, make it easier for the next person to accept, work out the right move when you are stuck, and learn the pattern so it stops coming back.

4prompt heights
Open it in the interactive atlas →

The four heights

The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.

Execute — do the immediate task

+
I need the branch up to date before I run the new feature locally. Pull origin/main into my current…
I need the branch up to date before I run the new feature locally. Pull origin/main into my current branch and stop if there are conflicts; tell me which files changed and whether any migrations or dependency updates were pulled in.

Improve — make it easier to accept

+
Before I pull the main branch into feature/julie-search, make this safe and easy: show a short…
Before I pull the main branch into feature/julie-search, make this safe and easy: show a short summary of incoming commits with author and message, highlight commits that touch database migrations, lockfile, CI scripts, or public APIs, and warn if tests or linters have recently failed on those commits.

Decide — diagnose the stuck moment

+
I just pulled latest and two new DB migrations landed from Marco. I haven’t run them locally and…

I ran pull and two migrations landed.

I just pulled latest and two new DB migrations landed from Marco. I haven’t run them locally and I’m worried about data shape and test flakiness. I can’t ask Marco right now. What’s the most likely risk and the best immediate steps to validate the migrations locally without affecting prod or my branch state?

Become — change the pattern

+
Every time I pull origin/main into feature branches I get surprise changes that break my local runs…

Pulls keep introducing hidden work to my branch.

Every time I pull origin/main into feature branches I get surprise changes that break my local runs or tests. Where am I losing time and what one habit or repo practice should I change so pulls are predictable and don’t repeatedly derail my work?

Next to this one

Other code editor work people do in Visual Studio Code.

Every task here came from the work, not from a feature list — which is why the prompts name what you want done and never the button that does it. The tool changes; the work does not.
Copyright © LLOS.ai · 2026 — original pedagogy, voice, and design — all rights reserved.

The rest of the map

Same library, five ways in.