{"owner":"XRPLF","repo":"rippled","hasSkills":true,"totalSkillsCount":1,"totalTokensCount":671,"categories":["plugin-manifest"],"hasMcp":false,"mcpConfig":null,"found":["nix/check-tools/README.md"],"skills":{"nix/check-tools/README.md":"# check-tools snapshots\n\nThese files capture the output of [`bin/check-tools.sh`](../../bin/check-tools.sh)\n— the version and resolved store path of each development tool — in each Nix\nenvironment:\n\n| File                   | Environment                          |\n| ---------------------- | ------------------------------------ |\n| `nix-ubuntu-amd64.txt` | `nix-ubuntu` CI image, `linux/amd64` |\n| `nix-ubuntu-arm64.txt` | `nix-ubuntu` CI image, `linux/arm64` |\n| `macos.txt`            | macOS, inside `nix develop`          |\n\nThe [`check-tools`](../../.github/workflows/check-tools.yml) workflow regenerates\neach snapshot in its environment and fails if it differs from the committed file.\nSo if you change the environment (bump the image tag in\n[`linux.json`](../../.github/scripts/strategy-matrix/linux.json), update\n`flake.lock`, change the tool list in `check-tools.sh`, …) you must regenerate\nand commit the affected snapshots.\n\nEach snapshot is `check-tools.sh` stdout with the git-clone connectivity check\nskipped (`CHECK_TOOLS_SKIP_CLONE=1`), so it is deterministic for a given\nenvironment. On macOS the dev-shell greeting that `nix develop` prints first is\ndropped with `sed -n '/^Detected OS:/,$p'`.\n\nThe store paths carry their derivation hash, so they change whenever a tool is\nrebuilt — a `flake.lock` update generally rewrites most of them even when no\nversion moves. That is deliberate: it makes tooling changes visible in review.\n\nTools scoped to a single dev shell rather than to `commonPackages` do not appear\nhere: `check-tools.sh` keys those off `XRPL_DEVSHELL`, and none of the three\nenvironments above is such a shell. Adding to one needs no snapshot update.\n\n## Regenerating\n\nThe two Linux snapshots come from the `nix-ubuntu` image (Docker or a compatible\nruntime such as Apple `container`). The image tag is pinned in `linux.json`:\n\n```bash\nimg=\"ghcr.io/xrplf/xrpld/nix-ubuntu:$(jq -r .image_tag .github/scripts/strategy-matrix/linux.json)\"\n\nfor arch in amd64 arm64; do\n    container run --rm -i -e CHECK_TOOLS_SKIP_CLONE=1 -a \"${arch}\" --entrypoint bash \"${img}\" -s \\\n        <bin/check-tools.sh >\"nix/check-tools/nix-ubuntu-${arch}.txt\"\ndone\n```\n\n(With Docker, replace `container run … -a \"${arch}\"` with\n`docker run … --platform \"linux/${arch}\"`.)\n\nThe macOS snapshot is generated locally. `CI=` is unset so `check-tools.sh`\nchecks the full dev-shell tool set (it otherwise skips some tools when `CI` is\nset):\n\n```bash\nCI= nix develop -c bash -c 'CHECK_TOOLS_SKIP_CLONE=1 bash bin/check-tools.sh' |\n    sed -n '/^Detected OS:/,$p' \\\n        >nix/check-tools/macos.txt\n```\n"},"files":{"nix/check-tools/README.md":"# check-tools snapshots\n\nThese files capture the output of [`bin/check-tools.sh`](../../bin/check-tools.sh)\n— the version and resolved store path of each development tool — in each Nix\nenvironment:\n\n| File                   | Environment                          |\n| ---------------------- | ------------------------------------ |\n| `nix-ubuntu-amd64.txt` | `nix-ubuntu` CI image, `linux/amd64` |\n| `nix-ubuntu-arm64.txt` | `nix-ubuntu` CI image, `linux/arm64` |\n| `macos.txt`            | macOS, inside `nix develop`          |\n\nThe [`check-tools`](../../.github/workflows/check-tools.yml) workflow regenerates\neach snapshot in its environment and fails if it differs from the committed file.\nSo if you change the environment (bump the image tag in\n[`linux.json`](../../.github/scripts/strategy-matrix/linux.json), update\n`flake.lock`, change the tool list in `check-tools.sh`, …) you must regenerate\nand commit the affected snapshots.\n\nEach snapshot is `check-tools.sh` stdout with the git-clone connectivity check\nskipped (`CHECK_TOOLS_SKIP_CLONE=1`), so it is deterministic for a given\nenvironment. On macOS the dev-shell greeting that `nix develop` prints first is\ndropped with `sed -n '/^Detected OS:/,$p'`.\n\nThe store paths carry their derivation hash, so they change whenever a tool is\nrebuilt — a `flake.lock` update generally rewrites most of them even when no\nversion moves. That is deliberate: it makes tooling changes visible in review.\n\nTools scoped to a single dev shell rather than to `commonPackages` do not appear\nhere: `check-tools.sh` keys those off `XRPL_DEVSHELL`, and none of the three\nenvironments above is such a shell. Adding to one needs no snapshot update.\n\n## Regenerating\n\nThe two Linux snapshots come from the `nix-ubuntu` image (Docker or a compatible\nruntime such as Apple `container`). The image tag is pinned in `linux.json`:\n\n```bash\nimg=\"ghcr.io/xrplf/xrpld/nix-ubuntu:$(jq -r .image_tag .github/scripts/strategy-matrix/linux.json)\"\n\nfor arch in amd64 arm64; do\n    container run --rm -i -e CHECK_TOOLS_SKIP_CLONE=1 -a \"${arch}\" --entrypoint bash \"${img}\" -s \\\n        <bin/check-tools.sh >\"nix/check-tools/nix-ubuntu-${arch}.txt\"\ndone\n```\n\n(With Docker, replace `container run … -a \"${arch}\"` with\n`docker run … --platform \"linux/${arch}\"`.)\n\nThe macOS snapshot is generated locally. `CI=` is unset so `check-tools.sh`\nchecks the full dev-shell tool set (it otherwise skips some tools when `CI` is\nset):\n\n```bash\nCI= nix develop -c bash -c 'CHECK_TOOLS_SKIP_CLONE=1 bash bin/check-tools.sh' |\n    sed -n '/^Detected OS:/,$p' \\\n        >nix/check-tools/macos.txt\n```\n"},"items":[{"name":"README.md","path":"nix/check-tools/README.md","rawUrl":"https://raw.githubusercontent.com/XRPLF/rippled/HEAD/nix/check-tools/README.md","title":"check-tools Documentation","category":"plugin-manifest","format":"markdown","content":"# check-tools snapshots\n\nThese files capture the output of [`bin/check-tools.sh`](../../bin/check-tools.sh)\n— the version and resolved store path of each development tool — in each Nix\nenvironment:\n\n| File                   | Environment                          |\n| ---------------------- | ------------------------------------ |\n| `nix-ubuntu-amd64.txt` | `nix-ubuntu` CI image, `linux/amd64` |\n| `nix-ubuntu-arm64.txt` | `nix-ubuntu` CI image, `linux/arm64` |\n| `macos.txt`            | macOS, inside `nix develop`          |\n\nThe [`check-tools`](../../.github/workflows/check-tools.yml) workflow regenerates\neach snapshot in its environment and fails if it differs from the committed file.\nSo if you change the environment (bump the image tag in\n[`linux.json`](../../.github/scripts/strategy-matrix/linux.json), update\n`flake.lock`, change the tool list in `check-tools.sh`, …) you must regenerate\nand commit the affected snapshots.\n\nEach snapshot is `check-tools.sh` stdout with the git-clone connectivity check\nskipped (`CHECK_TOOLS_SKIP_CLONE=1`), so it is deterministic for a given\nenvironment. On macOS the dev-shell greeting that `nix develop` prints first is\ndropped with `sed -n '/^Detected OS:/,$p'`.\n\nThe store paths carry their derivation hash, so they change whenever a tool is\nrebuilt — a `flake.lock` update generally rewrites most of them even when no\nversion moves. That is deliberate: it makes tooling changes visible in review.\n\nTools scoped to a single dev shell rather than to `commonPackages` do not appear\nhere: `check-tools.sh` keys those off `XRPL_DEVSHELL`, and none of the three\nenvironments above is such a shell. Adding to one needs no snapshot update.\n\n## Regenerating\n\nThe two Linux snapshots come from the `nix-ubuntu` image (Docker or a compatible\nruntime such as Apple `container`). The image tag is pinned in `linux.json`:\n\n```bash\nimg=\"ghcr.io/xrplf/xrpld/nix-ubuntu:$(jq -r .image_tag .github/scripts/strategy-matrix/linux.json)\"\n\nfor arch in amd64 arm64; do\n    container run --rm -i -e CHECK_TOOLS_SKIP_CLONE=1 -a \"${arch}\" --entrypoint bash \"${img}\" -s \\\n        <bin/check-tools.sh >\"nix/check-tools/nix-ubuntu-${arch}.txt\"\ndone\n```\n\n(With Docker, replace `container run … -a \"${arch}\"` with\n`docker run … --platform \"linux/${arch}\"`.)\n\nThe macOS snapshot is generated locally. `CI=` is unset so `check-tools.sh`\nchecks the full dev-shell tool set (it otherwise skips some tools when `CI` is\nset):\n\n```bash\nCI= nix develop -c bash -c 'CHECK_TOOLS_SKIP_CLONE=1 bash bin/check-tools.sh' |\n    sed -n '/^Detected OS:/,$p' \\\n        >nix/check-tools/macos.txt\n```\n","isInternal":false,"tokens":671,"sizeBytes":2616}],"systemPromptSnippet":"<yakaai_skills repo=\"XRPLF/rippled\">\n<!-- File: nix/check-tools/README.md (Tokens: ~671 | Category: plugin-manifest) -->\n# check-tools snapshots\n\nThese files capture the output of [`bin/check-tools.sh`](../../bin/check-tools.sh)\n— the version and resolved store path of each development tool — in each Nix\nenvironment:\n\n| File                   | Environment                          |\n| ---------------------- | ------------------------------------ |\n| `nix-ubuntu-amd64.txt` | `nix-ubuntu` CI image, `linux/amd64` |\n| `nix-ubuntu-arm64.txt` | `nix-ubuntu` CI image, `linux/arm64` |\n| `macos.txt`            | macOS, inside `nix develop`          |\n\nThe [`check-tools`](../../.github/workflows/check-tools.yml) workflow regenerates\neach snapshot in its environment and fails if it differs from the committed file.\nSo if you change the environment (bump the image tag in\n[`linux.json`](../../.github/scripts/strategy-matrix/linux.json), update\n`flake.lock`, change the tool list in `check-tools.sh`, …) you must regenerate\nand commit the affected snapshots.\n\nEach snapshot is `check-tools.sh` stdout with the git-clone connectivity check\nskipped (`CHECK_TOOLS_SKIP_CLONE=1`), so it is deterministic for a given\nenvironment. On macOS the dev-shell greeting that `nix develop` prints first is\ndropped with `sed -n '/^Detected OS:/,$p'`.\n\nThe store paths carry their derivation hash, so they change whenever a tool is\nrebuilt — a `flake.lock` update generally rewrites most of them even when no\nversion moves. That is deliberate: it makes tooling changes visible in review.\n\nTools scoped to a single dev shell rather than to `commonPackages` do not appear\nhere: `check-tools.sh` keys those off `XRPL_DEVSHELL`, and none of the three\nenvironments above is such a shell. Adding to one needs no snapshot update.\n\n## Regenerating\n\nThe two Linux snapshots come from the `nix-ubuntu` image (Docker or a compatible\nruntime such as Apple `container`). The image tag is pinned in `linux.json`:\n\n```bash\nimg=\"ghcr.io/xrplf/xrpld/nix-ubuntu:$(jq -r .image_tag .github/scripts/strategy-matrix/linux.json)\"\n\nfor arch in amd64 arm64; do\n    container run --rm -i -e CHECK_TOOLS_SKIP_CLONE=1 -a \"${arch}\" --entrypoint bash \"${img}\" -s \\\n        <bin/check-tools.sh >\"nix/check-tools/nix-ubuntu-${arch}.txt\"\ndone\n```\n\n(With Docker, replace `container run … -a \"${arch}\"` with\n`docker run … --platform \"linux/${arch}\"`.)\n\nThe macOS snapshot is generated locally. `CI=` is unset so `check-tools.sh`\nchecks the full dev-shell tool set (it otherwise skips some tools when `CI` is\nset):\n\n```bash\nCI= nix develop -c bash -c 'CHECK_TOOLS_SKIP_CLONE=1 bash bin/check-tools.sh' |\n    sed -n '/^Detected OS:/,$p' \\\n        >nix/check-tools/macos.txt\n```\n</yakaai_skills>"}