@harness-one/cli
v0.1.1
Published
CLI scaffolding + audit tool for harness-one
Maintainers
Readme
@harness-one/cli
CLI scaffolding + usage-audit tool for harness-one. Exposes the harness-one binary used to bootstrap new projects and print objective module-usage stats for existing ones.
The CLI ships as a standalone sibling package. Use pnpm dlx @harness-one/cli ... or install locally.
Install
# One-shot use without installing:
pnpm dlx @harness-one/cli init --modules core,tools,guardrails
# Or as a local dev dependency:
pnpm add -D @harness-one/cliNode 18+. Depends on harness-one (regular dependency; not peer) so the CLI resolves cleanly from a fresh node_modules.
Commands
harness-one init [--modules ...]— scaffold a starter project that imports the requested module surfaces. Templates emit modern subpath imports (e.g.from 'harness-one/tools',from '@harness-one/devkit'). The--modules eval/--modules evolveflags now route to@harness-one/devkit; the architecture-checker stays onharness-one/evolve-check.harness-one audit— scan a project directory forharness-one/*imports and print per-module import-site counts plus used/unused coverage.harness-one help [<topic>]— interactive module documentation browser. No network calls; everything ships with the binary.
Examples
npx harness-one init # interactive — choose which modules to scaffold
npx harness-one init --all # generate boilerplate for all available modules
npx harness-one init --modules core,tools,guardrails
npx harness-one audit # print per-module harness-one usage statisticsThe init command creates working starter files in a harness/
directory. The audit command scans your codebase for harness-one/*
imports and reports objective usage statistics (per-module import sites,
used/unused counts, and coverage percentage).
Programmatic API
The package also exports the parser + template registry for tools that want to embed the same scaffolding logic without shelling out to harness-one init.
import { parseInitArgs, renderTemplates } from '@harness-one/cli';Related
harness-one— the core runtime the CLI scaffolds against.@harness-one/devkit— eval + evolve dev-tools the templates link to.- Repository
README.md/CHANGELOG.md.
