{"owner":"oracle","repo":"graal","hasSkills":true,"hasMcp":false,"mcpConfig":null,"found":["AGENTS.md"],"skills":{"AGENTS.md":"# AGENTS.md\n\n## Orientation\n- GraalVM is split into `compiler/`, `espresso/`, `espresso-compiler-stub/`, `espresso-shared/`, `regex/`, `sdk/`, `substratevm/`, `sulong/`, `tools/`, `truffle/`, `visualizer/`, `vm/`, `wasm/`, and `web-image/`; each suite is managed with `mx`.\n- Read the local `AGENTS.md` or `README.md` for the suite you change.\n\n## Build & Quality\n- Run `mx` from the relevant suite directory. Default to the `vm` suite when no better target is obvious, for example `mx -p vm build`.\n- Common commands: `mx build`, `mx clean`, `mx unittest`, `mx help`, and `mx help <command>`.\n- Unless explicitly asked otherwise, run `mx build` with `--build-logs=silent`.\n- Never run multiple `mx build` or `mx checkstyle` commands concurrently in the same workspace. They can race on shared `mx build` outputs and produce misleading failures or corrupt intermediate artifacts.\n\n## Docs\n- Documentation sources live under `docs/`. Update the matching page for user-facing changes.\n- When working on documentation or editing Markdown files, consult `docs/AGENTS.md` for GraalVM documentation terminology, style, and Markdown conventions.\n- Apply `docs/AGENTS.md` to new or modified content only; do not refactor existing documentation in bulk just to match it.\n\n## Before Submitting\n- [ ] Ensure formatting and checkstyle pass (`mx checkstyle`).\n- [ ] Confirm tests or builds relevant to your suite succeed (`mx build`, targeted tests, etc.).\n- [ ] Verify documentation updates are included when behavior changes.\n- [ ] Flag and ask for extra permission for changes related to security (e.g., touching cryptographic code).\n"},"files":{"AGENTS.md":"# AGENTS.md\n\n## Orientation\n- GraalVM is split into `compiler/`, `espresso/`, `espresso-compiler-stub/`, `espresso-shared/`, `regex/`, `sdk/`, `substratevm/`, `sulong/`, `tools/`, `truffle/`, `visualizer/`, `vm/`, `wasm/`, and `web-image/`; each suite is managed with `mx`.\n- Read the local `AGENTS.md` or `README.md` for the suite you change.\n\n## Build & Quality\n- Run `mx` from the relevant suite directory. Default to the `vm` suite when no better target is obvious, for example `mx -p vm build`.\n- Common commands: `mx build`, `mx clean`, `mx unittest`, `mx help`, and `mx help <command>`.\n- Unless explicitly asked otherwise, run `mx build` with `--build-logs=silent`.\n- Never run multiple `mx build` or `mx checkstyle` commands concurrently in the same workspace. They can race on shared `mx build` outputs and produce misleading failures or corrupt intermediate artifacts.\n\n## Docs\n- Documentation sources live under `docs/`. Update the matching page for user-facing changes.\n- When working on documentation or editing Markdown files, consult `docs/AGENTS.md` for GraalVM documentation terminology, style, and Markdown conventions.\n- Apply `docs/AGENTS.md` to new or modified content only; do not refactor existing documentation in bulk just to match it.\n\n## Before Submitting\n- [ ] Ensure formatting and checkstyle pass (`mx checkstyle`).\n- [ ] Confirm tests or builds relevant to your suite succeed (`mx build`, targeted tests, etc.).\n- [ ] Verify documentation updates are included when behavior changes.\n- [ ] Flag and ask for extra permission for changes related to security (e.g., touching cryptographic code).\n"},"items":[{"name":"AGENTS.md","path":"AGENTS.md","title":"AGENTS.md","content":"# AGENTS.md\n\n## Orientation\n- GraalVM is split into `compiler/`, `espresso/`, `espresso-compiler-stub/`, `espresso-shared/`, `regex/`, `sdk/`, `substratevm/`, `sulong/`, `tools/`, `truffle/`, `visualizer/`, `vm/`, `wasm/`, and `web-image/`; each suite is managed with `mx`.\n- Read the local `AGENTS.md` or `README.md` for the suite you change.\n\n## Build & Quality\n- Run `mx` from the relevant suite directory. Default to the `vm` suite when no better target is obvious, for example `mx -p vm build`.\n- Common commands: `mx build`, `mx clean`, `mx unittest`, `mx help`, and `mx help <command>`.\n- Unless explicitly asked otherwise, run `mx build` with `--build-logs=silent`.\n- Never run multiple `mx build` or `mx checkstyle` commands concurrently in the same workspace. They can race on shared `mx build` outputs and produce misleading failures or corrupt intermediate artifacts.\n\n## Docs\n- Documentation sources live under `docs/`. Update the matching page for user-facing changes.\n- When working on documentation or editing Markdown files, consult `docs/AGENTS.md` for GraalVM documentation terminology, style, and Markdown conventions.\n- Apply `docs/AGENTS.md` to new or modified content only; do not refactor existing documentation in bulk just to match it.\n\n## Before Submitting\n- [ ] Ensure formatting and checkstyle pass (`mx checkstyle`).\n- [ ] Confirm tests or builds relevant to your suite succeed (`mx build`, targeted tests, etc.).\n- [ ] Verify documentation updates are included when behavior changes.\n- [ ] Flag and ask for extra permission for changes related to security (e.g., touching cryptographic code).\n","category":"root","tokens":406}]}