devstuff 1.13.1__tar.gz

devstuff-1.13.1/.claude/skills/run-stuff/SKILL.md

@@ -0,0 +1,65 @@
+---
+name: run-stuff
+description: Run, build, test, and smoke-test the dev-setup CLI; exercise list/catalog/install commands
+---
+
+`dev-setup` is a Python CLI that manages a Linux dev environment. It is driven directly via `uv run dev-setup <command>` — no GUI, no server, no browser. The smoke script at `.claude/skills/run-stuff/smoke.sh` is the primary agent harness.
+
+## Prerequisites
+
+- Python 3.11+
+- `uv` (installed at `~/.local/bin/uv`)
+
+Install the package in editable mode once:
+
+```bash
+uv pip install -e .
+```
+
+## Run (agent path)
+
+Run the smoke script from the repo root:
+
+```bash
+bash .claude/skills/run-stuff/smoke.sh
+```
+
+It exercises `version`, `list` (all variants), `catalog path`, `catalog export`, and `--help`. Exits 0 on success, 1 on any failure.
+
+To exercise a specific command directly:
+
+```bash
+uv run dev-setup version
+uv run dev-setup list
+uv run dev-setup list core
+uv run dev-setup list --installed
+uv run dev-setup list --available
+uv run dev-setup catalog path
+uv run dev-setup catalog export /tmp/export.yaml
+uv run dev-setup --help
+```
+
+Interactive commands (`install`, `remove`, `add`, `delete`) require a TTY and are not smoke-testable without mocking. To test them, run the app directly in a terminal.
+
+## Run (human path)
+
+```bash
+./dev-setup list        # bash wrapper — bootstraps .venv on first run
+./dev-setup install     # interactive multi-select picker
+```
+
+## Test suite
+
+```bash
+uv run pytest           # unit tests only (integration tests skipped by default)
+uv run pytest -m integration   # real installs — requires sudo + network
+```
+
+All 6 unit tests pass in ~0.3s.
+
+## Gotchas
+
+- `dev-setup` is not on `$PATH` directly in the dev environment — `uv run dev-setup` is the reliable invocation path. The `./dev-setup` bash wrapper also works from repo root and bootstraps its own `.venv`.
+- `pip` is not available in this environment; `uv pip install` is the substitute.
+- Interactive commands (`install`, `add`) open questionary/click prompts that hang in non-TTY shells. Pipe input only if you know the exact prompt sequence.
+- `catalog export` writes to a path argument; without an argument it prints to stdout. Check the README for the exact signature.

devstuff-1.13.1/.claude/skills/run-stuff/smoke.sh

@@ -0,0 +1,55 @@
+#!/usr/bin/env bash
+# Smoke test for dev-setup CLI. Run from repo root.
+set -euo pipefail
+
+PASS=0
+FAIL=0
+
+check() {
+  local label="$1"; shift
+  if output=$("$@" 2>&1); then
+    echo "  ✔  $label"
+    PASS=$((PASS+1))
+  else
+    echo "  ✘  $label"
+    echo "     Output: $output"
+    FAIL=$((FAIL+1))
+  fi
+}
+
+check_output() {
+  local label="$1"; local expected="$2"; shift 2
+  output=$("$@" 2>&1)
+  if echo "$output" | grep -q "$expected"; then
+    echo "  ✔  $label"
+    PASS=$((PASS+1))
+  else
+    echo "  ✘  $label (expected '$expected' in output)"
+    echo "     Got: $output"
+    FAIL=$((FAIL+1))
+  fi
+}
+
+echo ""
+echo "=== dev-setup smoke tests ==="
+echo ""
+
+check "version" uv run dev-setup version
+check_output "version number" "1\." uv run dev-setup version
+check "list (all)" uv run dev-setup list
+check "list core" uv run dev-setup list core
+check "list tools" uv run dev-setup list tools
+check "list --installed" uv run dev-setup list --installed
+check "list --available" uv run dev-setup list --available
+check "catalog path" uv run dev-setup catalog path
+check_output "catalog path output" ".config/dev-setup" uv run dev-setup catalog path
+check "catalog export" uv run dev-setup catalog export /tmp/dev-setup-smoke-export.yaml
+check_output "help flag" "Commands:" uv run dev-setup --help
+
+echo ""
+if [ "$FAIL" -eq 0 ]; then
+  echo "All $PASS checks passed."
+else
+  echo "$FAIL/$((PASS+FAIL)) checks failed."
+  exit 1
+fi

devstuff-1.13.1/.github/workflows/bump.yml

@@ -0,0 +1,95 @@
+name: Bump version
+
+on:
+  pull_request:
+    types: [closed]
+    branches:
+      - master
+
+# Serialize bump runs against master regardless of which PR triggered them.
+concurrency:
+  group: bump-master
+  cancel-in-progress: false
+
+jobs:
+  bump:
+    name: cz bump
+    runs-on: ubuntu-latest
+    # Only run for PRs that were actually merged, not closed unmerged.
+    # A raw `git push` — which is how this job publishes its own commit —
+    # never fires pull_request events, so there's no infinite-loop risk
+    # from this job triggering itself (unlike the old push-to-master
+    # trigger, which needed an explicit "bump:" message guard for that).
+    if: github.event.pull_request.merged == true
+    permissions:
+      contents: write
+    env:
+      # secrets can't be referenced directly in step `if:` conditions, so
+      # surface presence via an env var instead.
+      HAS_GH_PAT: ${{ secrets.GH_PAT != '' }}
+
+    steps:
+      - name: Require GH_PAT
+        # GH_PAT (a Personal Access Token with repo write scope) is required
+        # so that the tag push re-triggers publish.yml — GitHub Actions does
+        # not re-process events from pushes made with GITHUB_TOKEN. Fail loudly
+        # instead of silently pushing a tag that will never publish.
+        if: env.HAS_GH_PAT != 'true'
+        run: |
+          echo "::error::GH_PAT secret is not set. It is required so the tag push triggers publish.yml (GITHUB_TOKEN pushes are not re-processed by Actions)."
+          exit 1
+
+      - uses: actions/checkout@v4
+        with:
+          ref: master  # the merge already happened server-side by the time this runs
+          fetch-depth: 0  # commitizen needs full history to determine bump type
+          token: ${{ secrets.GH_PAT }}
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v5
+
+      - name: Configure git
+        run: |
+          git config user.name "github-actions[bot]"
+          git config user.email "github-actions[bot]@users.noreply.github.com"
+
+      - name: Run cz bump
+        id: bump
+        run: |
+          if uv run --group dev cz bump --yes; then
+            echo "bumped=true" >> "$GITHUB_OUTPUT"
+          else
+            EXIT=$?
+            if [ "$EXIT" -eq 21 ]; then
+              echo "No conventional commits found since last tag — nothing to bump."
+              echo "bumped=false" >> "$GITHUB_OUTPUT"
+            else
+              exit "$EXIT"
+            fi
+          fi
+
+      - name: Sync lockfile
+        if: steps.bump.outputs.bumped == 'true'
+        run: |
+          uv lock
+          git add uv.lock
+          if ! git diff --staged --quiet; then
+            # cz bump already tagged the pre-lock commit; amending moves HEAD
+            # to a new SHA, so the tag must be recreated to point at it.
+            # Must stay annotated (-a) — `git push --follow-tags` only
+            # pushes annotated tags, so a lightweight retag here would
+            # silently never reach the remote.
+            tag="$(git describe --tags --exact-match HEAD)"
+            git commit --amend --no-edit
+            git tag -f -a "$tag" -m "$tag" HEAD
+          fi
+
+      - name: Push commit and tag
+        if: steps.bump.outputs.bumped == 'true'
+        run: |
+          git push --follow-tags
+          tag="$(git describe --tags --exact-match HEAD)"
+          if ! git ls-remote --exit-code --tags origin "refs/tags/${tag}" >/dev/null; then
+            echo "::error::${tag} was not found on origin after push --follow-tags (publish.yml will not trigger)."
+            exit 1
+          fi

devstuff-1.13.1/.github/workflows/ci.yml

@@ -0,0 +1,27 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+jobs:
+  test:
+    name: Lint & unit tests
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: astral-sh/setup-uv@v5
+
+      - name: Sync dependencies
+        run: uv sync
+
+      - name: Ruff lint
+        run: uv run ruff check .
+
+      - name: Unit tests
+        run: uv run pytest -v

devstuff-1.13.1/.github/workflows/publish.yml

@@ -0,0 +1,44 @@
+name: Publish to PyPI
+
+on:
+  push:
+    tags:
+      - "v*"
+
+jobs:
+  build:
+    name: Build distribution
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v5
+
+      - name: Build wheel and source distribution
+        run: uv build
+
+      - name: Upload dist artifacts
+        uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  publish:
+    name: Publish to PyPI
+    needs: build
+    runs-on: ubuntu-latest
+    environment:
+      name: pypi
+      url: https://pypi.org/p/devstuff
+    permissions:
+      id-token: write  # required for OIDC trusted publishing
+    steps:
+      - name: Download dist artifacts
+        uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1

devstuff-1.13.1/.github/workflows/test-installs.yml

@@ -0,0 +1,174 @@
+name: Integration — Tool Installation
+
+# Weekly canary: catches upstream breakage (changed download URLs, API changes, etc.)
+# Manual trigger for ad-hoc validation (e.g., after merging a new tool).
+on:
+  schedule:
+    - cron: "0 6 * * 1"  # Monday 06:00 UTC
+  workflow_dispatch:
+
+jobs:
+  # ─── Stage 1: build the test image once and share it across all matrix jobs ───
+  build:
+    name: Build CI test image
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: astral-sh/setup-uv@v5
+
+      - name: Build wheel
+        run: uv build
+
+      # Two-step docker build matching the local dev workflow:
+      #   dev/Dockerfile        → dev-setup-sandbox  (minimal system + wheel installed)
+      #   dev/Dockerfile.ci     → dev-setup-ci       (+ pytest + test files baked in)
+      - name: Build sandbox image
+        run: docker build -f dev/Dockerfile -t dev-setup-sandbox .
+
+      - name: Build CI test image
+        run: docker build -f dev/Dockerfile.ci -t dev-setup-ci .
+
+      - name: Export image archive
+        run: docker save dev-setup-ci | gzip > dev-setup-ci.tar.gz
+
+      - name: Upload image artifact
+        uses: actions/upload-artifact@v4
+        with:
+          name: docker-image
+          path: dev-setup-ci.tar.gz
+          retention-days: 1
+
+  # ─── Stage 2: one isolated container per tool, all run in parallel ───────────
+  test:
+    name: Test — ${{ matrix.tool }}
+    needs: build
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false  # let all tools run even when some fail
+      matrix:
+        tool:
+          - aws
+          - eza
+          - gh
+          - git-lfs
+          - go
+          - htop
+          - ipython     # uvx tool, requires uv
+          - java
+          - lazygit
+          - mkcert
+          - nvm
+          - php
+          - pi          # installs nvm first via its declared `requires`
+          - ruby        # compiles from source — this job takes ~15 minutes
+          - saml2aws
+          - starship
+          - uv
+          - whichllm    # uvx tool, requires uv
+          - yq
+
+    steps:
+      - name: Download image artifact
+        uses: actions/download-artifact@v4
+        with:
+          name: docker-image
+
+      - name: Load image
+        run: docker load < dev-setup-ci.tar.gz
+
+      - name: Test ${{ matrix.tool }} installs
+        run: |
+          set +e
+          docker run --rm dev-setup-ci \
+            pytest "tests/integration/test_tools.py::test_install[${{ matrix.tool }}]" \
+              -v --tb=short 2>&1 | tee test-output.txt
+          RESULT=${PIPESTATUS[0]}
+          exit ${RESULT}
+
+      - name: Upload test output
+        if: always()
+        uses: actions/upload-artifact@v4
+        with:
+          name: test-output-${{ matrix.tool }}
+          path: test-output.txt
+
+      # Failure marker: a tiny file named after the tool so the report job can
+      # list exactly which tools failed without parsing pytest output.
+      - name: Write failure marker
+        if: failure()
+        run: echo "${{ matrix.tool }}" > "${{ matrix.tool }}.txt"
+
+      - name: Upload failure marker
+        if: failure()
+        uses: actions/upload-artifact@v4
+        with:
+          name: failure-${{ matrix.tool }}
+          path: ${{ matrix.tool }}.txt
+
+  # ─── Stage 3: open or update one GitHub issue summarising all failures ────────
+  report:
+    name: Report failures
+    needs: test
+    if: always() && needs.test.result == 'failure'
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      issues: write
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Download failure markers
+        uses: actions/download-artifact@v4
+        with:
+          pattern: failure-*
+          merge-multiple: true
+          path: failures/
+        continue-on-error: true  # no artifacts = nothing to download; don't abort
+
+      - name: Create or update issue
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          RUN_URL: ${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}
+        run: |
+          # Collect the names of tools that failed from their marker files
+          FAILED_LIST=""
+          for f in failures/*.txt; do
+            [ -f "$f" ] || continue
+            FAILED_LIST="${FAILED_LIST}\n- $(cat "$f")"
+          done
+
+          if [ -z "$FAILED_LIST" ]; then
+            FAILED_LIST="\n- (unknown — inspect the workflow run for details)"
+          fi
+
+          # Ensure the tracking label exists (no-ops if already present)
+          gh label create "install-ci" \
+            --color "#e11d48" \
+            --description "Automated tool-installation CI failure" \
+            2>/dev/null || true
+
+          BODY="## Tool installation failures\n\nThe following builtin tools failed to install in a clean Ubuntu environment:\n${FAILED_LIST}\n\n**Workflow run:** ${RUN_URL}\n\n_Opened automatically by the \`test-installs\` workflow. Close this issue once the failure is resolved and confirmed passing._"
+
+          # Dedup: comment on the existing open issue rather than filing a new one.
+          # This keeps the tracker tidy across weekly runs.
+          EXISTING=$(gh issue list \
+            --label "install-ci" \
+            --state open \
+            --json number \
+            --jq '.[0].number' 2>/dev/null)
+
+          if [ -n "$EXISTING" ]; then
+            gh issue comment "${EXISTING}" \
+              --body "$(printf '%b' "${BODY}")"
+            echo "Commented on existing issue #${EXISTING}"
+          else
+            gh issue create \
+              --title "Install CI: tool failures ($(date +%Y-%m-%d))" \
+              --body "$(printf '%b' "${BODY}")" \
+              --label "install-ci,bug"
+          fi

devstuff-1.13.1/.gitignore

@@ -0,0 +1,11 @@
+.venv/
+__pycache__/
+*.pyc
+*.pyo
+*.egg-info/
+dist/
+build/
+.pytest_cache/
+.mypy_cache/
+.ruff_cache/
+.claude/settings.local.json

devstuff-1.13.1/CHANGELOG.md

@@ -0,0 +1,159 @@
+## v1.13.1 (2026-07-11)
+
+## v1.13.0 (2026-07-05)
+
+### Feat
+
+- add category field, yq tool, and 4 new functions
+
+## v1.12.0 (2026-07-05)
+
+### Feat
+
+- add functions/scripts subsystem (dev-setup run / functions)
+
+### Fix
+
+- enforce required function params — empty values and bashrc calls
+
+## v1.11.0 (2026-07-05)
+
+### Feat
+
+- add interactive update picker with recommended-update detection
+- add update command to upgrade installed packages
+- add CLAUDE.md for project guidance and tool installation instructions
+- group interactive install picker by category with aligned columns and parallel status probe
+
+### Refactor
+
+- dataclass GenericTool with strategy dispatch, recursive requires, sha256 script verification, parallel list, ruff lint + unit tests
+
+## v1.10.0 (2026-07-04)
+
+### Feat
+
+- **catalog**: add ansible and ansible-vault tools
+
+## v1.9.1 (2026-07-01)
+
+### Fix
+
+- correct lmstudio tool entry and add homebrew
+
+## v1.9.0 (2026-07-01)
+
+### Feat
+
+- remove eza tool and update llm-checker configuration in tools.yaml
+
+## v1.8.2 (2026-07-01)
+
+### Fix
+
+- bump workflow silently dropped the tag after lockfile sync
+
+## v1.8.1 (2026-07-01)
+
+### Fix
+
+- move GH_PAT presence check out of step if: condition
+- harden bump workflow and close CI/removal gaps found in review
+
+## v1.8.0 (2026-06-28)
+
+### Feat
+
+- **catalog**: add ipython to tools
+- add bat and pre-commit to tool catalog
+
+### Fix
+
+- update git push command to ensure tags are pushed correctly
+- update Pi Coding Agent tool configuration for improved installation and usage
+- enhance Makefile with run-tests options for improved testing flexibility
+- remove legacy migration and correct YAML refactor bugs
+
+## v1.7.1 (2026-06-27)
+
+### Fix
+
+- include whichllm and corrected uv.lock
+
+## v1.7.0 (2026-06-27)
+
+### Feat
+
+- load tools from YAML catalogs
+
+## v1.6.0 (2026-06-26)
+
+### Feat
+
+- update add_cmd to support uvx package type and enhance GenericTool for uv dependencies
+
+## v1.5.0 (2026-06-26)
+
+### Feat
+
+- post-add remove script validation for bash tools
+
+### Fix
+
+- restore zip permissions explicitly and surface aws installer errors
+- resolve CI install failures for aws, htop, php, ruby
+
+## v1.4.0 (2026-06-19)
+
+### Feat
+
+- add eza builtin tool
+
+## v1.3.0 (2026-06-19)
+
+### Feat
+
+- gate tool availability on required dependencies
+
+## 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