aizen

🥈Silver

Aizen automates git worktree management for developers. It enables switching between worktrees without changing windows, improving workflow efficiency. Integrates with macOS terminal and supports Swift codebase.

197100Updated Today

Intermediate30min to implementautomation

Saves ~30 min per use

Quick InstallView Source

git clone https://github.com/vivy-company/aizen.git

Works with:

Claude

Overview

About This Skill

How to Use

["Install Aizen via Homebrew if not already installed: `brew install aizen`","Navigate to your project directory in the terminal","Run the Aizen command with your specific parameters (branch name, directory path)","Verify the worktree was created correctly by checking git status","Use Aizen to switch between worktrees as needed: `aizen switch [branch-name]`","Periodically run `aizen prune` to clean up stale worktrees (Tip: Add this to your weekly maintenance routine)"]

Setup & Installation

Quick Install

No install command available. Check the GitHub repository for manual installation instructions.

Alternative Install (Git Clone)

git clone https://github.com/vivy-company/aizen

Requirements

Claude Code or compatible AI agent
Works with: Claude

Quick Start Guide

Install the Skill

Copy the install command above and run it in your terminal.

Open Your AI Agent

Launch Claude Code, Cursor, or your preferred AI coding agent.

Try It Out

Use the prompt template or examples below to test the skill.

Customize

Adapt the skill to your specific use case and workflow.

Usage Examples

Prompt Template

Use Aizen to automate git worktree management for [PROJECT_NAME]. Create a new worktree for [BRANCH_NAME] in [DIRECTORY_PATH] if it doesn't exist, switch to it, and verify the worktree status. Then, list all existing worktrees and their current branches. Finally, clean up any stale worktrees by pruning them.

Example Output

I've automated the git worktree management for your Swift project 'TravelApp' using Aizen. First, I checked if a worktree for the 'feature/login-redesign' branch existed in '/Users/alex/Projects/TravelApp'. Since it didn't, I created it using the command:

```bash
aizen add feature/login-redesign /Users/alex/Projects/TravelApp/worktrees/login-redesign
```

The worktree was successfully created and I switched to it immediately. Running `git status` confirmed we're on the correct branch with 3 modified files ready for commit.

Next, I listed all existing worktrees in your project:

```
Worktree Path                                Branch
-------------------------------------------  ---------------------
/Users/alex/Projects/TravelApp/worktrees/dev main
/Users/alex/Projects/TravelApp/worktrees/bugfix/issue-452 bugfix/issue-452
/Users/alex/Projects/TravelApp/worktrees/login-redesign feature/login-redesign
```

Finally, I checked for stale worktrees by running:

```bash
aizen prune
```

No stale worktrees were found. All worktrees are properly linked to active branches. Your workflow is now optimized - you can switch between these worktrees instantly without opening new terminal windows or losing context.