stash
Skill2 starsChanged 4 months agoMITView on GitHub
Save, restore, and manage work-in-progress with git stash — shelve uncommitted changes to switch context, then bring them back without losing work. Use when the user says "stash my changes", "shelve this work", "save my work in progress", "pop the stash", "I need to switch branches but have uncommitted changes", "restore my stashed changes", or "clean up my stashes".
3 other projects use a version of this.
Adopted by
Most recently taken up by
- grooverLab/stashtheir own version, first seen Oct 20, 2026
- yiyaw-lab/agent-armortheir own version, first seen Jun 22, 2026
- hoktaar/claude-skillstheir own version, first seen Mar 20, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- yiyaw-lab/agent-armor★ 1same name
- grooverLab/stash★ 0same name
- hoktaar/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository68 other files it gives its agents.
- a11ySkill
- api-docsSkill
- audit-logSkill
- benchmarkSkill
- bisectSkill
- cacheSkill
- changelogSkill
- cherry-pickSkill
- ci-setupSkill
- codeownersSkill
- commit-messageSkill
- connection-poolSkill
- contributingSkill
- coverageSkill
- db-migrateSkill
- dead-codeSkill
- debugSkill
- depsSkill
- diagramSkill
- dockerizeSkill
- docstringSkill
- e2eSkill
- env-exampleSkill
- error-handlingSkill
- explainSkill
- feature-flagSkill
- flaky-testSkill
- gitignoreSkill
- graceful-shutdownSkill
- graphqlSkill
- healthcheckSkill
- i18nSkill
- idempotencySkill
- licenseSkill
- lint-fixSkill
- loggingSkill
- migrateSkill
- mockSkill
- onboardSkill
- optimizeSkill
- paginationSkill
- pr-descriptionSkill
- pre-commitSkill
- profileSkill
- prune-branchesSkill
- rate-limitSkill
- readmeSkill
- rebaseSkill
- refactorSkill
- regexSkill
- releaseSkill
- resolve-conflictsSkill
- retrySkill
- review-diffSkill
- scaffoldSkill
- secrets-scanSkill
- security-headersSkill
- seedSkill
- soft-deleteSkill
- sqlSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 0 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 25
Use a descriptive message: git stash push -m "<what this is>" so the entry is identifiable later — never an anonymous stash when several …
- Very specific: line 29
Prefer git stash apply <ref> over pop when unsure — apply keeps the stash so a botched restore is recoverable.
- Very specific: line 31
If applying may conflict (the branch moved on), say so first.
- Very specific: line 37
Default to non-destructive actions: apply over pop, named saves over anonymous, and never drop/clear without explicit confirmation of which …
- Very specific: line 38
Always give saved stashes a descriptive -m message, and target restores by explicit stash@{N} rather than assuming the top of the stack.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Working tree & stash state
!git status --short 2>/dev/null
!git stash list 2>/dev/null | head -20
!git branch --show-current 2>/dev/null
Instructions
Help the user shelve or restore work with git stash based on $ARGUMENTS. Stashing touches uncommitted work, so default to the non-destructive option and confirm before anything that can discard changes (drop, clear, or a conflicting pop).
Method
- Read the intent. Common cases: save current changes to switch context, restore (pop/apply) a previous stash, inspect what's in a stash, or clean up old stashes. If
$ARGUMENTSis empty and there are local changes, assume they want to save; if the tree is clean and stashes exist, assume they want to restore. - When saving:
- Use a descriptive message:
git stash push -m "<what this is>"so the entry is identifiable later — never an anonymous stash when several may pile up. - Include untracked files only when needed (
-u/--include-untracked); warn that-a/--allalso stashes ignored files and is rarely wanted. - To stash only some files, use a pathspec (
git stash push -m "..." -- path/...) or--keep-indexto keep staged changes in the tree.
- Use a descriptive message:
- When restoring:
- Prefer
git stash apply <ref>overpopwhen unsure —applykeeps the stash so a botched restore is recoverable;popdeletes it on success. Reach forpoponly once the right stash is confirmed. - Identify the target explicitly (
stash@{N}) rather than assuming the top of the stack, especially whengit stash listshows several. - If applying may conflict (the branch moved on), say so first; on conflict, resolve like a merge (see the
resolve-conflictsskill) — and note that a failedpopleaves the stash intact.
- Prefer
- When inspecting:
git stash show -p stash@{N}shows the diff; list withgit stash listand map each entry to its branch/message before acting. - When cleaning up: confirm exactly which entries before
git stash drop stash@{N}. Treatgit stash clearas destructive — it removes all stashes and is not part of normal undo. Always confirm explicitly, and mention entries linger in the reflog briefly if recovery is needed.
Rules
- Default to non-destructive actions:
applyoverpop, named saves over anonymous, and neverdrop/clearwithout explicit confirmation of which entries are affected. - Always give saved stashes a descriptive
-mmessage, and target restores by explicitstash@{N}rather than assuming the top of the stack. - Warn before restoring onto a tree that has moved on (conflicts likely) and before stashing untracked/ignored files unless the user asked.
- A stash is not a backup — surface that dropped/cleared stashes are only briefly recoverable via the reflog, and prefer a commit for anything that must not be lost.
- End by showing the resulting
git status --shortandgit stash listso the user can see exactly what was saved or restored.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

