How to safely stash changes in a parent repo containing dirty nested git repositories
Scanned 9/9/2026
Install to Claude Code
npx -y skills add vamseeachanta/workspace-hub --skill nested-git-repo-stash-safety --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Nested Git Repo Stash Safety?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/vamseeachanta-nested-git-repo-stash-safety-workspace-hub)More formats (shields.io, HTML) on the badges page.
---
name: nested-git-repo-stash-safety
description: How to safely stash changes in a parent repo containing dirty nested git repositories
version: 1.0.0
source: auto-extracted
extracted: 2026-04-10
metadata:
tags: ["git", "submodules", "nested-repos", "stash", "workflow"]
---
# Nested Git Repo Stash Safety
When a parent repo contains a nested git repository (gitlink pointer), `git stash` in the parent only captures the SHA pointer to the nested repo, not the nested repo's actual working-tree changes. Modified files inside the nested repo are invisible to the parent's stash and will survive or be left behind unpredictably. Always manually snapshot or stash changes inside nested repos separately before performing parent-repo operations. Use `git status` to detect `m` (modified gitlink) entries indicating a dirty nested repo state.Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Designs system architecture, component specifications, and technical integration strategy. Use when: designing solutions, system architecture, technology stack, or integration approaches.