Menu
Use when triaging open AtelierArith/ailujsoi GitHub issues that lack a milestone assignment.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
コミットして 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.
作業中に発見したバグや追加機能の必要性を 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.
| name | github-milestone-triage |
| description | Use when triaging open AtelierArith/ailujsoi GitHub issues that lack a milestone assignment. |
Assign milestone-unassigned open issues to the best-fit existing milestone, or propose a new milestone when an issue clearly belongs to a missing category. Prefer the most specific milestone and document the reason.
gh issue list --state open --milestone none --limit 200
gh api repos/AtelierArith/ailujsoi/milestones --paginate \
--jq '.[] | "\(.title): \(.description // "no description") (open:\(.open_issues))"'
gh issue edit NUM1 NUM2 NUM3 --milestone "Exact Milestone Title"
gh issue list --state open --milestone none --limit 200
| Theme | Milestone |
|---|---|
AoT / juliars --emit-binary / pure-Rust backend | AoT Backend Expansion (2026-07) |
Compiler, runtime, dispatch, subtyping, JuliaType, specialization | Compiler and Runtime Modernization |
main regression, prevention, CI gates, product quality | Product Quality and Platform Hardening |
| Module scope, cache restore, binding resolution | Module Scope and Cache-Restore Parity (2026-07) |
| VM performance, typed-loop IR, broadcast kernel, runtime specializer codegen | VM Performance and Typed-Loop Optimizations (2026-07) |
Iterators, generators, collections, Memory, array literal semantics | Iteration, Generators, and Collection Semantics (2026-07) |
| Parser, lexer, lowering, macro, syntax compatibility | Parser, Lowering, and Syntax Compatibility Gaps (2026-07 follow-up) |
| Regex, display, version string, text representation | Display, Version, and Text Representation Parity (2026-07 follow-up) |
| Rust refactoring, clippy, helper consolidation, orphaned code | Rust Code Quality and Helper Consolidation |
| Pure Julia base/stdlib implementation | Pure Julia 化（継続） |
| Architecture debt, upstream Julia structural parity audit | アーキテクチャ負債・本家 Julia 構造パリティ監査 (2026-07) |
| REPL, module evaluation state, session lifecycle | REPL and Module Evaluation State (2026-07) |
| Register VM work | RegisterVM |
| Compile-time speed | CompileSpeed |
| Missing / three-valued logic parity | Missing and Three-Valued Logic Parity |
| Conflict | Prefer |
|---|---|
| Multiple milestones could fit | The most specific milestone (narrow scope beats broad scope). |
| Performance vs. feature work | The milestone that names the primary intent of the issue. |
| Documentation vs. UX text | Documentation if it changes reference/help content; Frontend/UX if it changes in-app strings. |
| Testing/CI/coverage improvements | Quality & Reliability or DevEx if it exists; otherwise Tech Debt only if it is maintenance. |
| Infrastructure vs. backend | Backend if it changes application logic; a new milestone only if it is observability/security/DevEx/quality & reliability. |
Before creating a new milestone, confirm:
Good names: "Observability & Monitoring", "Quality & Reliability", "Developer Experience".