github.com/JuliaLang/julia (link)

commit signals (802)

source signals (12)

• CLAUDE.mdvia claude-code

  <!--
  
  Include the contents of AGENTS.md
  
  https://code.claude.com/docs/en/claude-code-on-the-web#best-practices
  
  -->
  
  @AGENTS.md
  

• .claudedirectoryvia claude-code
• AGENTS.mdvia agents-md

  # Information for AI agents
  
  ## Module Organization
  - [`base/`](base/) - Core standard library (loaded at startup)
  - [`stdlib/`](stdlib/) - Standard library packages (can be loaded independently)
  - [`Compiler/`](Compiler/) - Julia compiler as a separate module (can be swapped)
  - [`src/`](src/) - C/C++ runtime and LLVM codegen
  - [`cli/`](cli/) - Command-line interface and loader
  - [`doc/`](doc/) - Documentation and User Manual
  
  ## Running Julia
  
  You should have a recent binary copy of julia in your `$HOME/.j

• doc/src/devdocs/agents/skills/test-changes/SKILL.mdvia unspecified

  ---
  name: test-changes
  description: Run and update Julia tests after changing test files. Use when adding to or modifying any test file under test/ or stdlib/**/test/.
  ---
  
  # Julia test changes
  
  Use this when you change or add a Julia test.
  
  - If you have changed a test (e.g. `foo`), run `make test-revise-foo` for the
    corresponding test to ensure that the test is still passing with your changes.
  - If you are adding a new test, add it to an existing test file. Do not create a
    new test file unless explici

• doc/src/devdocs/agents/skills/compiler-jl/SKILL.mdvia unspecified

  ---
  name: compiler-jl
  description: Develop and test Julia's Compiler.jl. Use when modifying Compiler/, debugging compiler behavior, or activating stdlib Compiler for reflection/native-codegen experiments instead of using sysimage Base.Compiler.
  ---
  
  # Compiler.jl development
  
  Use this when modifying `Compiler/` source, tests, or package metadata.
  
  ## Compiler modules in Julia
  
  During bootstrap, `Compiler/` is built into the sysimage as `Base.Compiler`.
  That in-sysimage compiler is what Julia normally uses f

• doc/src/devdocs/agents/skills/ci-timing/SKILL.mdvia unspecified

  ---
  name: ci-timing
  description: Compare a Julia PR's Buildkite job durations against recent CI history (per-job mean/min/max over the last N days). Use when asked whether a PR slows down or speeds up CI, or to check a build's timings against the weekly baseline.
  ---
  
  # CI timing analysis
  
  ```sh
  julia --startup-file=no --project=contrib/ci-timing contrib/ci-timing/ci_timing_compare.jl <PR-number>
  ```
  
  Prints a markdown table, slowest job first, plus a TOTAL row: each job's duration
  in the PR's `julia-pr` bu

• doc/src/devdocs/agents/skills/c-static-analysis/SKILL.mdvia unspecified

  ---
  name: c-static-analysis
  description: Run Clang static analysis on Julia's C/C++ runtime and codegen, and satisfy the GC-rooting checker. Use after modifying runtime/codegen .c/.cpp files under src/ (excluding headers), before opening a PR.
  ---
  
  # C/C++ static analysis (src/)
  
  Use this after you modify a runtime/codegen C/C++ source file under `src/` (not
  headers). Note that runtime changes also require a rebuild (`make -j`).
  
  Run static analysis checks:
  
  - First run `make -C src install-analysis-deps` t

• doc/src/devdocs/agents/skills/julia-syntax-lowering/SKILL.mdvia unspecified

  ---
  name: julia-syntax-lowering
  description: Develop and test JuliaSyntax and JuliaLowering in Julia's source tree. Use when modifying JuliaSyntax/ or JuliaLowering/, running package or targeted tests, or checking JuliaLowering execution.
  ---
  
  # JuliaSyntax & JuliaLowering development
  
  Use this when modifying `JuliaSyntax/` or `JuliaLowering/` source, tests, or
  package metadata.
  
  ## Testing JuliaSyntax
  
  Run package tests from the repository root:
  
  ```sh
  julia --project=JuliaSyntax -e 'using Pkg; Pkg.test()'

• doc/src/devdocs/agents/skills/doctests/SKILL.mdvia unspecified

  ---
  name: doctests
  description: Write and verify Julia `jldoctest` code blocks. Use whenever adding or changing a `jldoctest` block in a docstring (base/, stdlib/, Compiler/) or under doc/, and before opening a PR that touches doctests.
  ---
  
  # Julia doctests
  
  Use this whenever you add or modify any `jldoctest` code block.
  
  ## Writing
  
  Before writing new doctests, review `doc/src/devdocs/contributing/jldoctests.md`
  for best practices (filters, labels, setup code).
  
  ## Verifying
  
  If you changed any `jldoctest

• doc/src/devdocs/agents/skills/buildkite-logs/SKILL.mdvia unspecified

  ---
  name: buildkite-logs
  description: Fetch and inspect Julia Buildkite CI logs and artifacts without web sign-in, including the TTFX benchmark jobs. Use when debugging Julia CI failures, reviewing Buildkite jobs, investigating a TTFX regression, or when the Buildkite MCP is unavailable.
  ---
  
  # Reviewing Buildkite CI logs
  
  Use this when investigating Julia Buildkite CI failures, especially if the
  Buildkite MCP is unavailable. The recipe requires `gh`, `curl`, `python3`, and
  network access to GitHub and Buil

• doc/src/devdocs/agents/skills/external-deps/SKILL.mdvia unspecified

  ---
  name: external-deps
  description: Modify Julia's external dependencies and JLLs — patches under deps/patches/, version bumps in deps/, and JLL updates. Use when touching deps/ or any *_jll folder, including refreshing checksums.
  ---
  
  # External dependencies & JLLs
  
  Use this when modifying `deps/`, dependency patches, or a JLL.
  
  ## External dependencies (deps/, deps/patches/)
  
  When modifying external dependencies (patches in `deps/patches/` or version
  updates in `deps/`):
  
  1. Always test builds with `US

• .agentsdirectoryvia unspecified

ignorefile signals (0)

none