eng

eng CLI

                                          __ __
                                         |  \  \
  ______  _______   ______        _______| ▓▓\▓▓
 /      \|       \ /      \      /       \ ▓▓  \
|  ▓▓▓▓▓▓\ ▓▓▓▓▓▓▓\  ▓▓▓▓▓▓\    |  ▓▓▓▓▓▓▓ ▓▓ ▓▓
| ▓▓    ▓▓ ▓▓  | ▓▓ ▓▓  | ▓▓    | ▓▓     | ▓▓ ▓▓
| ▓▓▓▓▓▓▓▓ ▓▓  | ▓▓ ▓▓__| ▓▓    | ▓▓_____| ▓▓ ▓▓
 \▓▓     \ ▓▓  | ▓▓\▓▓    ▓▓     \▓▓     \ ▓▓ ▓▓
  \▓▓▓▓▓▓▓\▓▓   \▓▓_\▓▓▓▓▓▓▓      \▓▓▓▓▓▓▓\▓▓\▓▓
                  |  \__| ▓▓
                   \▓▓    ▓▓
                    \▓▓▓▓▓▓

A modern, modular CLI tool for developer automation, dotfiles management, system utilities, and project codemods. Built in Go, designed for extensibility and productivity.

Features

• Git Repository Management — Bulk operations across multiple git repositories with intelligent branch detection
• Project Management — Organize and manage groups of related repositories as logical projects
• Dotfiles Management — Manage dotfiles via a bare git repo, with sync/fetch/checkout helpers
• Dotfiles Secrets — Backup and restore manifest-managed env files with Bitwarden Secrets Manager
• System Utilities — macOS/Linux helpers (kill port, kill process, proxy, update, compaudit fix)
• File Utilities — Find and delete files by extension, filename, or glob pattern
• Codemod Automation — Project codemods (lint setup, prettier, copilot instructions)
• Tailscale Helpers — Bring Tailscale service up/down
• GitLab Integration — Manage MR rules and authentication via glab CLI
• Config Management — Centralized config via Viper with automatic migration
• Auto-Update — Version checking and Homebrew auto-update support

Installation

Homebrew (Recommended)

brew tap eng618/eng
brew install eng

Go Install

go install github.com/eng618/eng@latest

From Source

git clone https://github.com/eng618/eng.git
cd eng
task install  # or: go install .

Usage

eng [command] [flags]

Quick Start

# Configure your development folder
eng config git-dev-path ~/Development

# Sync all git repositories
eng git sync-all

# Install dotfiles from your repo
eng dotfiles install

# Backup or restore manifest-managed dotfiles secrets
eng dotfiles secrets backup
eng dotfiles secrets restore

# Optional: run SSH setup directly if you want to prepare keys first
eng system setup ssh

# Setup a new development machine
eng system setup

# Check version and updates
eng version

Private Dotfiles Quickstart

For private GitHub dotfiles repositories, eng dotfiles install now validates dotfiles config first, checks core prerequisites, and only then runs GitHub SSH setup when the configured repo URL uses SSH.

If cloning fails due to SSH auth, run:

eng system setup ssh

Dotfiles Secrets

eng dotfiles secrets turns the manifest-driven bws backup and restore flow into a first-class CLI feature.

By default it looks for the manifest at $HOME/bin/secrets/server.manifest using the configured dotfiles worktree, and restores files relative to that worktree. The Bitwarden Secrets Manager project UUID can come from --project-id, BWS_PROJECT_ID, or the manifest comment header.

# Backup managed env values into Bitwarden Secrets Manager
eng dotfiles secrets backup

# Restore env files from their tracked .example templates
eng dotfiles secrets restore

# Validate manifest/template/secret consistency
eng dotfiles secrets doctor

eng system setup dotfiles now runs eng dotfiles secrets restore automatically after install when:

• the manifest exists at the configured dotfiles worktree (bin/secrets/server.manifest)
• BWS_ACCESS_TOKEN is set

If those prerequisites are not met, the restore step is skipped safely.

Available Commands

For detailed command documentation, see docs/COMMANDS.md.

Global Flags

--config string   # Config file (default: $HOME/.eng.yaml)
-v, --verbose     # Verbose output
-h, --help        # Help for any command

Documentation

• Command Reference — Complete documentation for all commands
• Architecture — Technical architecture and design
• Releasing — Automated release and Homebrew publication process
• Changelog — Version history and release notes

Support

• Issues: GitHub Issues
• Discussions: GitHub Discussions

Contributing

Contributions are welcome! Please follow these guidelines:

1. Fork the repository
2. Create a feature branch (git checkout -b feature/amazing-feature)
3. Make your changes following the Go style guidelines
4. Run validation: task validate (runs format, lint, and tests)
5. Commit your changes using Conventional Commits
6. Push to the branch (git push origin feature/amazing-feature)
7. Open a Pull Request

Development Commands

task build      # Build the binary
task install    # Install to $GOPATH/bin
task lint       # Run golangci-lint
task test       # Run tests with coverage
task validate   # Run format + lint + test
task changelog  # Generate changelog
task release    # Create a release (goreleaser)

See Taskfile.yaml for all available tasks.

Authors

• Eric N. Garcia — @eng618

License

MIT License © 2023–2026 Eric N. Garcia

Links

• GitHub Repository
• Releases
• Homebrew Tap