Create a new branch

Create a new branch 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 a working branch to implement the new payments endpoint. Create a new branch named…
I need a working branch to implement the new payments endpoint. Create a new branch named feature/payments-2026-07-17 off the current main, ensure my working tree is clean before creating it, and switch to it. If main is behind origin/main, warn me and offer to rebase or pull first. After creating the branch, print the branch name and current HEAD commit.

Improve — make it easier to accept

+
Before I create a new feature/payments branch, make it easy for reviewers later. Recommend a branch…
Before I create a new feature/payments branch, make it easy for reviewers later. Recommend a branch name that encodes ticket number, scope, and date; suggest a checklist of files to avoid committing (secrets, local env overrides), and show a short commit template to use for the first commit so history reads well in PRs.

Decide — diagnose the stuck moment

+
I created feature/payments but later realized I started it from an older main and not origin/main.…

I created a branch and later found it's off the wrong base

I created feature/payments but later realized I started it from an older main and not origin/main. I am worried the PR will include unrelated commits and confuse reviewers. I cannot tell whether to rebase or recreate the branch. Recommend the safest corrective action and the exact sequence of commands to fix the branch while preserving my work and minimizing force-push risk.

Become — change the pattern

+
I often start work on a new branch and only later discover it's based on stale code, which bloats…

I keep creating branches from stale bases

I often start work on a new branch and only later discover it's based on stale code, which bloats PRs and wastes reviewers' time. Help me adopt one small habit and a quick checklist that prevents creating branches from the wrong base without slowing me down.

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.