Bubbletea parity workflow

Skill dsisnero/crystal_forge/skills/bubbletea-parity-workflow

A set of skills to help with Crystal development

Install

npx -y skills add dsisnero/crystal_forge --skill bubbletea-parity-workflow

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Orchestrate Bubble Tea Go-vs-Crystal parity work. Use when you need to choose between Go golden generation, Crystal verification, example-layer fixes, shard fixes, or raw diagnostic fallback.

SKILL.md

2.1 KB, 474 tokens by cl100k_base, as published. Nobody here has run it

Bubble Tea Parity Workflow

This skill is the router for Bubble Tea parity work. It decides the path; the companion skills own the detailed implementation.

Route first

Need fresh Go goldens: use bubbletea-go-teatest-golden.
Need Crystal verification against existing goldens: use bubbletea-crystal-teatest-golden.
Drift is in example model / update / view / harness code: use bubbletea-port-example-parity.
Drift is under lib/: use crystal-shard-lib-patch.
No teatest harness exists on either side: use the raw fallback scripts here, then add proper golden coverage.

Default flow

Refresh Go goldens.
Sync the generated *.golden files into the Crystal repo.
Run Crystal verification against the synced fixtures.
Assign any remaining mismatch to example, src, or lib.

./scripts/run_teatest_golden_mode.sh \
  --go-workdir <go_dir> \
  --go-update-cmd '<go teatest command>' \
  --sync-goldens-from <go_golden_dir> \
  --sync-goldens-to <crystal_golden_dir> \
  --crystal-workdir <crystal_dir> \
  --crystal-verify-cmd '<crystal spec command>'

Fallback path

Use scripts/run_parity.sh only when a proper teatest/golden harness does not exist yet. Treat its byte-level output as temporary diagnostics, not final parity evidence.

Guardrails

Keep example behavior faithful to Go; do not edit examples just to match a fixture.
If no Go oracle exists, label the result as smoke verification rather than parity.
Prefer deterministic message injection over sleep-driven timing.
Keep temporary captures and caches under temp/.
If cache or module writes are blocked, rerun with escalation rather than inventing a different workflow.

Completion

Parity work is ready to close when:

The Go oracle matches the harness under test.
Crystal verification passes against the synced fixtures.
Any remaining mismatch has a clear owner.