/update-all

You can refresh npm global packages and uv-installed tools simultaneously by running an update-all hook script that scans your mixed toolchain environments and returns an automated status summary of what changed and what failed.

To repair a broken Python venv, the update process runs uv pip checks to detect failing installs or missing dist-infos, then repairs missing transitive dependencies automatically after common upgrade patterns break the environment.

Yes, you can update git submodules and npm project dependencies together by executing a multi-layer dependency update routine that fetches remote submodule updates and refreshes npm project packages in a single workspace maintenance pass.

No, the update-all script explicitly excludes Claude plugin installs and MCP server refresh, requiring manual restart for those servers, while also skipping specifically pinned projects that need a dedicated check and update script.

The best way to maintain a mixed-toolchain workspace is running an automated update-all routine that refreshes npm globals, uv tools, Python venv tooling, npm dependencies, and git submodules, then generates a report of skipped and failed items.

uv pip check fails after updating Python tool venvs because common upgrade patterns leave broken dist-infos or missing transitive dependencies, which the update-all process detects and repairs by scanning pyproject.toml files in registered tool directories.