fix: using-git-worktrees skill runs for all pyproject.toml projects, breaking non-Poetry setups

[kuishou68]

Bug Report

Description

In skills/using-git-worktrees/SKILL.md, the auto-detected Python project setup step is:

if [ -f pyproject.toml ]; then poetry install; fi

This unconditionally runs poetry install for any project containing pyproject.toml, even when the project uses uv, pip, hatch, pdm, or plain setuptools. The vast majority of modern Python projects use pyproject.toml without Poetry.

Impact

• Running poetry install on a non-Poetry project fails (Poetry rejects the file or installs incorrectly).
• On machines without Poetry installed it errors out entirely.
• This silently breaks the "clean baseline" step that the worktrees skill relies on.

Expected Behaviour

The skill should detect the actual package manager by inspecting pyproject.toml content (look for [tool.poetry]) or by checking for lock files (poetry.lock, uv.lock, etc.) before choosing the install command.

Suggested Fix

# Python - detect package manager
if [ -f pyproject.toml ]; then
  if grep -q '\[tool\.poetry\]' pyproject.toml 2>/dev/null; then
    poetry install
  elif [ -f uv.lock ]; then
    uv sync
  elif [ -f requirements.txt ]; then
    pip install -r requirements.txt
  else
    pip install -e .
  fi
elif [ -f requirements.txt ]; then
  pip install -r requirements.txt
fi

Affected File

skills/using-git-worktrees/SKILL.md, "Run Project Setup" section

[kuishou68]

I've opened PR #1109 to fix this issue. The updated 'Run Project Setup' section now inspects pyproject.toml for [tool.poetry] and checks for a uv.lock file before deciding which install command to run, so Poetry is only invoked for actual Poetry projects. #1109

[Bortlesboat]

I confirmed this is still present on current main in a local checkout (917e5f5). The Run Project Setup section in skills/using-git-worktrees/SKILL.md still contains:

if [ -f requirements.txt ]; then pip install -r requirements.txt; fi
if [ -f pyproject.toml ]; then poetry install; fi

That means any worktree session on a non-Poetry Python project with a pyproject.toml gets steered into poetry install, which is the wrong setup path for uv, hatch, pdm, plain setuptools, etc. On machines without Poetry installed it also fails immediately.

I like that this issue is scoped to one specific snippet in using-git-worktrees, rather than being a broad workflow complaint. That makes it a good candidate for a narrow fix instead of a larger redesign.