eskit CLI — init, inspect, replay dev tooling #63

New issue

Closed

opened 2026-02-21 22:43:41 +00:00 by ash · 1 comment

ash commented

2026-02-21 22:43:41 +00:00

Owner

Why

Dev tooling makes the library feel like a product, not just code. Also critical for EMFlow code generation later.

Commands

eskit init — scaffold a new project with decider, events, store wiring
eskit inspect <stream> — show events in a stream (connect to SQLite/Postgres)
eskit replay <projection> — rebuild a projection from scratch
eskit stats — show stream counts, event counts, store size

Priority

Lower — ship after core features are solid. But design the interfaces now so CLI can plug in later.

Connection to EMFlow

This CLI is the bridge: EMFlow generates the slice definitions, eskit init scaffolds them into a running project.

Acceptance

CLI binary with cobra/urfave
init scaffolds minimal project
inspect reads from SQLite store
Works as both CLI and library

## Why Dev tooling makes the library feel like a product, not just code. Also critical for EMFlow code generation later. ## Commands - `eskit init` — scaffold a new project with decider, events, store wiring - `eskit inspect <stream>` — show events in a stream (connect to SQLite/Postgres) - `eskit replay <projection>` — rebuild a projection from scratch - `eskit stats` — show stream counts, event counts, store size ## Priority Lower — ship after core features are solid. But design the interfaces now so CLI can plug in later. ## Connection to EMFlow This CLI is the bridge: EMFlow generates the slice definitions, `eskit init` scaffolds them into a running project. ## Acceptance - [ ] CLI binary with cobra/urfave - [ ] `init` scaffolds minimal project - [ ] `inspect` reads from SQLite store - [ ] Works as both CLI and library