git-extra-commands
git-extra-commands is a collection of 70+ utility scripts and aliases that extend git's functionality for common development tasks. It packages as a ZSH plugin but works in bash and other shells, offering helpers for branch management, commit analysis, and workflow automation.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | unixorn/git-extra-commands |
| Owner | unixorn |
| Primary language | Shell |
| License | Apache-2.0 — OSI-approved |
| Stars | 1.2k |
| Forks | 94 |
| Open issues | 7 |
| Latest release | v2025.11.6 (2025-11-06) |
| Last updated | 2026-07-06 |
| Source | https://github.com/unixorn/git-extra-commands |
What git-extra-commands is
A shell script collection (primarily bash/zsh) providing git subcommands for operations like branch cleanup, commit browsing with fzf, author tracking, and history manipulation. Licensed Apache 2.0; integrates with ZSH frameworks (oh-my-zsh, antigen, zgenom) and manual installation paths.
Get the git-extra-commands source
Clone the repository and explore it locally.
git clone https://github.com/unixorn/git-extra-commands.gitcd git-extra-commands# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- Installation method varies by shell framework (oh-my-zsh, antigen, zgenom, or manual $PATH additions); verify compatibility with your shell configuration before deployment.
- Many scripts have undocumented or external dependencies (e.g., fzf for preview scripts, expect for git-add-match, PyGTK for git-age); audit required scripts for availability in target environment.
- Scripts come from diverse external sources with potentially different update frequencies and maintenance status; consider pinning specific version (current: v2025.11.6) and periodically reviewing included script sources.
- Some scripts modify history (git-change-author, git-clone-subset, git-branch-rebaser); require team training and pre-commit hooks to prevent accidental misuse in shared repositories.
- ZSH plugin manager integration is convenience-focused; manual installation into /usr/local/bin or custom $PATH is straightforward but requires manual updates.
When to avoid it — and what to weigh
- Minimal shell scripting experience — Installation and customization require bash/zsh familiarity. Troubleshooting script failures may demand shell scripting knowledge; not suitable for developers who exclusively use GUI clients.
- Non-Unix/Linux environments without WSL — Primary target is Unix-like systems. Windows native support is limited (one script notes macOS-only functionality). Requires terminal/shell access.
- Organizations requiring vendored/auditable dependencies — Collection includes scripts sourced from many external authors with potentially varying quality and update cadence. Mixed provenance may complicate compliance or security audits in regulated environments.
- Projects relying on git GUIs or IDE integrations — These are command-line scripts. Integration with graphical clients or IDEs requires manual aliasing or wrapper setup; does not extend git's native GUI tools.
License & commercial use
Licensed under Apache License 2.0. Stated as OSI-compliant permissive license. Collection notes that included scripts from external sources may carry different licenses (inline in each script); collection maintainer respects author attribution and removal requests.
Apache 2.0 is a permissive OSI license permitting commercial use, modification, and distribution with attribution and liability waiver. However, individual scripts sourced from external authors may carry different terms; review embedded license headers in scripts used in commercial environments. No warranty provided. Consult legal review if uncertain about specific script provenance.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Active |
| Documentation | Adequate |
| License clarity | Clear |
| Deployment complexity | Low |
| DEV.co fit | Good |
| Assessment confidence | High |
Collection bundles shell scripts from diverse external sources; code provenance and review status per script is unclear. Scripts that manipulate git history (change-author, clone-subset) or accept user input (fzf-based tools) warrant review for injection vectors. No security audit mentioned. Users should review embedded script source code before running in high-security environments. Shell script execution inherits risks of bash/zsh environments; no sandboxing. Recommend pinning to specific release rather than auto-updating.
Alternatives to consider
GitHub CLI (gh)
Modern, actively maintained, single binary. Covers PR checkout, branch listing, and GitHub-specific workflows. Smaller dependency surface than 70+ shell scripts. Trade-off: less granular control and fewer offline repository analysis tools.
git-extras (Tj Holowaychuk)
Similar shell script collection with narrower scope (~40 commands). Centralized maintenance and simpler dependency model. Trade-off: fewer specialized scripts for branch analysis, fzf integration, and workflow patterns than git-extra-commands.
Custom git aliases + fzf
Build your own minimal set of shell aliases and fzf-based helpers tailored to team workflow. Reduces external dependencies and improves control. Trade-off: requires scripting effort and ongoing maintenance.
Build on git-extra-commands with DEV.co software developers
Evaluate git-extra-commands in a non-production ZSH environment first. Review script sources and external dependencies. If your team uses shell heavily and needs targeted git analytics or branch automation, this collection can reduce boilerplate. For CI/CD or security-critical workflows, use purpose-built tools instead.
Talk to DEV.coRelated open-source tools
Surfaced by semantic similarity across the DEV.co open-source index.
Related on DEV.co
Explore the category and the services that help you build with it.
git-extra-commands FAQ
Can I use this in production CI/CD pipelines?
What if a script has a bug or conflicts with my workflow?
Does this work on macOS, Linux, and Windows?
How do I keep my installation updated?
Software development & web development with DEV.co
Adopting git-extra-commands is usually one piece of a larger software development effort. As a software development agency, DEV.co provides software development services and web development expertise — pairing senior software developers and web developers with your team to design, build, and operate open-source devops software in production.
Ready to streamline your git workflow?
Evaluate git-extra-commands in a non-production ZSH environment first. Review script sources and external dependencies. If your team uses shell heavily and needs targeted git analytics or branch automation, this collection can reduce boilerplate. For CI/CD or security-critical workflows, use purpose-built tools instead.