[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B0PQ36VCZF6DCXV1YC5R8Z":3,"skill-same:01M7B0PQ36VCZF6DCXV1YC5R8Z":53},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":13,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M7B0PQ36VCZF6DCXV1YC5R8Z","docker-test-shell",null,"Use when testing in a clean throwaway container.","gitricko\u002F.minions","gitricko","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F18060558?v=4","01M7B0KG9EHG0CZ0QT1EN5YPCR","01M7B0KGA0ZV14R7SKBF3B5SCT",2,"MIT","https:\u002F\u002Fgithub.com\u002Fgitricko\u002F.minions\u002Fblob\u002Fmain\u002Fskills\u002Fdocker-test-shell\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: docker-test-shell\ndescription: Use when testing in a clean throwaway container.\nversion: 1.0.0\nauthor: Hermes Agent\nlicense: MIT\nplatforms: [linux]\n---\n\n# Docker Test Shell (`dts`)\n\nTest ANY tool inside a fresh, throwaway Linux container — never trust the host.\n\n## The one concept\n\n> Test inside a throwaway container so your own environment's installed libs, stale state, and services do not pollute the test.\n\nThat is the entire tool. No test framework, no schema, no verify primitives. Just: get me into a clean container with my repo mounted in, and let me run commands. Target logic is PLAIN SHELL composed of `dts exec` + bash checks.\n\n## Quickstart\n\n```bash\n# from the repo you want to test (it gets bind-mounted at \u002Fsrc)\n.\u002Fscripts\u002Fdts.sh up\n.\u002Fscripts\u002Fdts.sh exec \"bash \u002Fsrc\u002Finstall.sh\"\n.\u002Fscripts\u002Fdts.sh exec \"my-tool --version\"\n.\u002Fscripts\u002Fdts.sh clean\n```\n\nFor convenience, add the script dir to PATH or alias `dts`:\n```bash\nexport PATH=\"$PWD\u002Fscripts:$PATH\"   # or symlink dts.sh -> \u002Fusr\u002Flocal\u002Fbin\u002Fdts\n```\n\n## Commands\n\n| Command | Job |\n|---------|-----|\n| `dts up` | Create container (fresh base, repo bind-mounted at `\u002Fsrc`, uid-1000 user). Installs NOTHING. |\n| `dts exec \"\u003Ccmd>\"` | Run `\u003Ccmd>` inside the container as the uid-1000 user, `bash -l`. TTY-aware. |\n| `dts apt \"\u003Cpkgs>\"` | Run `apt-get update && install -y \u003Cpkgs>` as ROOT. The one privileged path (apt needs root; normal user can't). |\n| `dts shell` | Drop into an interactive shell (`-it`). For a human at a terminal. |\n| `dts clean` | Remove the container (no orphans). |\n| `dts status` | Show container state + note the mount is present. |\n\n## When to use `dts exec` vs raw `docker exec`\n\n| Scenario | Use | Why | Notes |\n|----------|-----|-----|-------|\n| Normal test commands (build, version check, API call) | `dts exec` | Runs as uid-1000, `bash -l`, `-i` no `-t` — matches CI\u002FCodespace parity | |\n| Install apt packages (`apt-get install`) | `dts apt` | Dedicated root path; apt needs root, uid-1000 can't | |\n| Debug interactively (human at terminal) | `dts shell` | `-it` gives full interactive TTY | |\n| One-off root inspection (logs, sqlite, config files) | `docker exec -u 0:0 dts-test \u003Ccmd>` | Root-only operations outside apt; explicit `docker exec -u 0:0` signals intent | |\n| Multi-step stateful commands from a script | `dts exec` with piped stdin | `printf 'cmd1\\ncmd2\\n' \\| dts exec bash` — stdin stays open, runs sequentially | |\n\n**Rule of thumb:** `dts exec` = the test harness path (uid-1000, parity). Raw `docker exec -u 0:0` = the escape hatch for root-only ops that aren't apt installs (e.g. reading sqlite DBs, checking process ports, killing stuck processes). Don't run test commands as root — it masks permission bugs that would fail in CI\u002FCodespace.\n\n## Config\n\n- **Base image**: configurable via `IMAGE`, defaults to `ubuntu:24.04`:\n  ```bash\n  IMAGE=debian:12 dts up\n  IMAGE=node:22 dts up\n  ```\n- **Container name**: `CONTAINER` (default `dts-test`).\n- **Mount target**: always `\u002Fsrc`. Static, predictable.\n- **uid\u002Fgid**: `CONTAINER_UID`\u002F`CONTAINER_GID` (default 1000).\n\n## The golden rules (each verified by live testing)\n\n1. **Never trust the host.** Always repro in the container. The host has stale packages, leftover venvs, running services — a passing host test proves nothing about a fresh install.\n2. **Drive with `docker exec -i`, never `-it`, when scripted.** `-it` fails with \"the input device is not a TTY\" when stdin is piped (an agent's normal mode). `-i` keeps stdin open, runs scripted AND stateful REPL-style commands fine. Reserve `-it` for a real human typing.\n3. **Use `bash -l` (login shell).** Plain `bash -c` is non-interactive and doesn't source `.profile`. Login shell gives host\u002FCI parity.\n4. **Run as uid 1000, never root.** CI runner + Codespaces both run uid 1000; root masks permission bugs. `dts` does this automatically.\n5. **Install apt packages with `dts apt`, never `dts exec`** — apt (and other package managers) need root, but the container's normal user runs as uid 1000 and can't. Use the dedicated root path:\n   ```bash\n   dts apt \"curl g++ make\"          # apt-get update && install -y, as root\n   ```\n   `dts exec` is the uid-1000 path for the actual test commands. Different targets need different prereqs; keep the tool minimal and make the choice explicit per test.\n6. **Verify the mount with md5, not just listing.** Listing can lie; md5 proves same file (host write appears in container, container write appears on host, file md5-identical both sides).\n7. **Clean up after yourself.** No orphan containers. `dts clean`.\n\n## Verification is plain shell\n\nThere are no `verify` subcommands. Check exit codes, grep output, curl endpoints:\n\n```bash\ndts exec \"hermes --version\" && echo \"install OK\"\ndts exec \"curl -sf http:\u002F\u002F127.0.0.1:20128\u002Fhealthz && echo server-up\"\n```\n\n## Non-goals\n\n- No test-definition \u002F YAML schema (target logic = a short bash script).\n- No `verify` subcommands.\n- No Dockerfile \u002F image build (bind-mount + base image, no rebuild cycle).\n- No persistent SSH-like daemon (`docker exec -i` + piped stdin reproduces a stateful session).\n- No bundled apt prereqs.\n\n## How to teach\u002Fperpetuate this\n\n1. **Never trust the host** — always repro in a fresh container.\n2. **Learn the target iteratively** in `shell` mode (or one-off `exec`): poke, observe, confirm, then codify.\n3. **Codify as a short bash script** of `dts exec` + checks — repeatable, and arguably CI-run-able.\n4. **Record each pitfall** with root cause + fix (as references\u002F here or a wiki article).\n\n## Pitfalls table (hard-won)\n\n| Pitfall | Root cause | Fix |\n|---------|-----------|-----|\n| \"input device is not a TTY\" when scripted | `docker exec -it` needs a host PTY | Use `-i` (no `-t`) when stdin is piped; `-it` only for a real human |\n| No `.profile` sourced | `bash -c` is non-interactive | Use `bash -l` (login shell) |\n| Permission bugs masked | Tested as root | Always run as uid 1000 (CI\u002FCodespace parity) |\n| Mount \"works\" but file is stale | Bind-mount created once; container cached | Verify with md5 both sides; never trust a listing |\n| Orphan containers eat disk | No cleanup | `dts clean` after each session |\n| `rm -rf ~\u002F.minions` fails \"Device or resource busy\" in DTS | Host ollama cache mounted at `$MINIONS_HOME\u002Flib\u002Follama` via `-v \u002Ftmp\u002F...:\u002Fhome\u002F...\u002Flib\u002Follama` — `rm -rf` cannot remove a mountpoint | Mount cache outside the tree (`\u002Ftmp\u002Fcache:ro`) instead; if legacy mount remains, unmount with `umount -l` plus `sudo umount -l` fallback (container runs as uid 1000) |\n| `mkdir -p lib\u002Follama` fails \"Read-only filesystem\" through symlink | Dir symlink `lib\u002Follama -> \u002Ftmp\u002Fcache:ro` makes `mkdir -p` traverse the ro target | Symlink files not dirs: `lib\u002Follama\u002Follama -> \u002Ftmp\u002Fcache\u002Follama`; `mkdir -p lib\u002Follama` then creates a real dir |\n| `mkdir ~\u002F.minions` fails \"Permission denied\" in DTS | Base image pre-creates `$HOME` owned by root; conditional `[ -d $home ] or chown` skipped the fix | Always `mkdir -p $home && chown $uid:$gid $home` unconditionally in `dts up` |\n| Cache not mounted so install re-downloads and fails | Version string `v0.40.0` vs cache dir `ollama-0.40.0-...` — un-stripped `v` leaves `OLLAMA_HOST_CACHE` empty | Normalize `version=${version#v}` and map arch aliases before building the cache path |\n| `bash install.sh \\| tee log` reports success while install failed | Pipe exit is `tee`'s 0 when `pipefail` is off, masking left-side failure | Prefix with `set -o pipefail; cmd \\| tee log` |\n| `npm install` OOM `JavaScript heap out of memory` | `NODE_OPTIONS --max-old-space-size=512` too small for large package in constrained DTS\u002FCI | Raise to 2048 in shared `install_npm_package` wrapper |\n| `.tar.zst` fails `stdin: not in gzip format` or `zstd required` | Missing `zstd` in DTS container and `tar -xzf` used for `.tar.zst` (needs `--zstd`\u002F`-I zstd`) | Install `zstd` in `dts apt` prereqs; extract via `zstd -dc \\| tar -xf` or `tar --zstd -xf`; prefer host cache copy `\u002Ftmp\u002Follama-cache\u002Follama` on reinstall to avoid re-download |\n| New optional binary re-downloads every DTS run | No `*_HOST_CACHE` mount for the new dep — same trap as Ollama before `OLLAMA_HOST_CACHE` | Mirror the Ollama pattern: mount host cache at `\u002Ftmp\u002F\u003Cname>-cache:ro` (outside `MINIONS_HOME`), add `TAILSCALE_HOST_CACHE` handling in `scripts\u002Fdts.sh` and a fast-path `if [ -f \u002Ftmp\u002F\u003Cname>-cache\u002F\u003Cbin> ]` in `lib\u002F\u003Cname>.sh` |\n| Daemon needs TUN\u002F`NET_ADMIN` but tests run as uid 1000 | `tailscaled` fails to create TUN, or second daemon collides on control socket when systemd already runs one | Default to `--tun=userspace-networking` with `--statedir` + `--socket` under `MINIONS_HOME` (`TAILSCALE_SOCKET`), presence-gate boot on `command -v`, guard `systemctl is-active`\u002F`pgrep` before `start_service`, and keep `status.sh`\u002F`self-check.sh` `set -e`-safe |\n\n## Support files\n\n- `scripts\u002Fdts.sh` — the tool itself (up\u002Fexec\u002Fshell\u002Fclean\u002Fstatus).\n- `references\u002Fdts-usage.md` — worked examples + how the golden rules were validated.\n\n## Related\n\n- Wiki: [docker-test-shell-proposal.md](..\u002F..\u002Fwiki\u002Fdocker-test-shell-proposal.md) — full design rationale.\n- This skill replaces the project-specific `minions-docker-testing` approach with a standalone primitive.\n","# Docker Test Shell (`dts`)\n\nTest ANY tool inside a fresh, throwaway Linux container — never trust the host.\n\n## The one concept\n\n> Test inside a throwaway container so your own environment's installed libs, stale state, and services do not pollute the test.\n\nThat is the entire tool. No test framework, no schema, no verify primitives. Just: get me into a clean container with my repo mounted in, and let me run commands. Target logic is PLAIN SHELL composed of `dts exec` + bash checks.\n\n## Quickstart\n\n```bash\n# from the repo you want to test (it gets bind-mounted at \u002Fsrc)\n.\u002Fscripts\u002Fdts.sh up\n.\u002Fscripts\u002Fdts.sh exec \"bash \u002Fsrc\u002Finstall.sh\"\n.\u002Fscripts\u002Fdts.sh exec \"my-tool --version\"\n.\u002Fscripts\u002Fdts.sh clean\n```\n\nFor convenience, add the script dir to PATH or alias `dts`:\n```bash\nexport PATH=\"$PWD\u002Fscripts:$PATH\"   # or symlink dts.sh -> \u002Fusr\u002Flocal\u002Fbin\u002Fdts\n```\n\n## Commands\n\n| Command | Job |\n|---------|-----|\n| `dts up` | Create container (fresh base, repo bind-mounted at `\u002Fsrc`, uid-1000 user). Installs NOTHING. |\n| `dts exec \"\u003Ccmd>\"` | Run `\u003Ccmd>` inside the container as the uid-1000 user, `bash -l`. TTY-aware. |\n| `dts apt \"\u003Cpkgs>\"` | Run `apt-get update && install -y \u003Cpkgs>` as ROOT. The one privileged path (apt needs root; normal user can't). |\n| `dts shell` | Drop into an interactive shell (`-it`). For a human at a terminal. |\n| `dts clean` | Remove the container (no orphans). |\n| `dts status` | Show container state + note the mount is present. |\n\n## When to use `dts exec` vs raw `docker exec`\n\n| Scenario | Use | Why | Notes |\n|----------|-----|-----|-------|\n| Normal test commands (build, version check, API call) | `dts exec` | Runs as uid-1000, `bash -l`, `-i` no `-t` — matches CI\u002FCodespace parity | |\n| Install apt packages (`apt-get install`) | `dts apt` | Dedicated root path; apt needs root, uid-1000 can't | |\n| Debug interactively (human at terminal) | `dts shell` | `-it` gives full interactive TTY | |\n| One-off root inspection (logs, sqlite, config files) | `docker exec -u 0:0 dts-test \u003Ccmd>` | Root-only operations outside apt; explicit `docker exec -u 0:0` signals intent | |\n| Multi-step stateful commands from a script | `dts exec` with piped stdin | `printf 'cmd1\\ncmd2\\n' \\| dts exec bash` — stdin stays open, runs sequentially | |\n\n**Rule of thumb:** `dts exec` = the test harness path (uid-1000, parity). Raw `docker exec -u 0:0` = the escape hatch for root-only ops that aren't apt installs (e.g. reading sqlite DBs, checking process ports, killing stuck processes). Don't run test commands as root — it masks permission bugs that would fail in CI\u002FCodespace.\n\n## Config\n\n- **Base image**: configurable via `IMAGE`, defaults to `ubuntu:24.04`:\n  ```bash\n  IMAGE=debian:12 dts up\n  IMAGE=node:22 dts up\n  ```\n- **Container name**: `CONTAINER` (default `dts-test`).\n- **Mount target**: always `\u002Fsrc`. Static, predictable.\n- **uid\u002Fgid**: `CONTAINER_UID`\u002F`CONTAINER_GID` (default 1000).\n\n## The golden rules (each verified by live testing)\n\n1. **Never trust the host.** Always repro in the container. The host has stale packages, leftover venvs, running services — a passing host test proves nothing about a fresh install.\n2. **Drive with `docker exec -i`, never `-it`, when scripted.** `-it` fails with \"the input device is not a TTY\" when stdin is piped (an agent's normal mode). `-i` keeps stdin open, runs scripted AND stateful REPL-style commands fine. Reserve `-it` for a real human typing.\n3. **Use `bash -l` (login shell).** Plain `bash -c` is non-interactive and doesn't source `.profile`. Login shell gives host\u002FCI parity.\n4. **Run as uid 1000, never root.** CI runner + Codespaces both run uid 1000; root masks permission bugs. `dts` does this automatically.\n5. **Install apt packages with `dts apt`, never `dts exec`** — apt (and other package managers) need root, but the container's normal user runs as uid 1000 and can't. Use the dedicated root path:\n   ```bash\n   dts apt \"curl g++ make\"          # apt-get update && install -y, as root\n   ```\n   `dts exec` is the uid-1000 path for the actual test commands. Different targets need different prereqs; keep the tool minimal and make the choice explicit per test.\n6. **Verify the mount with md5, not just listing.** Listing can lie; md5 proves same file (host write appears in container, container write appears on host, file md5-identical both sides).\n7. **Clean up after yourself.** No orphan containers. `dts clean`.\n\n## Verification is plain shell\n\nThere are no `verify` subcommands. Check exit codes, grep output, curl endpoints:\n\n```bash\ndts exec \"hermes --version\" && echo \"install OK\"\ndts exec \"curl -sf http:\u002F\u002F127.0.0.1:20128\u002Fhealthz && echo server-up\"\n```\n\n## Non-goals\n\n- No test-definition \u002F YAML schema (target logic = a short bash script).\n- No `verify` subcommands.\n- No Dockerfile \u002F image build (bind-mount + base image, no rebuild cycle).\n- No persistent SSH-like daemon (`docker exec -i` + piped stdin reproduces a stateful session).\n- No bundled apt prereqs.\n\n## How to teach\u002Fperpetuate this\n\n1. **Never trust the host** — always repro in a fresh container.\n2. **Learn the target iteratively** in `shell` mode (or one-off `exec`): poke, observe, confirm, then codify.\n3. **Codify as a short bash script** of `dts exec` + checks — repeatable, and arguably CI-run-able.\n4. **Record each pitfall** with root cause + fix (as references\u002F here or a wiki article).\n\n## Pitfalls table (hard-won)\n\n| Pitfall | Root cause | Fix |\n|---------|-----------|-----|\n| \"input device is not a TTY\" when scripted | `docker exec -it` needs a host PTY | Use `-i` (no `-t`) when stdin is piped; `-it` only for a real human |\n| No `.profile` sourced | `bash -c` is non-interactive | Use `bash -l` (login shell) |\n| Permission bugs masked | Tested as root | Always run as uid 1000 (CI\u002FCodespace parity) |\n| Mount \"works\" but file is stale | Bind-mount created once; container cached | Verify with md5 both sides; never trust a listing |\n| Orphan containers eat disk | No cleanup | `dts clean` after each session |\n| `rm -rf ~\u002F.minions` fails \"Device or resource busy\" in DTS | Host ollama cache mounted at `$MINIONS_HOME\u002Flib\u002Follama` via `-v \u002Ftmp\u002F...:\u002Fhome\u002F...\u002Flib\u002Follama` — `rm -rf` cannot remove a mountpoint | Mount cache outside the tree (`\u002Ftmp\u002Fcache:ro`) instead; if legacy mount remains, unmount with `umount -l` plus `sudo umount -l` fallback (container runs as uid 1000) |\n| `mkdir -p lib\u002Follama` fails \"Read-only filesystem\" through symlink | Dir symlink `lib\u002Follama -> \u002Ftmp\u002Fcache:ro` makes `mkdir -p` traverse the ro target | Symlink files not dirs: `lib\u002Follama\u002Follama -> \u002Ftmp\u002Fcache\u002Follama`; `mkdir -p lib\u002Follama` then creates a real dir |\n| `mkdir ~\u002F.minions` fails \"Permission denied\" in DTS | Base image pre-creates `$HOME` owned by root; conditional `[ -d $home ] or chown` skipped the fix | Always `mkdir -p $home && chown $uid:$gid $home` unconditionally in `dts up` |\n| Cache not mounted so install re-downloads and fails | Version string `v0.40.0` vs cache dir `ollama-0.40.0-...` — un-stripped `v` leaves `OLLAMA_HOST_CACHE` empty | Normalize `version=${version#v}` and map arch aliases before building the cache path |\n| `bash install.sh \\| tee log` reports success while install failed | Pipe exit is `tee`'s 0 when `pipefail` is off, masking left-side failure | Prefix with `set -o pipefail; cmd \\| tee log` |\n| `npm install` OOM `JavaScript heap out of memory` | `NODE_OPTIONS --max-old-space-size=512` too small for large package in constrained DTS\u002FCI | Raise to 2048 in shared `install_npm_package` wrapper |\n| `.tar.zst` fails `stdin: not in gzip format` or `zstd required` | Missing `zstd` in DTS container and `tar -xzf` used for `.tar.zst` (needs `--zstd`\u002F`-I zstd`) | Install `zstd` in `dts apt` prereqs; extract via `zstd -dc \\| tar -xf` or `tar --zstd -xf`; prefer host cache copy `\u002Ftmp\u002Follama-cache\u002Follama` on reinstall to avoid re-download |\n| New optional binary re-downloads every DTS run | No `*_HOST_CACHE` mount for the new dep — same trap as Ollama before `OLLAMA_HOST_CACHE` | Mirror the Ollama pattern: mount host cache at `\u002Ftmp\u002F\u003Cname>-cache:ro` (outside `MINIONS_HOME`), add `TAILSCALE_HOST_CACHE` handling in `scripts\u002Fdts.sh` and a fast-path `if [ -f \u002Ftmp\u002F\u003Cname>-cache\u002F\u003Cbin> ]` in `lib\u002F\u003Cname>.sh` |\n| Daemon needs TUN\u002F`NET_ADMIN` but tests run as uid 1000 | `tailscaled` fails to create TUN, or second daemon collides on control socket when systemd already runs one | Default to `--tun=userspace-networking` with `--statedir` + `--socket` under `MINIONS_HOME` (`TAILSCALE_SOCKET`), presence-gate boot on `command -v`, guard `systemctl is-active`\u002F`pgrep` before `start_service`, and keep `status.sh`\u002F`self-check.sh` `set -e`-safe |\n\n## Support files\n\n- `scripts\u002Fdts.sh` — the tool itself (up\u002Fexec\u002Fshell\u002Fclean\u002Fstatus).\n- `references\u002Fdts-usage.md` — worked examples + how the golden rules were validated.\n\n## Related\n\n- Wiki: [docker-test-shell-proposal.md](..\u002F..\u002Fwiki\u002Fdocker-test-shell-proposal.md) — full design rationale.\n- This skill replaces the project-specific `minions-docker-testing` approach with a standalone primitive.\n",{"name":5,"author":23,"license":14,"version":24,"platforms":25,"description":7},"Hermes Agent","1.0.0",[26],"linux","main","e95aec76487a22bbbc23b63234724bc7178d4692","skills\u002Fdocker-test-shell","https:\u002F\u002Fgithub.com\u002Fgitricko\u002F.minions","https:\u002F\u002Fgithub.com\u002Fgitricko","2026-11-13 16:00:00",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add gitricko\u002F.minions --skill docker-test-shell",{"tool":39,"command":40},"bunx","bunx skills add gitricko\u002F.minions --skill docker-test-shell",{"tool":42,"command":43},"pnpm","pnpm dlx skills add gitricko\u002F.minions --skill docker-test-shell","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgitricko\u002F.minions\u002Fblob\u002Fmain\u002Fskills\u002Fdocker-test-shell\u002FSKILL.md",true,[47],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fdts-usage.md","REFERENCE","参考文档",4215,"https:\u002F\u002Fgithub.com\u002Fgitricko\u002F.minions\u002Fblob\u002Fmain\u002Fskills\u002Fdocker-test-shell\u002Freferences\u002Fdts-usage.md",[54,61,68,75,82,89],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M7B0VJ3Q0YMCTJY69FEJ4100","version-single-source","Use when adding a new component dependency or versioning a binary in install\u002Fboot scripts.","https:\u002F\u002Fgithub.com\u002Fgitricko\u002F.minions\u002Fblob\u002Fmain\u002Fskills\u002Fversion-single-source\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M7B0V888DV8J3JY5W9Z6WCF3","tdd","Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions \"red-green-refactor\", or wants integration tests.","https:\u002F\u002Fgithub.com\u002Fgitricko\u002F.minions\u002Fblob\u002Fmain\u002Fskills\u002Ftdd\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M7B0TVFM38JH3PBA2K219Z2X","shell-path-login","Use when a binary or script works in one shell context but not another (interactive vs non-interactive login vs non-login shell).","https:\u002F\u002Fgithub.com\u002Fgitricko\u002F.minions\u002Fblob\u002Fmain\u002Fskills\u002Fshell-path-login\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M7B0TKFCTVQBTSNF9WF1MXJ6","self-update-fix","Fix a failing dependency update PR. Use when a self-update PR's CI fails, or when invoked by scripts\u002Fself-update-fix.sh.","https:\u002F\u002Fgithub.com\u002Fgitricko\u002F.minions\u002Fblob\u002Fmain\u002Fskills\u002Fself-update-fix\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M7B0TB57WEW0E6E9874K3C72","pr-change-log","Use when a multi-commit PR needs its description written\u002Fupdated, or when closing out a long branch with many fix commits.","https:\u002F\u002Fgithub.com\u002Fgitricko\u002F.minions\u002Fblob\u002Fmain\u002Fskills\u002Fpr-change-log\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":18},"01M7B0T2FGSV0ZFRZ46PG4BBY2","persistent-knowledge","Persistent skills\u002Fknowledge in Codespace via symlinks.","https:\u002F\u002Fgithub.com\u002Fgitricko\u002F.minions\u002Fblob\u002Fmain\u002Fskills\u002Fpersistent-knowledge\u002FSKILL.md",[],[]]