HARNEZ(1)General Commands ManualHARNEZ(1)

harnez

Name

harnez — manage coding-agent harnesses and engineering conventions from declarative YAML

Synopsis

harnez <command> [options]

Description

Keep a shared engineering setup reviewable while understanding what your agents consume and where their tools fail. This overview follows source revision 0a2cce5, reviewed on 16 September 2026; the newest source features may require a source build.

This reference covers the main setup, context, telemetry, and repository commands. Run harnez --help for the complete installed command tree and harnez <command> --help for all options.

Installation

$ go install ubunatic.com/harnez@latest

Commands

apply

Synchronize configured harnesses. Optional debloat presets disable selected capabilities in Claude Code, Codex, and Antigravity; recorded prior settings can be restored.

harnez apply [-c config.yaml] [--variant lite|full] [--debloat] [--debloat-preset minimal|aggressive]

init

Set up project instructions, documentation, and Makefile targets.

harnez init [--docs name,…] [--variant lite|full] [-m mode] [-y]

diff

Preview managed-block changes; -e reports drift through the exit status.

harnez diff [-e] [-c config.yaml] [-t ~/.claude]

status

Show applied configuration and tracker checks; --debloat reports context preset settings and ownership.

harnez status [--debloat] [-c config.yaml]

revert

Restore recorded pre-debloat settings for Claude Code, Codex, and Antigravity.

harnez revert --debloat

docs variant

Switch an installed document's source variant while preserving local content after its stop marker.

harnez docs variant <name> <lite|full> [-d project]

scan-docs

Scan child projects for managed documentation drift without writing changes.

harnez scan-docs <directory>

usage

Inspect token, session, and quota usage; -w opens the live dashboard and --offline uses local caches.

harnez usage [--json|--summary|-w] [--offline] [--agent name]

distill

Strip routine output noise and preserve the wrapped command's exit status; also accepts piped input.

harnez distill -- <command> [args…]

exec

Proxy a command's output without buffering and record shell-call telemetry.

harnez exec -- <command> [args…]

rate

Record tool quality feedback or a lightweight successful-session heartbeat.

harnez rate <tool> <1-5> <reason> [ticket]
harnez rate --ok

stats

Report tool frequency, scores, failure rates, and measured distillation byte savings; --auto filters to the current session.

harnez stats [--project name] [--auto] [--json]

find

Search active and archived issues with fuzzy terms and status filters, or report the next free number. Use -a for all matches.

harnez find issues "status:open query" [-a]
harnez find issues next

issues

Reserve new ticket numbers, list or validate tickets, and change lifecycle status. Status changes regenerate the index and commit by default; new creates an uncommitted draft.

harnez issues new <title>
harnez issues <start|block|close> <number> [reason]
harnez issues list [-a]
harnez issues lint

index

Regenerate the issue index and the documentation studies table from source files.

harnez index

assess

Inspect code and documentation metrics, token estimates, and repository feasibility.

harnez assess [path] [--json]

mode

Switch output terseness and synchronize the project instruction overlay.

harnez mode [level] [--status] [--clear]

dochistory

Analyze document token evolution and categories through Git history.

harnez dochistory [files…] [--json]

release

Run the configured version, build, signing, and forge publishing pipeline.

harnez release [--dry-run] [--bump patch|minor|major] [--continue]

clean

Remove managed blocks and keys while preserving unmanaged content.

harnez clean [-c config.yaml] [-t ~/.claude]

Configuration

target_dir: ~/.claude
docs: [golang, canary, spec]
effort: medium