Stash local changes

Stash local changes in Git — with three ready prompts, from the immediate task to the lasting pattern.

3prompt heights
Open it in the interactive atlas →

3 ready prompts

Written for the moment this actually comes up.

Execute — do the immediate task

+
Stash my local edits in the feature/ui branch so I can switch to main and pull the latest changes.…
Stash my local edits in the feature/ui branch so I can switch to main and pull the latest changes. Save the stash with a message 'WIP: refactor dropdown for B2B demo', verify the stash is recorded, switch to main, pull origin/main, then return to feature/ui and apply the stash if requested.

Improve — make it easier to accept

+
Before I stash, make it easy for me to resume: show which files are modified and why they might…
Before I stash, make it easy for me to resume: show which files are modified and why they might conflict with main, suggest whether to stash only tracked files or include untracked assets, and warn if the working tree contains generated files that shouldn't be stashed. Recommend a clear stash message.

Become — change the pattern

+
Our team keeps accumulating messy local commits and diverging branches because people avoid…

Developers hoard messy local commits instead of stashing

Our team keeps accumulating messy local commits and diverging branches because people avoid stashing or creating clear WIP commits. This clutters history and makes code review harder. Where are we failing in basic local workflow habits, and what simple rules or rituals would reduce stolen time and messy histories while keeping developers productive?

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.