Initialize a repository

Initialize a repository in Git — 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 fresh repository for the new payment-service project. Initialize a repo in the current…
I need a fresh repository for the new payment-service project. Initialize a repo in the current folder, create an initial commit that includes README.md and .gitignore, and set the main branch name to main so our CI picks it up. Confirm the commit hash and show the branch name after initialization.

Improve — make it easier to accept

+
Before I initialize this repo for payment-service, make it easy for teammates to start: put the…
Before I initialize this repo for payment-service, make it easy for teammates to start: put the purpose and quick start in README.md, add a .gitignore that excludes node_modules and build outputs, and ensure the branch will be called main. Flag anything that would confuse a reviewer or break CI on first push.

Decide — diagnose the stuck moment

+
I just created the project folder for payment-service and I'm unsure about the next step. I want a…

I created the project folder and want to track it with version control

I just created the project folder for payment-service and I'm unsure about the next step. I want a clean initial commit and the branch named main so CI works. Tell me the likely pitfalls I might hit on initialization (wrong branch name, missing .gitignore, empty commit), and the exact minimal sequence of commands and checks to follow so the repo is ready for the first push.

Become — change the pattern

+
Across multiple projects, we lose time fixing initial commits, correcting branch names from master…

We keep creating repos with messy initial commits and wrong branch names

Across multiple projects, we lose time fixing initial commits, correcting branch names from master to main, and adding .gitignore afterwards. What habit should I change in our repo creation checklist so every new repo starts clean with the right branch name, sensible ignores, and a purposeful README? Suggest a short template and a simple enforcement step.

Next to this one

Other version control work people do in Git.

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.