メニュー
Publish or version-bump a Wally package in this repo. Use when asked to publish, release, or bump a package version. Covers the publish script's non-interactive flags, the auto-generated init.luau, and CI workflow actions.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Work on the coverage system itself under tools/coverage (Rust full_moon engine or Lune orchestrator). Use when modifying instrumentation, probes, mutation testing, the report, adapters, or when golden tests fail. Covers building, testing, golden regeneration, and layout boundaries.
Create a new Wally package under lib/ in this repo. Use when asked to scaffold, add, or create a new package/module/library. Covers the scaffold script, the pure-Luau vs datamodel entry-point decision, and post-scaffold registration steps.
Run tests and coverage for a package in this repo. Use when asked to run tests, check coverage, run the test suite, or verify a package's specs pass. Covers command forms, flags, pipeline selection (Lune vs Roblox Studio), and reading the output.
Write or edit documentation in this repo — moonwave API docs, doc comments, or guide pages. Use when asked to document an API, add a guide, fix docs, or preview the docs site. Covers moonwave comment forms, guide-file conventions, classOrder registration, and previewing.
Write or modify tiniest test specs (.spec.luau) in this repo. Use when adding tests, fixing failing tests, or improving coverage for a package. Covers spec structure, the expect matcher API, snapshots, Roblox class shims, and the FakeIntermediary bridge for replicator tests.
| name | publish-package |
| description | Publish or version-bump a Wally package in this repo. Use when asked to publish, release, or bump a package version. Covers the publish script's non-interactive flags, the auto-generated init.luau, and CI workflow actions. |
npm run publish runs scripts/publish.py. It is interactive by default but
has non-interactive flags — prefer them when driving it as an agent:
python scripts/publish.py --package-name <name> --version-change patch --publish
# --version-change: major | minor | patch | none
# --no-publish = bump/prepare only; --yes = auto-accept prompts
Publishing to wally is an outward-facing, irreversible action — confirm
with the user before running with --publish/--yes.
version in lib/<name>/wally.toml (unless none).src/init.luau), it
generates a temporary passthrough init.luau that requires the entry
module and re-exports every export type. This file is marked
"AUTO-GENERATED ... do not commit" and is removed after — if one lingers in
the working tree after a failed publish, delete it.*.spec.luau / *.spec.lua and CLAUDE.md
files out of the package dir (and prunes dirs emptied by that, e.g.
Tests/) so specs and agent context never ship in the published package;
they are restored to the repo afterwards, even on failure.wally.toml,
default.project.json, README.md), runs wally publish, then restores.npm run readme (root README.md is
generated — never hand-edit).moonwave.toml.scripts/workflow_actions/ holds the GitHub Actions pieces:
publish_detect_changed_packages.py (which packages changed),
publish_resolve_version_change.py (bump type resolution),
validate_publish_setup.py. Check these before changing publish behavior —
local script and CI must stay in agreement.