Menu
Rebuild Ray from source — determines the right build mode based on what changed
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Diagnose a failing Ray Sphinx / Read the Docs documentation build. Parses the Sphinx warning stream (an RtD build log, a local build, or pasted text), classifies each warning against a rules table, and proposes the canonical fix in severity-tier order. Detects a hard-broken build, segregates known-benign suppressed classes, and lists every unclassified warning. Use when a `docs/readthedocs.com:anyscale-ray` check fails, when asked "why is the docs build failing?" or "what warning is breaking this PR?", or to turn a Sphinx warning dump into an ordered fix list.
Convert Ray documentation pages from reStructuredText (.rst) to MyST Markdown (.md). Use when migrating existing files under doc/source/ to MyST, finishing a partial MyST migration of a directory, or when asked to convert/migrate a doc page to markdown. Covers the RST-to-MyST directive mapping, label and cross-reference preservation, sphinx-design tabs/dropdowns, doctest/testcode handling, the doc/BUILD.bazel doctest exclusions, and the build and doctest verification needed to land a clean docs PR.
Run linting and formatting checks on Ray code
Manage Python dependencies in Ray — add/remove/upgrade packages, work with raydepsets lock files, debug dependency conflicts, and regenerate compiled requirements. Covers `python/requirements*`, `python/requirements/**`, `python/deplocks/**`, and `ci/raydepsets/configs/*.depsets.yaml`.
Fetch and analyze Buildkite CI build logs for failures
| name | rebuild |
| description | Rebuild Ray from source — determines the right build mode based on what changed |
Canonical build docs: doc/source/ray-contribute/development.md
Use the user's configured Python from CLAUDE.local.md, or fall back to which python.
Update this skill if any changes are detected in development.rst.
git diff --name-only HEAD (or ask the user)pip install -e . — editable mode auto-picks up Python changes)Running Python tests that exercise C++ changes: When a Python test depends on C++ or Cython code (raylet, GCS, core_worker, etc.), run the C++/Cython rebuild below before running the test. Editable Python installs do not rebuild the compiled extensions, so stale binaries will run otherwise.
For changes to Tune, RLlib, Autoscaler, and most Python files. Two approaches depending on how Ray was installed:
pip install -e . (editable/full source build)No rebuild needed — Python changes are picked up automatically.
python python/ray/setup-dev.pypython python/ray/setup-dev.py -y --skip _private dashboardWarning: With setup-dev.py, don't run pip uninstall ray or pip install -U.
Instead: rm -rf <site-packages>/ray, reinstall wheel, re-run setup-dev.py.
bazel run //:gen_ray_pkg
bazel build //src/ray/raylet:raylet # Raylet only
bazel build //src/ray/gcs:gcs_server # GCS server only
bazel build //src/ray/core_worker:core_worker # Core worker only
bazel build //:ray_pkg # All C++ and Cython
bazel run -c fastbuild //:gen_ray_pkg — fast build (less optimization)bazel run -c dbg //:gen_ray_pkg — debug build with symbols (for gdb)bazel run -c opt //:gen_ray_pkg — optimized buildMake permanent in ~/.bazelrc: build --compilation_mode=fastbuild
cd python/ray/dashboard/client && npm ci && npm run build && cd -cd python/ && pip install -r requirements.txtpip install -e . --verboseAdd to ~/.bazelrc if machine runs out of memory:
build --local_ram_resources=HOST_RAM*.5 --local_cpu_resources=4
build --disk_cache=~/bazel-cache
bazel info execution_rootpip install -e .