Fetch remote branches

Fetch remote branches in GitHub — 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 to update my view of remote branches so I can start work on the feature branch that others…
I need to update my view of remote branches so I can start work on the feature branch that others pushed. Fetch all remote branches from origin to my local repo without merging anything. After fetching, list new or updated remote branch names and the last commit for each. If authentication fails or no new branches are found, explain why and what to try next.

Improve — make it easier to accept

+
Before I fetch remote branches for a release review, make it easy for me to see what's relevant.…
Before I fetch remote branches for a release review, make it easy for me to see what's relevant. Show which remote branches changed in the last week, surface branches with work-in-progress labels or long-running feature names, and flag any branch whose HEAD modifies build or deployment scripts. Recommend which three branches I should check out locally and why.

Decide — diagnose the stuck moment

+
I fetched origin but the expected remote branch feature/login-reset is not appearing in my local…

fetch didn't show the branch I expected

I fetched origin but the expected remote branch feature/login-reset is not appearing in my local refs. The contributor says they pushed it yesterday. I am worried they pushed to the wrong remote or I missed auth. I cannot tell which happened. Diagnose the likely causes and give the concrete commands I should run to verify where that branch actually is and how to fetch it.

Become — change the pattern

+
Across projects I keep missing coworkers' branches and start work on stale code. I lose context and…

I repeatedly miss new remote branches

Across projects I keep missing coworkers' branches and start work on stale code. I lose context and extra PRs pile up. Recommend one change to my daily routine and a small git habit that ensures I see new remote branches promptly without noisy fetch spam.

Next to this one

Other code hosting work people do in GitHub.

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.