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

kymo-verify

스타7

포크1

업데이트2026년 6월 20일 23:45

Run kymostudio's verifiable stop condition — Python pytest + JS conformance parity — and report a clear PASS/FAIL with the failing output. Use as the goal check for any /loop or /goal on this repo, or to confirm a change is green before committing. Trigger phrases - "is it green", "verify the build", "check parity", "did the change break anything".

설치

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

Manus에서 실행

출처

kymostudio

kymostudio/kymostudio

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

다운로드

Manus에서 실행

Scope

$1 selects what to run (default all):

python — the Python reference impl + all golden/baseline/conformance gates.
js — the JS impl, including the read-only parity check against Python's goldens.
all — both (this is the real contract; JS parity is meaningless without Python green).

Run

From the repo root. Stream output; do not summarize away failures.

Python (run when scope is python or all):

cd packages/python && uv run --group dev python -m pytest -q

This single command gates: golden SVGs (test_diagrams.py, test_layout.py, test_edges.py, byte-for-byte), the BPMN corpus baseline (test_bpmn_corpus.py), and Python↔JS conformance goldens (test_conformance.py, test_bpmn_conformance.py).

JS (run when scope is js or all):

cd packages/js && npm test

This builds TS → dist/ then runs node --test, including conformance.test.js and bpmn-conformance.test.js which assert JS models equal the Python-written goldens.

Report

Emit a verdict block, nothing fancier:

GOAL: <PASS|FAIL>
  python: <pass|fail|skipped>   (<n passed, m failed>)
  js:     <pass|fail|skipped>   (<n passed, m failed>)

On FAIL, quote the first failing test name + its assertion diff. Do not regenerate any golden to make a test pass — that is a separate, deliberate action: use /kymo-golden, which first requires classifying the failure as intended vs a real regression.

If the failure is a JS conformance divergence, it is almost always a rounding mismatch — see /kymo-parity (fix JS toward Python with pyRound, never loosen the test).

이 저장소의 다른 Skills

같은 저장소

issue

kymostudio/kymostudio

Create or reformat a GitHub issue on kymostudio/kymostudio via the `gh` CLI. Picks the matching `.github/ISSUE_TEMPLATE` form (bug_report / feature_request), mirrors its fields into the body, sets the org Issue Type (Feature for feature_request) and auto-applies `#`-prefixed area labels from the existing repo labels. Use when the user says "tạo issue", "create issue", "mở issue", "open issue", "report bug", or asks to reformat an existing issue for this repo.

2026-06-247

fmt-sweep

kymostudio/kymostudio

Fix a red "Format & clippy" (rust.yml) CI job on kymostudio — auto-apply cargo fmt, verify the exact CI lint gate goes green, and ship the fix. Use when a Rust core CI run fails on the rustfmt or clippy step, or to pre-empt one before pushing Rust changes. Formatting is deterministic and non-semantic, so the fmt fix is safe to auto-apply; clippy failures are surfaced, not blindly rewritten.

2026-06-217

kymo-golden

kymostudio/kymostudio

Reconcile kymostudio's golden/baseline fixtures after an INTENTIONAL renderer, layout, or grammar change — classify each failing gate as intended vs a real regression, regenerate only the right tier, then prove parity held. Use when golden SVG tests, the BPMN corpus baseline, or the conformance suite fail because you deliberately changed output. Do NOT use to silence an unexplained red test.

2026-06-207

kymo-parity

kymostudio/kymostudio

Check or close Python↔JS feature parity in kymostudio via the conformance suite. Use when adding a feature to one impl (Python or JS) that the other needs, when a JS conformance test diverges from Python's golden, or to confirm a new behavior is locked in both languages. Encodes the rule that Python is the reference impl and JS reconciles toward it.

2026-06-207

loop-design

kymostudio/kymostudio

Design an autonomous agent loop for the kymostudio repo — pick a verifiable goal contract, wire trigger/actions/verification/memory, and pick a safe maturity level. Use when the user wants to automate recurring work here ("automate X", "set up a loop", "run this nightly", "keep checking Y"), or before writing a /loop, /goal, or .claude/workflows script. Loop engineering = designing the system that prompts the agent, not prompting by hand.

2026-06-207

name	kymo-verify
description	Run kymostudio's verifiable stop condition — Python pytest + JS conformance parity — and report a clear PASS/FAIL with the failing output. Use as the goal check for any /loop or /goal on this repo, or to confirm a change is green before committing. Trigger phrases - "is it green", "verify the build", "check parity", "did the change break anything".
argument-hint	[python\|js\|all]
allowed-tools	Bash Read

The single "is the goal contract satisfied?" command for this monorepo. A loop's /goal should call this; everything else is an action that runs until this passes.

Scope

$1 selects what to run (default all):

python — the Python reference impl + all golden/baseline/conformance gates.
js — the JS impl, including the read-only parity check against Python's goldens.
all — both (this is the real contract; JS parity is meaningless without Python green).

Run

From the repo root. Stream output; do not summarize away failures.

Python (run when scope is python or all):

cd packages/python && uv run --group dev python -m pytest -q

JS (run when scope is js or all):

cd packages/js && npm test

This builds TS → dist/ then runs node --test, including conformance.test.js and bpmn-conformance.test.js which assert JS models equal the Python-written goldens.

Report

Emit a verdict block, nothing fancier:

GOAL: <PASS|FAIL>
  python: <pass|fail|skipped>   (<n passed, m failed>)
  js:     <pass|fail|skipped>   (<n passed, m failed>)

If the failure is a JS conformance divergence, it is almost always a rounding mismatch — see /kymo-parity (fix JS toward Python with pyRound, never loosen the test).