The EkoHacks CLI: our everyday operations, automated one small command at a time.
We run a distributed team shipping open source to npm with strict TDD and trunk based development. Every operation we repeat by hand gets written down first, run by hand until it is boring, and then encoded here. The first one is releasing: the manual process lives in EkoLite's RELEASING.md, and ekohacks release is that document as a command.
The release command is built: the four stories in stories/ are implemented, each delivered red first — a failing test is committed and reviewed before any production code exists. The suite is the specification. The acceptance test for the whole is the next real EkoLite release, run with ekohacks release <version>.
The second command is ekohacks docs check, specified in stories/6-docs-check.md: a gate that fails when a package's docs drift from its shipped exports map, born from the EkoLite 0.4.0 release shipping a wrong public surface. Its acceptance test is the same command run inside EkoLite.
ekohacks docs sync is the other half, specified in stories/8-docs-sync.md: it writes the edits the check can prove — the entry-point block, the prose counts — and scaffolds a stub page for an entry point the docs just gained, leaving the prose to a person. stories/9-docs-draft.md specifies drafting that prose and opening a PR for a human to review; it is written down, not built.
The third command is ekohacks stories, specified in stories 11–13: the Linear board as a surface. fetch reads a whole column across pages, archive empties it once it has been read (reversible, batched, safe to re-run), and create pushes a new project's backlog from a JSON file with a --dry-run preview. It grew from the dojo's story-audit workshop scripts and the propi-o backlog push, and needs LINEAR_API_KEY in the environment. A mistyped team or column is a named stop rather than an empty result, specified in story 14 after user testing hit the ambiguity twice in an hour, and fetch with just the team prints the whole board, column by column (story 15).
- A tested core policy behind nullable infrastructure, in the style of James Shore's Testing Without Mocks: real wrappers around
git,ghandnpm, each with acreateNull()that answers with configurable responses and records what was asked of it. No mocks, no spies. - The CLI layer stays thin. Everything worth testing lives below it.
- TypeScript on Node 24, tests with Vitest, nothing bundled.