24 Zsh Plugins🔌 Every Developer & DevOps Engineer 🖥 Should Use in 2025

Published: (December 5, 2025 at 05:22 AM EST)
4 min read
Source: Dev.to

Source: Dev.to

Cover image for 24 Zsh Plugins🔌 Every Developer & DevOps Engineer 🖥 Should Use in 2025

Introduction

If you’re using Zsh with Oh My Zsh, you’re already ahead of the game. But are you leveraging the full power of its plugin ecosystem? Let me show you how to transform your terminal into a productivity powerhouse.

Prerequisites

Before we dive in, make sure you have:

  • Zsh installed – check with zsh --version (version 5.0 or higher recommended)
  • Oh My Zsh installed – if not, install it with:
sh -c "$(curl -fsSL https://raw.githubusercontent.com/ohmyzsh/ohmyzsh/master/tools/install.sh)"
  • Git installed – required to clone the custom plugins
  • Basic terminal knowledge – you should know how to edit files with nano, vim, or your preferred editor

To verify your setup:

# Check Zsh version
zsh --version

# Check if Oh My Zsh is installed
ls ~/.oh-my-zsh

# Check Git
git --version

Why Plugins Matter

The default Zsh installation with Oh My Zsh comes with just the git plugin enabled. While that’s a good start, you’re missing out on intelligent auto‑completions, helpful aliases, and productivity shortcuts that can save you hours every week.

The Setup

First, install two community plugins that are absolute game‑changers:

  1. zsh-autosuggestions (Fish‑like suggestions)
git clone https://github.com/zsh-users/zsh-autosuggestions ~/.oh-my-zsh/custom/plugins/zsh-autosuggestions
  1. zsh-syntax-highlighting (Real‑time command validation)
git clone https://github.com/zsh-users/zsh-syntax-highlighting ~/.oh-my-zsh/custom/plugins/zsh-syntax-highlighting

The Power Plugin List

Open your ~/.zshrc file and replace the plugins=() section with the following configuration:

plugins=(
  # Version Control
  git

  # Cloud & Infrastructure
  docker
  docker-compose
  kubectl
  helm
  terraform
  aws
  gcloud
  azure
  ansible

  # Programming Languages & Tools
  python
  pip
  node
  npm
  yarn
  golang
  rust

  # Productivity Boosters
  sudo              # Press ESC twice to add sudo to previous command
  extract           # Universal archive extractor (works with .tar, .zip, .gz, etc.)
  z                 # Jump to frequently used directories
  history           # Enhanced history commands
  command-not-found # Suggests package to install for missing commands
  vscode            # VS Code aliases and shortcuts

  # Community Plugins (must be last)
  zsh-autosuggestions
  zsh-syntax-highlighting
)

What Each Plugin Does

Cloud & Infrastructure Plugins

  • docker & docker-compose – auto‑completion for containers, images, and compose commands
  • kubectl – Kubernetes command completion and helpful aliases (k for kubectl, kgp for kubectl get pods)
  • helm – Helm chart management completions
  • terraform – Terraform command completion
  • aws / gcloud / azure – Cloud provider CLI completions

Language Plugins

  • python / pip – Python environment and package management shortcuts
  • node / npm / yarn – JavaScript ecosystem completions
  • golang / rust – Language‑specific tooling support

Productivity Plugins

  • sudo – Double‑tap ESC to prefix your last command with sudo
  • extract – Use extract <file> for any archive format – no need to remember tar flags
  • z – After using it for a while, type z project to jump to /home/user/dev/project
  • command-not-found – Suggests which package to install for missing commands (Ubuntu/Debian)

Community Plugins

  • zsh-autosuggestions – Shows suggestions based on your history as you type (press → to accept)
  • zsh-syntax-highlighting – Commands turn green if valid, red if invalid – catch typos before running

Activate Your Configuration

After updating your .zshrc, reload it:

source ~/.zshrc

Real-World Examples

Before

$ kubctl get pods  # Typo turns red immediately
$ # Realize mistake, fix it
$ kubectl get pods

After with plugins

  • The typo is highlighted in red instantly.
  • Start typing kub... and autosuggestions show kubectl get pods from history.
  • Press → to accept.

Or use the k alias: k get pods.

Directory Navigation

# Old way
$ cd ~/projects/work/important-service/

# With 'z' plugin (after visiting once)
$ z important
# Instantly jumps to ~/projects/work/important-service/

Archive Extraction

# Old way
$ tar -xzvf file.tar.gz
$ unzip archive.zip
$ tar -xjf file.tar.bz2

# New way with 'extract' plugin
$ extract file.tar.gz
$ extract archive.zip
$ extract file.tar.bz2
# All work the same way!

Performance Considerations

Having many plugins can slow down shell startup. If you notice lag:

  • Only enable plugins for tools you actually use
  • Remove language plugins for languages you don’t work with
  • Use time zsh -i -c exit to measure startup time

Bonus: Useful Aliases from These Plugins

Once activated, you get dozens of useful aliases:

Docker

  • dpsdocker ps
  • dpadocker ps -a
  • dcedocker-compose exec

Kubectl

  • kkubectl
  • kgpkubectl get pods
  • kgdkubectl get deployments
  • kafkubectl apply -f

Git

  • gstgit status
  • gcgit commit
  • gpgit push
  • gcogit checkout

Run alias in your terminal to see all available aliases.

Next Steps

  • Explore themes – try agnoster or powerlevel10k for a beautiful prompt
  • Custom aliases – add your own in ~/.zshrc or ~/.oh-my-zsh/custom/aliases.zsh
  • Discover more plugins – run ls ~/.oh-my-zsh/plugins/ to see the 350+ available plugins

Conclusion

A well‑configured terminal is a developer’s best friend. These plugins transform Zsh from a simple shell into an intelligent assistant that autocompletes, suggests, and validates as you type. The initial setup takes about 5 minutes, but you’ll save hours every week through improved efficiency and reduced context‑switching.

What plugins do you use? Drop your favorites in the comments!

Back to Blog

Related posts

Read more »