status

Shows clean, dirty, ahead, behind, and remote state for target repositories.

Usage

git-wrangler status [--repo <path>] [--json] [--no-fetch] [--guided]

What it does

Discovers Git worktrees under the current directory, or targets exactly one worktree with --repo, and displays a compact table of working tree state and upstream tracking state.

By default, status first runs git fetch --prune origin for each target repository so ahead/behind information is based on fresh remote-tracking refs. Use --no-fetch for offline or local-only runs.

Options

Flag	Required	Description
`--repo <path>`	Optional	Target exactly one repository instead of discovering recursively.
`--json`	Optional	Emit one JSON document on stdout. Suppresses normal dashboard output, colors, and progress.
`--no-fetch`	Optional	Use local remote-tracking refs without fetching `origin` first.
`--guided`	Optional	Interactively configure command options. Cannot be combined with `--json`.

Examples

# Analyze all repositories in the current directory
git-wrangler status

# Analyze a single repository
git-wrangler status --repo /path/to/repo

# Output status in JSON format
git-wrangler status --json

# Use local remote-tracking refs without refreshing origin
git-wrangler status --no-fetch

Notes

dirty — the working tree has uncommitted changes or untracked files
ahead N — you have N local commits not yet pushed to the remote
behind N — the remote has N commits you haven’t pulled yet
no remote — no upstream tracking branch is configured
Fetch failures are per-repository failures; JSON mode reports them in repositories[].