Diagnose and recover from stale git lock files in multi-repo workspaces, especially with submodules
Scanned 9/9/2026
Install to Claude Code
npx -y skills add vamseeachanta/workspace-hub --skill multi-repo-stale-lock-recovery --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Multi Repo Stale Lock Recovery?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/vamseeachanta-multi-repo-stale-lock-recovery)More formats (shields.io, HTML) on the badges page.
---
name: multi-repo-stale-lock-recovery
description: Diagnose and recover from stale git lock files in multi-repo workspaces, especially with submodules
version: 1.0.0
source: auto-extracted
extracted: 2026-04-11
metadata:
tags: ["git", "multi-repo", "debugging", "stale-locks"]
---
# Multi-Repo Stale Lock Recovery
When bulk operations fail across multiple repos with `.git/index.lock` errors, check for stale crashes from background processes (especially with submodules). Use `lsof` to verify no git process is actually running, then safely remove the lock file and retry. If the lock reappears immediately after cleanup, a background process may still be running — wait briefly and monitor with `ps` before retrying. In submodule-heavy workspaces, lock files in one repo can reference another's submodule path.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!
Ultra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. Use when user says "write a commit", "commit message", "generate commit", "/commit", or invokes /caveman-commit. Auto-triggers when staging changes.