Diagnose and recover from stale git lock files caused by crashed background processes
Scanned 9/9/2026
Install to Claude Code
Skills Directorynpx -y skills add vamseeachanta/workspace-hub --skill recover-from-stale-git-locks --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Recover From Stale Git Locks?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/vamseeachanta-recover-from-stale-git-locks)More formats (shields.io, HTML) on the badges page.
---
name: recover-from-stale-git-locks
description: Diagnose and recover from stale git lock files caused by crashed background processes
version: 1.0.0
source: auto-extracted
extracted: 2026-04-11
metadata:
tags: ["git", "debugging", "automation", "recovery"]
---
# Recover from Stale Git Locks
When git operations fail with `.git/index.lock` errors, the lock file may persist after a crash. Check if any git process is actually running with `ps aux | grep git`. If none exist, safely remove the stale lock file with `rm .git/index.lock`, then retry the operation. For submodules or nested repos, check and clean locks in each `.git` directory. Always verify the background process completed before proceeding.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.
