A Rust workspace of focused CLI binaries for API testing, Git operations, agent workflow evidence, provider automation, planning, and desktop/media utilities. Shared crates keep JSON contracts, terminal UX, and cross-CLI behavior consistent.

Start here when choosing a binary. The source of truth for the current installable binary list is:

bash scripts/workspace-bins.sh

Completion obligations for those binaries are tracked in docs/specs/completion-coverage-matrix-v1.md.

Each crate is either a standalone CLI binary, a multi-binary crate, or a shared library used across the workspace.

• crates/nils-common: Shared cross-CLI utilities (including markdown payload validation and markdown-table canonicalization helpers).
• crates/nils-markdown: Tera-backed Markdown template engine, shared helpers, golden-test harness, and opt-in md-render binary for rendering .md.tera templates from JSON view data.
• crates/nils-term: Terminal UX helpers (TTY detection + progress rendering on stderr).
• crates/nils-test-support: Test-only helpers for deterministic workspace integration tests.
• crates/cli-template: Minimal example CLI for validating packaging and new-crate patterns.

• crates/api-testing-core: Shared library for the API testing CLIs (config/auth, history, reporting).
• crates/api-rest: REST request runner from JSON request specs, with history + Markdown reports.
• crates/api-gql: GraphQL operation runner for .graphql files (variables, history, reports, schema).
• crates/api-grpc: gRPC request runner from JSON specs, with history + Markdown reports.
• crates/api-websocket: Deterministic WebSocket request runner with history + Markdown reports.
• crates/api-test: Suite runner that orchestrates REST/GraphQL/gRPC/WebSocket cases and outputs JSON (and optional JUnit).

• crates/git-scope: Git change inspector (tracked/staged/unstaged/untracked/commit) with tree + optional file printing.
• crates/git-cli: Git tools dispatcher (utils/reset/commit/branch/ci/open).
• crates/git-summary: Per-author contribution summaries over a date range (adds/dels/net/commits).
• crates/git-lock: Label-based commit locks per repo (lock/list/diff/unlock/tag).
• crates/forge-cli: Provider-neutral forge CLI wrapping gh / glab for PR/MR + Issue lifecycle, repository label catalog maintenance, CI wait-checks, and the pr deliver macro (open draft → CI green → ready → merge).

• crates/macos-agent: macOS desktop automation primitives for app/window discovery, input actions, screenshot, and wait helpers.
• crates/fzf-cli: Interactive fzf toolbox for files, Git, processes, ports, and shell history.
• crates/memo: Capture-first memo workflow CLI with agent enrichment loop (add, list, search, report, fetch, apply).
• crates/zsh-kit: Runtime entrypoint for cloning/updating an operator-supplied Zsh repository, validating its setup hook, optionally writing ZDOTDIR bootstrap state, and dispatching shell-specific setup back to the repository.
• crates/image-processing: Image conversion CLI for svg/png/webp/jpg plus SVG validation with JSON/report outputs.
• crates/screen-record: macOS ScreenCaptureKit + Linux (X11) recorder for a single window or display with optional audio.

• crates/agent-runtime: Runtime-kit tooling binary (agent-runtime) for render, install, doctor, audit-drift, runtime state maintenance, skill listing, and PR/MR body rendering.
• crates/agent-docs: Deterministic policy-document resolver and auditor for Codex/agent workflows (audit, preflight, init, explain, list, remove).
• crates/agent-memory: Local agent memory-store resolver and manager (path, index, init-agent, init-persona, doctor, completion).
• crates/agent-out: Canonical $AGENT_HOME/out/ path generator and layout auditor for agent workflow artifacts.
• crates/agent-session: tmux-backed Codex and Claude Code session launcher for mobile handoff workflows.
• crates/agent-scope-lock: Deterministic edit-scope lock CLI for agent workflows (create, read, validate, clear).
• crates/web-evidence: Redacted static HTTP evidence capture for agent workflows (capture, completion).
• crates/agent-workflow-primitives: Multi-binary local-first agent workflow primitives (agent-run, browser-session, canary-check, docs-impact, heuristic-inbox, model-cross-check, repo-retro, review-evidence, review-specialists, skill-usage, test-first-evidence).

• crates/codex-cli: Provider-specific CLI for OpenAI/Codex workflows (auth, diagnostics, execution flows, Starship), with adapters over nils-common::provider_runtime.
• crates/gemini-cli: Provider-specific CLI lane for Gemini workflows, with adapters over nils-common::provider_runtime.
• crates/opencode-cli: Provider-specific CLI lane for OpenCode prompt and semantic-commit helpers migrated from zsh-kit.
• crates/semantic-commit: Helper CLI for staged context, Semantic Commit validation, commit amend, and cleanup commit workflows.
• crates/plan-tooling: Plan Format v1 tooling CLI (to-json, validate, batches, artifact-audit, split-prs, scaffold, completion), with bundle validation, advisory durable-artifact classification, deterministic/auto grouping primitives, and strict lane-metadata validation gates.
• crates/plan-issue: Plan issue orchestration binaries (plan-issue, plan-issue-local). The v3 issue-backed lifecycle is owned by record open, record post, record repair-dashboard, record audit, and record close (see docs/specs/issue-backed-plan-record-contract-v2.md). Task Decomposition orchestration remains available through start-plan, start-sprint, etc., with runtime lane metadata materialized from plan content + split-prs grouping results.

Contributors should treat nils-common as the shared helper boundary for cross-CLI primitives.

• Put reusable, domain-neutral helpers in crates/nils-common.
• Keep crate-local adapters for user-facing copy, warning style, exit-code mapping, and CLI-specific UX policy.
• During migration, preserve parity by keeping output text/warnings/colors/exit behavior byte-for-byte stable.
• Characterize behavior with tests before moving helper logic, then re-run affected crate tests after migration.

Detailed scope, API examples, migration conventions, and non-goals are documented in crates/nils-common/README.md.

Finalized shared-crate boundary and extraction lane ownership are tracked in docs/specs/workspace-shared-crate-boundary-v1.md.

Workspace doc retention scope and delete/keep decisions are tracked in docs/specs/workspace-doc-retention-matrix-v1.md.

Canonical completion architecture and contributor validation live in docs/runbooks/cli-completion-development-standard.md. Use DEVELOPMENT.md for required delivery checks.

Completion obligation coverage is tracked in docs/specs/completion-coverage-matrix-v1.md.

Assets:

• completions/zsh/: zsh completions (plus aliases.zsh)
• completions/bash/: bash completions (plus aliases.bash)
• wrappers/: dev-only wrapper scripts

Local shell setup:

1. Zsh: add completions/zsh/ to your fpath, then run compinit in your shell init.
2. Zsh (optional): source completions/zsh/aliases.zsh (see completions/zsh/aliases.zsh)
3. Bash: copy completions/bash/<command> into your bash-completion directory, or source them from your shell init.
4. Bash (optional): source completions/bash/aliases.bash (see completions/bash/aliases.bash)
5. Dev-only: add wrappers/ to your PATH (or symlink wrapper scripts into a bin directory).

Build release binaries into the default local bin directory:

./scripts/install-local-release-binaries.sh

Install only a specific binary:

./scripts/install-local-release-binaries.sh --bin git-scope

The default destination is ~/.local/nils-cli/bin; add it to PATH when needed:

export PATH="$HOME/.local/nils-cli/bin:$PATH"

Prebuilt release tarballs are published from v* tags after CI verifies the tagged commit. Download the matching nils-cli-<tag>-<target>.tar.gz asset from GitHub Releases, extract it, and add <extract_dir>/bin to your PATH.

Release archives include the compiled binaries, shell completions, aliases, license file, and third-party license/notice artifacts. After extracting release assets, follow the same setup flow from "Shell wrappers and completions".

Use DEVELOPMENT.md as the canonical contributor checklist for local setup, validation commands, generated artifacts, release maintenance, and crates.io publishing.

New CLI crate onboarding is documented in docs/runbooks/new-cli-crate-development-standard.md.