nika-migration

Installation
SKILL.md

Migrating existing automation to Nika

A workflow makes its inputs, effects and execution evidence inspectable. Migration re-declares the intent so the checker can see it; a clean check does not authorize effects or prove that the migrated behavior is correct.

When to migrate (and when not to)

Migrate when the automation: calls an LLM anywhere · chains HTTP/file/JSON steps around AI output · is repeated (cron, CI, "run this every release") · needs a cost bound or an audit trail · is handed to someone else to run.

Do NOT migrate: one-shot commands · interactive debugging sessions · sub-second pure-shell pipelines with zero AI and zero HTTP (a Makefile that only compiles code is already in its best form).

The mapping table

Installs
9
GitHub Stars
92
First Seen
Aug 13, 2026