gitwise

English | Español

Python CLI for optimized Git workflows and coding agents integration.

gitwise gives coding agents bounded repository context, isolated branch workflows, and safe commit paths without hiding the underlying Git operations. Every command supports machine-readable JSON, and destructive operations expose dry-run or confirmation gates.

Requirements

• Python >= 3.10
• git >= 2.29
• macOS, Linux, or Windows

Install

Choose the channel you already trust:

Homebrew (macOS/Linux, recommended if you already use Homebrew):

brew install drzioner/tap/gitwise

Update later with brew upgrade gitwise. Uninstall with brew uninstall gitwise.

Installer script (auto-installs uv if needed):

curl -fsSL https://raw.githubusercontent.com/drzioner/gitwise/main/install.sh | bash

uv (if you already use uv):

uv tool install gitwise-cli

Windows PowerShell (PowerShell 5.1+):

irm https://raw.githubusercontent.com/drzioner/gitwise/main/install.ps1 | iex

From source (contributors only):

git clone https://github.com/drzioner/gitwise.git
cd gitwise
uv sync
uv run python -m gitwise doctor

Update through the same channel used to install:

brew upgrade gitwise                   # if installed via Homebrew (macOS/Linux)
uv tool upgrade gitwise-cli            # if installed via uv (any OS)
# or rerun the installer script

Uninstall:

brew uninstall gitwise                 # if installed via Homebrew
uv tool uninstall gitwise-cli          # if installed via uv (any OS)

Quick start

gitwise doctor
gitwise setup --dry-run
gitwise setup-agents --local --dry-run
gitwise summarize

The first three commands inspect or plan changes. Add --yes only after reviewing the plan.

Five workflows

1. Prepare a repository

Check the environment, preview modern Git defaults, and install the canonical agent layout:

gitwise doctor --json
gitwise setup --dry-run
gitwise setup --yes
gitwise setup-agents --local --dry-run
gitwise setup-agents --local --yes

setup and setup-agents do not change commit.gpgsign or user.signingkey.

2. Give an agent bounded context

Use structured summaries instead of feeding an agent an unbounded raw diff:

gitwise context --json
gitwise context --max-entries 50 --json
gitwise summarize --json
gitwise diff --stat --json

context --json defaults to 100 tree entries and reports tree_total plus tree_truncated when it omits entries.

3. Isolate agent work

Create a sibling worktree for a branch and use the path printed by the command:

gitwise worktree new feature/agent-task
gitwise worktree list --json

Use gitwise worktree remove feature/agent-task --dry-run before removal.

4. Review and commit safely

Inspect staged changes, scan for likely secrets, then create a conventional, GPG-signed commit through the repository's Git configuration:

gitwise diff --staged --scan-secrets
gitwise commit -m "fix: handle empty configuration"

gitwise blocks known signing and hook bypasses in generated agent rules. It does not create or replace signing keys.

5. Maintain the repo and check a PR

Keep maintenance explicit and inspect GitHub state without changing it:

gitwise audit --quick
gitwise clean --branches --dry-run
gitwise optimize --dry-run
gitwise pr checks
gitwise pr create --fill

pr delegates GitHub operations to gh; authenticate gh before using it.

Core commands

Support commands such as doctor, setup, status, clean, optimize, pr, commands, and schema serve those workflows. For all 30 commands, aliases, flags, and examples, see:

• Command reference (English)
• Referencia de comandos (Español)

JSON contract for agents

Global machine flags work before or after the subcommand:

gitwise --json status
gitwise status --json
gitwise commands --json
gitwise schema diff --json

Most JSON commands use the standard v3 envelope:

{"v":3,"ok":true,"command":"status","data":{},"hints":[],"errors":[]}

Use command and stable error code values for branching. Treat data as the command-specific payload. setup-agents retains versioned compatibility fields; inspect its current contract with gitwise schema setup-agents --json.

Safety model

• Git subprocesses scrub executable/config injection variables and use explicit timeouts.
• Destructive batch commands require confirmation; JSON mode returns an explicit gate.
• diff --scan-secrets and commit detect high-confidence credential patterns.
• setup-agents symlink creation is sandboxed to the target repository.
• CI runs ruff, basedpyright, pytest with a 75% coverage floor, pip-audit, and shellcheck.

See Security Policy for vulnerability reporting.

Documentation

• Documentation index (English)
• Indice de documentacion (Español)
• Contributing guide
• Guia de contribucion
• Security policy
• Politica de seguridad
• Code of Conduct
• Código de conducta
• Git conventions
• Convenciones Git

Environment Variables

Shell Completions

Generate completions script per shell:

gitwise completions bash > ~/.local/share/bash-completion/completions/gitwise
gitwise completions zsh > ~/.zsh/completions/_gitwise
gitwise completions fish > ~/.config/fish/completions/gitwise.fish

PowerShell (Windows / PowerShell Core): generate and dot-source the Register-ArgumentCompleter script. Add it to your $PROFILE for persistence:

gitwise completions powershell > gitwise.ps1
. .\gitwise.ps1
# or, to load on every session:
Add-Content $PROFILE ('. ' + ((Resolve-Path 'gitwise.ps1').Path))

Completion covers subcommands as the first token and per-command flags (--json, --dry-run, --max-count, etc.) thereafter.

Demo

Run the non-destructive current demo from a Git repository:

bash demo/script.sh

License

MIT - Deiner