원클릭으로 Manus에서 모든 스킬 실행

coverage-engine

스타4

포크3

업데이트2026년 7월 8일 22:47

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.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

Raild3x

Raild3x/ModulesOnRails

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Working on tools/coverage

Read tools/coverage/README.md first — it is the authoritative architecture doc (probe model, sentinel protocol, mutation semantics).

Layout boundary (load-bearing)

engine/ (Rust) and lune/core/ are repo-agnostic: nothing there may hardcode lib/, _Index, or .spec.luau. Layout knowledge lives only in lune/adapters/modules_on_rails.luau (this repo) behind the RepoAdapter interface in lune/adapter.luau.
The engine instruments by pure text insertion — existing bytes are never modified. Keep that invariant; byte offsets and file hashes depend on it.

Build & test

cd tools/coverage/engine && cargo build --release   # or --rebuild-engine on a run
cd tools/coverage/engine && cargo test              # unit + CLI + golden tests
lune run coverage.luau package=self --adapter=./tools/coverage/lune/adapters/coverage_self  # Lune core specs (from repo root)

Build/test release, not dev: full_moon recurses deeply and can overflow the stack in the dev profile.

Golden tests

engine/tests/golden/ pins exact map.json + instrumented output for engine/tests/fixtures/simple_pkg. Any intentional change to probe collection, id allocation, site keys, or splicing requires regeneration + diff review:

$env:UPDATE_GOLDEN = "1"; cargo test --test golden; Remove-Item Env:UPDATE_GOLDEN
git diff tests/golden/

Fixtures and goldens are pinned to LF via .gitattributes — never reformat or re-encode anything under engine/tests/fixtures/ or golden/.

Runtime gotchas

Lune 0.10.4 cannot parse const; that's why const-using packages route to the Studio pipeline. Don't add const to lune/ sources.
Studio results come back via the base64 stdout sentinel protocol ([[TM-COV ...]] lines in the adapter's runner template) — base64 is load-bearing (UTF-8 byte-slicing hazard), don't "simplify" it.
Mutation runs each mutant in a fresh child Lune process (lune/mutant_run.luau); a stop file .coverage/<pkg>/mutation.stop ends a run early keeping partials.

이 저장소의 다른 Skills

같은 저장소

new-package

Raild3x/ModulesOnRails

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.

2026-07-084

publish-package

Raild3x/ModulesOnRails

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.

2026-07-084

test-package

Raild3x/ModulesOnRails

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.

2026-07-084

write-docs

Raild3x/ModulesOnRails

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.

2026-07-084

write-specs

Raild3x/ModulesOnRails

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.

2026-07-084

name	coverage-engine
description	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.

Working on tools/coverage

Read tools/coverage/README.md first — it is the authoritative architecture doc (probe model, sentinel protocol, mutation semantics).

Layout boundary (load-bearing)

engine/ (Rust) and lune/core/ are repo-agnostic: nothing there may hardcode lib/, _Index, or .spec.luau. Layout knowledge lives only in lune/adapters/modules_on_rails.luau (this repo) behind the RepoAdapter interface in lune/adapter.luau.
The engine instruments by pure text insertion — existing bytes are never modified. Keep that invariant; byte offsets and file hashes depend on it.

Build & test

cd tools/coverage/engine && cargo build --release   # or --rebuild-engine on a run
cd tools/coverage/engine && cargo test              # unit + CLI + golden tests
lune run coverage.luau package=self --adapter=./tools/coverage/lune/adapters/coverage_self  # Lune core specs (from repo root)

Build/test release, not dev: full_moon recurses deeply and can overflow the stack in the dev profile.

Golden tests

$env:UPDATE_GOLDEN = "1"; cargo test --test golden; Remove-Item Env:UPDATE_GOLDEN
git diff tests/golden/

Fixtures and goldens are pinned to LF via .gitattributes — never reformat or re-encode anything under engine/tests/fixtures/ or golden/.

Runtime gotchas

Lune 0.10.4 cannot parse const; that's why const-using packages route to the Studio pipeline. Don't add const to lune/ sources.
Studio results come back via the base64 stdout sentinel protocol ([[TM-COV ...]] lines in the adapter's runner template) — base64 is load-bearing (UTF-8 byte-slicing hazard), don't "simplify" it.
Mutation runs each mutant in a fresh child Lune process (lune/mutant_run.luau); a stop file .coverage/<pkg>/mutation.stop ends a run early keeping partials.