worktree-init
The worktree-init command creates isolated git worktrees for parallel development workflows, enabling users to work on multiple tasks simultaneously in separate Ghostty terminal panels. Use this when you need to develop several features or fixes concurrently without switching branches, automatically generating kebab-case branch names, setting up directory structures, and providing ready-to-run commands for each isolated Claude instance within its own worktree environment.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/davila7/claude-code-templates/HEAD/.claude/commands/worktree-init.md -o ~/.claude/commands/worktree-init.mdworktree-init.md
# Worktree Parallel Init Create multiple git worktrees for parallel development: $ARGUMENTS ## Instructions You are setting up parallel worktrees so the user can work on multiple tasks simultaneously in separate Ghostty terminal panels, each running its own Claude instance. ### Step 1: Validate Environment 1. Check this is a git repository: `git rev-parse --is-inside-work-tree` 2. Get the repo name: `basename $(git rev-parse --show-toplevel)` 3. Get the main branch name (check for `main` or `master`): `git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's@^refs/remotes/origin/@@'` — if that fails, default to `main` 4. Ensure working tree is clean: `git status --porcelain`. If dirty, warn the user and ask if they want to continue. 5. Fetch latest: `git fetch origin` ### Step 2: Parse Tasks Parse tasks from `$ARGUMENTS`. Tasks are separated by `|` (pipe character). If `$ARGUMENTS` is empty, use AskUserQuestion to ask the user to describe their tasks (they can provide multiple separated by `|`). For each task description: - Trim whitespace - Generate a kebab-case branch name: `claude/<kebab-case-task>` (max 50 chars, alphanumeric and hyphens only) - Generate a worktree directory path: `../worktrees/<repo-name>/claude-<kebab-case-task>` ### Step 3: Create Worktrees For each task: 1. Create the parent directory if needed: `mkdir -p ../worktrees/<repo-name>` 2. Create the worktree: ```bash git worktree add -b claude/<name> ../worktrees/<repo-name>/claude-<name> origin/<main-branch> ``` 3. Write a `.worktree-task.md` file inside the new worktree with this content: ```markdown # Worktree Task **Branch:** claude/<name> **Task:** <original task description> **Created:** <ISO date> **Source repo:** <path to main repo> ``` ### Step 4: Check for Dependencies If a `package.json` exists in the repo root, note that each worktree may need `npm install` (or the appropriate package manager). Check for: - `package-lock.json` → npm install - `yarn.lock` → yarn install - `pnpm-lock.yaml` → pnpm install - `bun.lockb` → bun install ### Step 5: Output Summary Display a clear summary table: ``` | # | Task | Branch | Path | |---|------|--------|------| | 1 | ... | claude/... | ../worktrees/repo/claude-... | ``` Then display ready-to-copy commands for Ghostty panels. For each worktree: ``` # Panel <N>: <task description> cd <absolute-path-to-worktree> && claude ``` If dependencies were detected, add a note: ``` # Note: Run <package-manager> install in each worktree before starting ``` Finally, remind the user: - Open a new Ghostty panel with `Cmd+D` (split right) or `Cmd+Shift+D` (split down) - When done with a task, use `/worktree-deliver` to commit, push, and create a PR - After merging all PRs, use `/worktree-cleanup --all` from the main repo
Use this agent when creating specialized Claude Code agents for the claude-code-templates components system. Specializes in agent design, prompt engineering, domain expertise modeling, and agent best practices. Examples: <example>Context: User wants to create a new specialized agent. user: 'I need to create an agent that specializes in React performance optimization' assistant: 'I'll use the agent-expert agent to create a comprehensive React performance agent with proper domain expertise and practical examples' <commentary>Since the user needs to create a specialized agent, use the agent-expert agent for proper agent structure and implementation.</commentary></example> <example>Context: User needs help with agent prompt design. user: 'How do I create an agent that can handle both frontend and backend security?' assistant: 'Let me use the agent-expert agent to design a full-stack security agent with proper domain boundaries and expertise areas' <commentary>The user needs agent development help, so use the agent-expert agent.</commentary></example>
Use this agent to create blog articles for aitmpl.com from Claude Code Templates components. Reads the component, asks the user to confirm details, generates SVG cover, HTML article, and updates blog-articles.json. Examples: <example>Context: User wants a blog for a component. user: 'Create a blog article for cli-tool/components/hooks/security/secret-scanner.json' assistant: 'I'll use the blog-writer agent to create the full blog article with cover image and proper structure' <commentary>The user wants a blog article from a component, use blog-writer for the full pipeline.</commentary></example>
Runs pre-deploy build checks on the dashboard. Validates Astro build, checks for common esbuild/JSX issues, verifies API endpoints compile, and reports errors with fixes. Use before merging PRs that touch dashboard/.
Regenerates the component catalog (docs/components.json) by running the Python script. Use this agent when components have been added, modified, or deleted to update the catalog. Handles the full regeneration process including download statistics fetching from Supabase.
CLI interface design specialist. Use PROACTIVELY to create terminal-inspired user interfaces with modern web technologies. Expert in CLI aesthetics, terminal themes, and command-line UX patterns.
Use this agent when creating CLI commands for the claude-code-templates components system. Specializes in command design, argument parsing, task automation, and best practices for CLI development. Examples: <example>Context: User wants to create a new CLI command. user: 'I need to create a command that optimizes images in a project' assistant: 'I'll use the command-expert agent to create a comprehensive image optimization command with proper argument handling and batch processing' <commentary>Since the user needs to create a CLI command, use the command-expert agent for proper command structure and implementation.</commentary></example> <example>Context: User needs help with command argument parsing. user: 'How do I create a command that accepts multiple file patterns?' assistant: 'Let me use the command-expert agent to design a flexible command with proper glob pattern support and validation' <commentary>The user needs CLI command development help, so use the command-expert agent.</commentary></example>
Applies researched improvements to Claude Code components, validates changes with the component-reviewer agent, and creates pull requests. The only agent that modifies files and creates PRs.
Migrates components (agents, commands, skills, hooks, settings, MCPs) from external GitHub repositories to claude-code-templates, validates them with component-reviewer, and regenerates the catalog