dev-setup 1.0.0__tar.gz → 1.2.0__tar.gz

dev_setup-1.2.0/.claude/settings.local.json

@@ -0,0 +1,9 @@
+{
+  "permissions": {
+    "allow": [
+      "Bash(uv run *)",
+      "Bash(docker build *)",
+      "Bash(git -C /home/sawyer/Documents/Projects/ClaudeProjects/dev-setup-py log --format=\"%H %ai %s\")"
+    ]
+  }
+}

dev_setup-1.2.0/CHANGELOG.md

@@ -0,0 +1,42 @@
+## v1.2.0 (2026-06-19)
+
+### Feat
+
+- add docker-compose.yml to dev/ sandbox
+- add dev/ sandbox with Dockerfile for local install testing
+- add docs command to open tool documentation in the browser
+- add Go, Java, and Ruby builtin tools under languages category
+- add gh, mkcert, ollama, and pi-coding-agent builtin tools
+- add --verbose/-v flag to stream install/remove output
+
+### Docs
+
+- add Prerequisites section to README
+
+### Chore
+
+- add commitizen dev dep and unify version source
+
+## v1.1.0 (2026-06-18)
+
+### Feat
+
+- add aws-cli and saml2aws built-in packages
+- add bash type for multi-step custom installs
+- add help_cmd field to all tools, display in list output
+- enhance project metadata in pyproject.toml
+
+### Refactor
+
+- improve maintainability and extensibility for new tool additions
+- switch from uv-run to pip/pipx install pattern
+
+### Docs
+
+- add comprehensive README
+
+## v1.0.0 (2026-06-17)
+
+### Feat
+
+- initial Python implementation of dev-setup CLI

{dev_setup-1.0.0 → dev_setup-1.2.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: dev-setup
-Version: 1.0.0
+Version: 1.2.0
 Summary: Development environment setup CLI for Linux
 Project-URL: Repository, https://github.com/thesawdawg/dev-setup-py
 Author-email: Sawyer <sawyerksu@gmail.com>
@@ -30,29 +30,78 @@ A Python-based CLI for managing your Linux development environment. Install, rem
 
 ---
 
-## How it works
+## Prerequisites
+
+| Requirement | Notes |
+|-------------|-------|
+| **OS** | Ubuntu 20.04+ or Debian 11+ (amd64) |
+| **Python** | 3.11 or later |
+| **curl** | Used by script-based installers (Docker, NVM, uv, etc.) |
+| **sudo** | Required for tools that write to system paths (`/usr/local/bin`, apt packages) |
+| **ca-certificates** | For HTTPS downloads — present on most systems by default |
 
-The entry point is a thin bash wrapper (`./dev-setup`) that bootstraps Python automatically:
+These are available on any standard Ubuntu/Debian install. On a fresh minimal image, run:
+
+```bash
+sudo apt-get install -y python3 python3-pip curl ca-certificates sudo
+```
 
-1. Checks for `uv` on `PATH`; installs it via the official installer if missing
-2. Runs `uv run --project <dir> python -m dev_setup` — uv provisions Python 3.11+ if needed
-3. All further logic (commands, UI, installs) is pure Python
+**Optional** — only needed when using specific install types:
 
-You never need to manually install Python or manage a virtualenv. The first invocation after a fresh clone may take a few seconds to resolve dependencies; every run after that is instant.
+| Requirement | When |
+|-------------|------|
+| `git` | `git`-type custom packages (`dev-setup add` → git) |
+| `node` / `npm` | `npm`-type custom packages |
+| `uv` | Running from source via `./dev-setup` (auto-installed if missing) |
 
 ---
 
 ## Installation
 
+### From PyPI (recommended)
+
+The simplest install — no git clone required, Python 3.11+ is the only prerequisite:
+
+```bash
+# pipx gives the tool its own isolated environment (preferred)
+pipx install dev-setup
+
+# or plain pip
+pip install dev-setup
+```
+
+After install, `dev-setup` is available as a command. Run `dev-setup --help` to verify.
+
+### From source (development)
+
 ```bash
 git clone <repo-url> ~/dev-setup-py
 cd ~/dev-setup-py
-bash install.sh
+bash install.sh   # installs from PyPI via pipx or pip
 ```
 
-`install.sh` creates a symlink at `~/.local/bin/dev-setup` and ensures `~/.local/bin` is on `PATH` in `~/.bashrc`. Open a new terminal (or run `source ~/.bashrc`) and you're done.
+Or to run directly from the cloned repo without installing:
+
+```bash
+./dev-setup list   # creates a .venv on first run, then stays fast
+```
 
-> **Note:** Installing this tool symlinks `~/.local/bin/dev-setup`, which will replace an existing bash `dev-setup` at that path if you have one.
+The `./dev-setup` bash script requires Python 3.11+ and creates a local `.venv` automatically. On Debian/Ubuntu, if `python3-venv` is not installed, it falls back to `uv venv` if uv is available.
+
+For editable development installs:
+
+```bash
+pip install -e .
+dev-setup list
+```
+
+---
+
+## How it works
+
+When installed from PyPI (via `pip` or `pipx`), the `dev-setup` command is a standard Python entry point — Python is the only runtime dependency. The `[project.scripts]` entry in `pyproject.toml` maps `dev-setup` directly to `dev_setup.__main__:main`.
+
+The bash `./dev-setup` script in the repo is a convenience runner for the git-clone workflow. It creates a `.venv` using `python3 -m venv` (falling back to `uv venv` on systems where `python3-venv` is a separate package) and installs the project in editable mode on first run.
 
 ---
 
@@ -338,17 +387,6 @@ class MyTool(Tool):
 
 ---
 
-## Requirements
-
-- Debian/Ubuntu Linux (apt-based; htop and php fall back to yum/dnf/pacman for detection)
-- `curl` (for bootstrapping uv and install scripts)
-- `git` (for `git`-type custom packages)
-- `sudo` access (Docker, PHP, saml2aws, htop installs write to system paths)
-
-Python 3.11+ is provisioned automatically by uv if not already present.
-
----
-
 ## Dependencies
 
 | Package | Version | Purpose |

{dev_setup-1.0.0 → dev_setup-1.2.0}/README.md

@@ -4,29 +4,78 @@ A Python-based CLI for managing your Linux development environment. Install, rem
 
 ---
 
-## How it works
+## Prerequisites
+
+| Requirement | Notes |
+|-------------|-------|
+| **OS** | Ubuntu 20.04+ or Debian 11+ (amd64) |
+| **Python** | 3.11 or later |
+| **curl** | Used by script-based installers (Docker, NVM, uv, etc.) |
+| **sudo** | Required for tools that write to system paths (`/usr/local/bin`, apt packages) |
+| **ca-certificates** | For HTTPS downloads — present on most systems by default |
 
-The entry point is a thin bash wrapper (`./dev-setup`) that bootstraps Python automatically:
+These are available on any standard Ubuntu/Debian install. On a fresh minimal image, run:
+
+```bash
+sudo apt-get install -y python3 python3-pip curl ca-certificates sudo
+```
 
-1. Checks for `uv` on `PATH`; installs it via the official installer if missing
-2. Runs `uv run --project <dir> python -m dev_setup` — uv provisions Python 3.11+ if needed
-3. All further logic (commands, UI, installs) is pure Python
+**Optional** — only needed when using specific install types:
 
-You never need to manually install Python or manage a virtualenv. The first invocation after a fresh clone may take a few seconds to resolve dependencies; every run after that is instant.
+| Requirement | When |
+|-------------|------|
+| `git` | `git`-type custom packages (`dev-setup add` → git) |
+| `node` / `npm` | `npm`-type custom packages |
+| `uv` | Running from source via `./dev-setup` (auto-installed if missing) |
 
 ---
 
 ## Installation
 
+### From PyPI (recommended)
+
+The simplest install — no git clone required, Python 3.11+ is the only prerequisite:
+
+```bash
+# pipx gives the tool its own isolated environment (preferred)
+pipx install dev-setup
+
+# or plain pip
+pip install dev-setup
+```
+
+After install, `dev-setup` is available as a command. Run `dev-setup --help` to verify.
+
+### From source (development)
+
 ```bash
 git clone <repo-url> ~/dev-setup-py
 cd ~/dev-setup-py
-bash install.sh
+bash install.sh   # installs from PyPI via pipx or pip
 ```
 
-`install.sh` creates a symlink at `~/.local/bin/dev-setup` and ensures `~/.local/bin` is on `PATH` in `~/.bashrc`. Open a new terminal (or run `source ~/.bashrc`) and you're done.
+Or to run directly from the cloned repo without installing:
+
+```bash
+./dev-setup list   # creates a .venv on first run, then stays fast
+```
 
-> **Note:** Installing this tool symlinks `~/.local/bin/dev-setup`, which will replace an existing bash `dev-setup` at that path if you have one.
+The `./dev-setup` bash script requires Python 3.11+ and creates a local `.venv` automatically. On Debian/Ubuntu, if `python3-venv` is not installed, it falls back to `uv venv` if uv is available.
+
+For editable development installs:
+
+```bash
+pip install -e .
+dev-setup list
+```
+
+---
+
+## How it works
+
+When installed from PyPI (via `pip` or `pipx`), the `dev-setup` command is a standard Python entry point — Python is the only runtime dependency. The `[project.scripts]` entry in `pyproject.toml` maps `dev-setup` directly to `dev_setup.__main__:main`.
+
+The bash `./dev-setup` script in the repo is a convenience runner for the git-clone workflow. It creates a `.venv` using `python3 -m venv` (falling back to `uv venv` on systems where `python3-venv` is a separate package) and installs the project in editable mode on first run.
 
 ---
 
@@ -312,17 +361,6 @@ class MyTool(Tool):
 
 ---
 
-## Requirements
-
-- Debian/Ubuntu Linux (apt-based; htop and php fall back to yum/dnf/pacman for detection)
-- `curl` (for bootstrapping uv and install scripts)
-- `git` (for `git`-type custom packages)
-- `sudo` access (Docker, PHP, saml2aws, htop installs write to system paths)
-
-Python 3.11+ is provisioned automatically by uv if not already present.
-
----
-
 ## Dependencies
 
 | Package | Version | Purpose |

dev_setup-1.2.0/app-design-output/recommendations.md

@@ -0,0 +1,100 @@
+# dev-setup — Maintainability Review
+
+_Generated 2026-06-18_
+
+## Goal
+Lower the cost of adding new tools to the core PyPI package build.
+
+---
+
+## Findings
+
+### 1. Builtin boilerplate: every package file duplicates the same `is_installed` / `get_version` logic [HIGH]
+
+Seven of eight builtin package files implement the same two-liner:
+```python
+def is_installed(self) -> bool:
+    return shutil.which(self.key) is not None
+
+def get_version(self) -> str:
+    r = subprocess.run([self.key, "--version"], capture_output=True, text=True)
+    return r.stdout.strip().splitlines()[0] if r.returncode == 0 else ""
+```
+Adding a new tool means copy-pasting this pattern. Errors diverge silently (`aws_cli` and `saml2aws` check `stderr` fallback; `docker` skips `splitlines()`).
+
+**Fix:** Add `WhichTool(Tool)` to `base.py` — a shared mixin that provides these two methods. Each builtin that passes `shutil.which` inherits from `WhichTool` instead of `Tool` and only overrides what's truly unique (install/remove logic). `NvmTool` keeps its own `is_installed()` since it checks a file path, not `which`.
+
+**Effort:** Low. Touches 7 files, each loses 8–12 lines.
+
+---
+
+### 2. Hardcoded category list in `list_cmd.py` silently drops new tools [HIGH]
+
+`list_cmd.py:34` iterates `("core", "tools", "custom")`. A builtin with any other `category` value is collected into `by_cat` but never rendered. Verified: a tool with `category = "cloud"` is invisible to `dev-setup list`.
+
+**Fix:** Derive iteration order dynamically using a priority dict — `core=0`, `custom=999`, all others sorted by name in between.
+
+**Effort:** 4-line change.
+
+---
+
+### 3. `add_cmd` and `delete_cmd` mutate private registry state directly [MEDIUM]
+
+`add_cmd.py:120-123` and `delete_cmd.py:39-42` both reach into `registry._registry` and `registry._order` directly. Any internal registry refactor (e.g., ordering strategy change) silently breaks these commands.
+
+**Fix:** Add public `register(tool)` and `deregister(key)` functions to `registry.py`. Commands use those; internals stay internal.
+
+**Effort:** Low.
+
+---
+
+### 4. Version is defined in two places and is out of sync [MEDIUM]
+
+`src/dev_setup/__init__.py` says `1.0.0`; `pyproject.toml` says `1.1.0`. Additionally, `ui.py:64` hardcodes the string `"v1.0.0"` in `print_banner()`.
+
+**Fix:** Single source of truth: update `__init__.py` to `1.1.0`, and have `print_banner()` read from `from dev_setup import __version__`.
+
+_Note: for a fully automated solution, `pyproject.toml` can be set to `dynamic = ["version"]` with `[tool.hatch.version] path = "src/dev_setup/__init__.py"`, eliminating the need to update two files on release. That's a separate change._
+
+**Effort:** 2 lines.
+
+---
+
+### 5. `CUSTOM_DIR` / `_CUSTOM_DIR` duplicated in `generic.py` [LOW]
+
+`generic.py` exports both `CUSTOM_DIR` and `_CUSTOM_DIR` (identical). `registry.py` imports the underscore form. This is confusing — two names for the same path.
+
+**Fix:** Remove `_CUSTOM_DIR`, update `registry.py` to import `CUSTOM_DIR`.
+
+---
+
+### 6. `import shutil as _shutil` inside `GenericTool.remove()` shadows a top-level import [LOW]
+
+`generic.py` imports `shutil` at the top of the file, then re-imports it as `_shutil` inside the `git` branch of `remove()`. The local shadowing is unnecessary.
+
+**Fix:** Use the module-level `shutil` directly.
+
+---
+
+## What "adding a new builtin" looks like after fixes
+
+Before (current): ~50 lines per file including copy-pasted `is_installed`, `get_version`, and `shutil`/`subprocess` imports.
+
+After: ~30 lines. A simple tool like `htop` becomes:
+```python
+class HtopTool(WhichTool):
+    key = "htop"
+    name = "htop"
+    description = "Interactive process and resource monitor"
+    category = "tools"
+    install_type = "apt"
+    help_cmd = "man htop"
+
+    def install(self) -> Optional[str]:
+        ...  # only the unique install logic
+
+    def remove(self) -> None:
+        ...  # only the unique remove logic
+```
+
+New tools with unusual categories won't vanish from `list`. New categories appear automatically without touching `list_cmd.py`.

dev_setup-1.2.0/dev/Dockerfile

@@ -0,0 +1,38 @@
+FROM ubuntu:24.04
+
+ENV DEBIAN_FRONTEND=noninteractive \
+    TZ=UTC \
+    LANG=C.UTF-8
+
+# System packages needed to bootstrap dev-setup and run its installers
+RUN apt-get update && apt-get install -y --no-install-recommends \
+    python3.12 \
+    python3.12-venv \
+    python3-pip \
+    curl \
+    git \
+    sudo \
+    ca-certificates \
+    gnupg \
+    lsb-release \
+    && rm -rf /var/lib/apt/lists/*
+
+# Non-root user with passwordless sudo — mirrors a real developer workstation
+RUN useradd -m -s /bin/bash developer \
+    && echo "developer ALL=(ALL) NOPASSWD:ALL" >> /etc/sudoers
+
+USER developer
+WORKDIR /home/developer
+
+# Install the pre-built wheel (built by 'make build' before docker build runs)
+COPY --chown=developer:developer dist/dev_setup-*.whl /tmp/
+
+RUN pip install --user --break-system-packages /tmp/dev_setup-*.whl \
+    && rm /tmp/dev_setup-*.whl
+
+ENV PATH="/home/developer/.local/bin:$PATH"
+
+# Pre-create config dir so the tool has somewhere to write on first run
+RUN mkdir -p /home/developer/.config/dev-setup/packages
+
+CMD ["/bin/bash", "--login"]

dev_setup-1.2.0/dev/Makefile

@@ -0,0 +1,19 @@
+ROOT := ..
+
+.PHONY: build run shell clean
+
+# Build a fresh wheel from source, then build the Docker image.
+# Clean dist first so the glob in the Dockerfile matches exactly one file.
+build:
+	cd $(ROOT) && rm -f dist/*.whl dist/*.tar.gz && uv build
+	docker compose build
+
+# Drop into an interactive shell as the 'developer' user
+run: build
+	docker compose run --rm sandbox
+
+shell: run
+
+# Remove the built image and named volume
+clean:
+	docker compose down --rmi local --volumes 2>/dev/null || true

dev_setup-1.2.0/dev/docker-compose.yml

@@ -0,0 +1,14 @@
+services:
+  sandbox:
+    build:
+      context: ..
+      dockerfile: dev/Dockerfile
+    image: dev-setup-sandbox
+    stdin_open: true
+    tty: true
+    volumes:
+      # Persist custom packages added via 'dev-setup add' across container runs
+      - dev-setup-config:/home/developer/.config/dev-setup
+
+volumes:
+  dev-setup-config:

dev_setup-1.2.0/dev-setup

@@ -0,0 +1,66 @@
+#!/usr/bin/env bash
+# Local runner for development / git-clone installs.
+# For production: pip install dev-setup  or  pipx install dev-setup
+set -euo pipefail
+
+DEVSETUP_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+VENV="$DEVSETUP_DIR/.venv"
+
+# Common locations where pip/pipx/uv install binaries
+export PATH="$HOME/.local/bin:$HOME/.cargo/bin:$PATH"
+
+_find_python() {
+    local py
+    for py in python3.13 python3.12 python3.11 python3; do
+        if command -v "$py" &>/dev/null; then
+            if "$py" -c "import sys; exit(0 if sys.version_info >= (3,11) else 1)" 2>/dev/null; then
+                echo "$py"
+                return 0
+            fi
+        fi
+    done
+    echo "  ✖ Python 3.11+ is required." >&2
+    echo "    Install from https://www.python.org/downloads/ or via your package manager." >&2
+    exit 1
+}
+
+_setup_venv() {
+    local python="$1"
+    echo "  ❯ Creating virtual environment..."
+
+    if "$python" -m venv "$VENV" &>/dev/null; then
+        "$VENV/bin/pip" install --quiet -e "$DEVSETUP_DIR"
+        echo "  ✔ Ready"
+        return 0
+    fi
+
+    # python3 -m venv may leave a partial directory behind on failure — clean it up
+    rm -rf "$VENV"
+
+    # Debian/Ubuntu ships python3 without python3-venv by default.
+    # uv can create venvs with a bundled pip, bypassing ensurepip entirely.
+    if command -v uv &>/dev/null; then
+        echo "  ❯ python3-venv unavailable — falling back to uv venv..."
+        uv venv "$VENV" --quiet
+        VIRTUAL_ENV="$VENV" uv pip install -e "$DEVSETUP_DIR" --quiet
+        echo "  ✔ Ready"
+        return 0
+    fi
+
+    echo "  ✖ Could not create virtual environment." >&2
+    echo "" >&2
+    echo "  On Debian/Ubuntu, install the missing package:" >&2
+    echo "    sudo apt install python3-venv" >&2
+    echo "" >&2
+    echo "  Or install the tool directly (no venv needed):" >&2
+    echo "    pip install dev-setup   or   pipx install dev-setup" >&2
+    exit 1
+}
+
+PYTHON=$(_find_python)
+
+if [ ! -f "$VENV/bin/python" ] || ! "$VENV/bin/python" -c "import dev_setup" 2>/dev/null; then
+    _setup_venv "$PYTHON"
+fi
+
+exec "$VENV/bin/python" -m dev_setup "$@"

dev_setup-1.2.0/install.sh

@@ -0,0 +1,67 @@
+#!/usr/bin/env bash
+# Installs dev-setup from PyPI using pipx (preferred) or pip.
+set -euo pipefail
+
+PACKAGE="dev-setup"
+
+_find_python() {
+    local py
+    for py in python3.13 python3.12 python3.11 python3; do
+        if command -v "$py" &>/dev/null; then
+            if "$py" -c "import sys; exit(0 if sys.version_info >= (3,11) else 1)" 2>/dev/null; then
+                echo "$py"
+                return 0
+            fi
+        fi
+    done
+    echo "  ✖ Python 3.11+ is required." >&2
+    echo "    Install from https://www.python.org/downloads/ or via your package manager." >&2
+    exit 1
+}
+
+_ensure_local_bin_on_path() {
+    local dir="$HOME/.local/bin"
+    local bashrc="$HOME/.bashrc"
+    if ! grep -qF '.local/bin' "$bashrc" 2>/dev/null; then
+        printf '\n# dev-setup\nexport PATH="%s:$PATH"\n' "$dir" >> "$bashrc"
+        echo "  ✔ Added $dir to PATH in $bashrc"
+        NEED_RELOAD=1
+    fi
+}
+
+PYTHON=$(_find_python)
+NEED_RELOAD=0
+echo "  ✔ Python: $($PYTHON --version)"
+
+# --- pipx path (preferred: isolated env, clean uninstall) ---
+if command -v pipx &>/dev/null || "$PYTHON" -m pipx --version &>/dev/null 2>&1; then
+    PIPX=$(command -v pipx 2>/dev/null || echo "$PYTHON -m pipx")
+    echo "  ❯ Installing $PACKAGE via pipx..."
+    $PIPX install "$PACKAGE"
+    echo ""
+    echo "  ✔ Done. Run: dev-setup --help"
+    exit 0
+fi
+
+# --- bootstrap pipx then use it ---
+if "$PYTHON" -m pip --version &>/dev/null 2>&1; then
+    echo "  ❯ pipx not found — installing pipx first..."
+    "$PYTHON" -m pip install --user pipx --quiet
+    "$PYTHON" -m pipx ensurepath --quiet 2>/dev/null || true
+    _ensure_local_bin_on_path
+
+    echo "  ❯ Installing $PACKAGE via pipx..."
+    "$PYTHON" -m pipx install "$PACKAGE"
+    echo ""
+    echo "  ✔ Done. Run: dev-setup --help"
+    [ "$NEED_RELOAD" -eq 1 ] && echo "    (run 'source ~/.bashrc' first if the command isn't found)"
+    exit 0
+fi
+
+# --- last resort: pip --user ---
+echo "  ❯ Installing $PACKAGE via pip..."
+"$PYTHON" -m pip install --user "$PACKAGE" --quiet
+_ensure_local_bin_on_path
+echo ""
+echo "  ✔ Done. Run: dev-setup --help"
+[ "$NEED_RELOAD" -eq 1 ] && echo "    (run 'source ~/.bashrc' first if the command isn't found)"

{dev_setup-1.0.0 → dev_setup-1.2.0}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "dev-setup"
-version = "1.0.0"
+version = "1.2.0"
 description = "Development environment setup CLI for Linux"
 readme = "README.md"
 requires-python = ">=3.11"
@@ -42,5 +42,13 @@ build-backend = "hatchling.build"
 [tool.hatch.build.targets.wheel]
 packages = ["src/dev_setup"]
 
-[tool.uv]
-package = true
+[dependency-groups]
+dev = [
+    "commitizen>=3.0",
+]
+
+[tool.commitizen]
+name = "cz_conventional_commits"
+version_provider = "pep621"
+tag_format = "v$version"
+update_changelog_on_bump = true

dev_setup-1.2.0/src/dev_setup/__init__.py

@@ -0,0 +1,6 @@
+from importlib.metadata import version, PackageNotFoundError
+
+try:
+    __version__ = version("dev-setup")
+except PackageNotFoundError:
+    __version__ = "dev"

{dev_setup-1.0.0 → dev_setup-1.2.0}/src/dev_setup/base.py

@@ -1,5 +1,6 @@
 from __future__ import annotations
 
+import shutil
 import subprocess
 from abc import ABC, abstractmethod
 from pathlib import Path
@@ -14,6 +15,7 @@ class Tool(ABC):
     install_type: str = "unknown"
     builtin: bool = True
     help_cmd: str = ""
+    docs_url: str = ""
 
     @abstractmethod
     def is_installed(self) -> bool: ...
@@ -32,6 +34,22 @@ class Tool(ABC):
         return ""
 
 
+class WhichTool(Tool):
+    """Base for tools whose presence is detected via PATH lookup (shutil.which)."""
+
+    def is_installed(self) -> bool:
+        return shutil.which(self.key) is not None
+
+    def get_version(self) -> str:
+        if not shutil.which(self.key):
+            return ""
+        r = subprocess.run([self.key, "--version"], capture_output=True, text=True)
+        if r.returncode != 0:
+            return ""
+        out = r.stdout.strip() or r.stderr.strip()
+        return out.splitlines()[0] if out else ""
+
+
 def run_bash(cmd: str, **kwargs) -> subprocess.CompletedProcess:
     return subprocess.run(["bash", "-c", cmd], **kwargs)
 

{dev_setup-1.0.0 → dev_setup-1.2.0}/src/dev_setup/cli.py

@@ -25,6 +25,7 @@ def _register_commands() -> None:
     from dev_setup.commands.remove_cmd import remove_cmd
     from dev_setup.commands.add_cmd import add_cmd
     from dev_setup.commands.delete_cmd import delete_cmd
+    from dev_setup.commands.docs_cmd import docs_cmd
 
     cli.add_command(list_cmd, "list")
     cli.add_command(install_cmd, "install")
@@ -33,6 +34,7 @@ def _register_commands() -> None:
     cli.add_command(add_cmd, "add")
     cli.add_command(delete_cmd, "delete")
     cli.add_command(delete_cmd, "rm")
+    cli.add_command(docs_cmd, "docs")
 
 
 _register_commands()