study-depslisted

# Study Dependencies Clone and study your project's dependencies at their exact pinned versions using git worktrees under `~/study/`. Use `$ARGUMENTS` as the user's filter. If `$ARGUMENTS` is empty, ask the user which dependency to study. Parse `$ARGUMENTS` for flags and strip them from the filter text: | Flag | Effect | |------|--------| | `--lang <language>` | Override auto-detected language directory | | `--no-worktree` | Clone only, skip worktree creation | The remaining text after stripping flags is the **filter** — a package name, `"all"`, or a category like `"dev"` or `"build"`. ## Step 1: Detect Preferred Tools ```bash for tool in rg ag fd jq; do command -v "$tool" >/dev/null 2>&1 && echo "$tool:available" || echo "$tool:missing" done ``` For content search, prefer `rg` over `ag` over `grep`. For file finding, prefer `fd` over `find`. For JSON parsing, use `jq` when available, otherwise parse manually. ## Step 2: Scan Manifest Files Search the current project root for manifest files and extract dependencies with their version constraints. | Manifest | Language dir | Lockfiles | Extraction method | |----------|-------------|-----------|-------------------| | `package.json` | `typescript` | `package-lock.json`, `pnpm-lock.yaml`, `yarn.lock`, `bun.lock` | `dependencies`, `devDependencies`, `peerDependencies` fields | | `pyproject.toml` | `python` | `uv.lock`, `poetry.lock`, `requirements.txt` | `[project]` `dependencies`, `[tool.poetry.dependencies]` | | `Ca