3 ready prompts
Written for the moment this actually comes up.
Improve — make it easier to accept
+Before I push this global ignore to other devs, make the common patterns visible. Produce a…
Improve — make it easier to accept
+Before I push this global ignore to other devs, make the common patterns visible. Produce a proposed global exclude that covers editor swap files, OS metadata, and IDE folders we never commit. Add comments explaining why each pattern exists and flag any patterns that risk hiding files we might want to track (for example, .env). Ladder":"L2"
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Decide — diagnose the stuck moment
+I added *.log to my global exclude and my repository still shows server.log as untracked. I am…
Decide — diagnose the stuck moment
+I added a pattern but files still appear in status
I added *.log to my global exclude and my repository still shows server.log as untracked. I am worried the file is already tracked or my global exclude is misconfigured, and I cannot tell which. What is the likely reason and the quickest command to prove whether server.log is already tracked by the repo? Ladder":"L5"
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Across projects we keep committing OS files and IDE folders because new engineers set different…
Become — change the pattern
+Each developer maintains different ignore rules and we commit junk
Across projects we keep committing OS files and IDE folders because new engineers set different local ignores. This causes noisy diffs and wasted code-review time. Recommend one team habit and one repo-level change that will reduce accidental commits of junk across all developers. Ladder":"L6"
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
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.