Centralized troubleshooting runbook for recurring workspace/tool failures (npm install/test errors, Windows file locks, branch/state mismatches, unexpected external file changes, CI/validation confusion, flaky local E2E). Use when commands fail, installs break, permissions/EPERM/EBUSY errors occur, behavior differs from expectation, or a systematic triage process is needed.
This skill is the centralized location for cross-repo troubleshooting knowledge.
Goal:
git status --porcelain and git diff --name-only if changes are involvedreferences/* and link them from this file.If npm install/ci fails on Windows with EPERM/EBUSY and locked native modules:
If you see “external changes” (formatter/user/tool edits) and need to decide whether to pause:
If the user reports missing changes or your view doesn’t match theirs:
If failures might be caused by persistent shell cwd drift:
When you discover a reusable troubleshooting tip, propose it in this format (staged repo-locally):