julia-vm-oss
julia-vm-oss contains 16 collected skills from AtelierArith, with repository-level occupation coverage and site-owned skill detail pages.
Skills in this repository
コミットして PR を作成・マージするよう依頼されたとき (/create-pr)。軽量フロー。多ファイル・多関心の大きな変更の仕上げには sjulia-finish-branch を使う。
Use when asked to clear, triage, fix, or resolve the open `bug`-labeled GitHub issue backlog for this repo (SubsetJuliaVM / AtelierArith/ailujsoi) — collect all open bug issues, fix each in parallel git worktrees, open PRs, and merge.
Use when triaging open AtelierArith/ailujsoi GitHub issues that lack a milestone assignment.
作業中に発見したバグや追加機能の必要性を GitHub Issue として起票するスキル。upstream julia では動くが sjulia で動かない / 結果が違うギャップ、バグ修正後の再発防止策を、最小 MWE と julia-vs-sjulia 出力比較付きで起票する。
Use when asked to merge a GitHub pull request and there may be open review comments, or when a PR has unresolved review threads that must be addressed before merging. Applies when the merge is blocked by reviewer feedback, by requested changes, or by open comment threads that need resolution.
Use after fixing (or while fixing) a bug in SubsetJuliaVM (sjulia) — wrong output, crash, or an existing-error class — when the fix should become durable, repo-wide prevention, or when the user asks for a prevention Issue or 再発防止.
Use when cargo nextest run --release is too slow, changing subset_julia_vm source causes many crates to recompile, or you need faster fixture-test iteration in SubsetJuliaVM.
Use when asked to run or compare the coprime pi benchmark in the SubsetJuliaVM repo across Julia upstream, juliars, sjulia VM typed/untyped, and Python 3.14 via uv, especially when results must be reflected in docs/vm/BLOG.md.
Use when adding base/stdlib Julia functions, writing or updating fixture tests, hitting a Julia compatibility gap, optimizing VM codegen/runtime, measuring VM performance, or preparing a commit/PR in the SubsetJuliaVM (sjulia) repo.
Use when adding, updating, or removing a workaround, ad-hoc special case, temporary shortcut, or compatibility shim in SubsetJuliaVM (sjulia) — or when the user mentions WORKAROUNDS.md or a `Workaround:` comment.
Use when finishing a SubsetJuliaVM (sjulia) branch and need to turn its changes into logical commits, open a pull request, and merge it in one continuous flow. Applies after a multi-file change is complete and the next step is commit → PR → merge.
Use when acting as the lead/orchestrator (管理者) for parallel implementation agents in this repo: an agent has opened a PR and reported completion, and you must review its diff, resolve merge conflicts with main, run the local gates (GitHub Actions is disabled — local checks are the ONLY gates), and drive the PR to a regular merge. Also applies when integrating several agent PRs in sequence.
Use when finishing a multi-file change in the SubsetJuliaVM (sjulia) repo and preparing commits, or when an existing branch has accumulated mixed concerns that should be separated before a PR.
Use when asked to run or compare the Mandelbrot benchmark in the SubsetJuliaVM repo across Julia upstream, juliars, sjulia VM typed/untyped, and Python 3.14 via uv, especially when results must be reflected in docs/vm/BLOG.md.
Use when a piece of work in this repo is finished — a PR merged, a bug fixed, an investigation concluded, a refactor or doc task wrapped up — and you are about to report completion to the user. Also use when the user says "postmortem", "振り返り", or asks what was learned or what should happen next.
Use the moment you discover a construct that runs in upstream `julia` but does not run correctly in sjulia — a parse error, an "unsupported"/"not implemented" runtime error, a MethodError on otherwise-valid syntax, a crash, or wrong output — even if the gap is incidental to your current task and even if you could easily route around it.