nomadutil

CLI and library for local Git ship/release workflows. Stage everything, commit only when there are staged changes, push a branch, and (for release) create an annotated version tag — same behavior as classic shell helpers, runnable from any git repo.

Commands are grouped under modules so more tools can be added later. v1 ships the git module.

Install

Global CLI:

npm install -g nomadutil

As a library dependency:

npm install nomadutil

One-off without installing:

npx nomadutil git ship "fix login crash"

Local development

npm install
npm run build
npm link          # or: npm i -g .

Publish to npm

Publishing and GitHub Releases are automated via GitHub Actions when you push a version tag (v*.*.*). The tag version must match package.json (as with nomadutil git release 1.0.8 after bumping the package version).

One-time setup — configure Trusted Publishing on npmjs.com (no NPM_TOKEN secret):

1. Open the package → Access → Trusted Publishers → GitHub Actions
2. Set owner anomaddev, repository NomadUtil, workflow filename publish.yml
3. Leave Environment blank; allow npm publish

Then release:

# bump "version" in package.json first, commit, then:
nomadutil git release 1.0.8

That pushes tag v1.0.8, which runs:

• .github/workflows/release.yml — creates a GitHub Release (with generated notes)
• .github/workflows/publish.yml — publishes to npm via Trusted Publishing (OIDC)

Provenance is omitted while this repository is private (npm only supports provenance from public repos).

Manual publish (local):

npm install          # required — installs typescript for the build step
npm login
npm publish --access public

prepublishOnly runs tsc before packing. If you see exit code 127 / tsc: not found, dependencies were not installed (or an .npmrc omitted devDependencies — use npm install --include=dev).

CLI

Always operates on the current working directory’s git repository (not the tool install path).

Help and version

nomadutil --help          # or -h
nomadutil --version       # or -V
nomadutil git --help
nomadutil git ship --help

Flag	Description
-h, --help	Show usage (works at any command level)
-V, --version	Print the installed package version

Running nomadutil with no arguments also prints help (and exits non-zero).

Ship

Stage all changes, commit if anything is staged, push the branch:

nomadutil git ship "fix login crash"

Release

Same as ship, then create an annotated tag and push it. If package.json is present and its version does not match, release fails and asks whether to update package.json / package-lock.json and continue (-y skips the prompt):

nomadutil git release 1.0.0
nomadutil git release 1.0.0 "optional message"
nomadutil git release v1.0.0   # same tag as 1.0.0 → v1.0.0
nomadutil git release 1.0.1 -y # auto-bump package version on mismatch

Flags

Shared by git ship and git release:

Flag	Default	Description
--remote <name>	origin	Git remote
--branch <name>	main	Branch to push
--dry-run	off	Print what would run; no git writes
-y, --yes	off	git release only: auto-update package version on mismatch

Examples:

nomadutil git ship "wip" --dry-run
nomadutil git release 1.2.0 --remote origin --branch main

Exit non-zero on missing args or git failures.

Library

import { ship, release } from 'nomadutil'

await ship({ message: 'fix login crash' })

await release({ version: '1.0.0' })
await release({
  version: 'v1.0.0',
  message: 'optional message',
  remote: 'origin',
  branch: 'main',
  dryRun: false,
  cwd: process.cwd(), // optional; defaults to process.cwd()
})

Defaults

• Remote: origin
• Branch: main
• Tag prefix: v (versions 1.0.0 and v1.0.0 both become tag v1.0.0)
• Release message: Release vX.Y.Z when omitted
• Working tree: current working directory (process.cwd() / optional cwd)

Modules

Module	Commands
git	ship, release

More modules can be added later as nomadutil <module> <command>.