# Create Git Worktrees Faster

Starting parallel Git work can require branch naming, worktree setup, and remote tracking steps. This skill guides Claude, Codex, or Claude Code through a repeatable workspace initialization workflow.

## Install

```bash
npx skillstore add billchirico/git-workspace-init
```

## Metadata

- Status: approved
- Slug: billchirico-git-workspace-init
- Skillstore revision: r1
- Version status: missing
- Tree hash: 5505038c216575217e6809442fc6c609da7c19796449756483a889887ecaa728
- Author: BillChirico
- GitHub username: BillChirico
- License: MIT
- Repository: https://github.com/BillChirico/bills-claude-skills/tree/main/git-workspace-init/
- Ref: 5ab1d37e83436c6eef84de88573e142b94f2a4ad
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network, filesystem
- Quality score: 77
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/billchirico-git-workspace-init
- Manifest: https://skillstore.pages.dev/api/skills/billchirico-git-workspace-init/manifest

## Capabilities

- Prompts for a task type and short task description before branch creation.
- Formats branch names with conventional prefixes such as feat, fix, docs, and chore.
- Places new worktrees under a .worktrees directory at the repository root.
- Shows Git commands for creating a branch from a chosen base branch.
- Includes optional remote tracking setup with git push -u origin.
- Documents cleanup commands for removing worktrees and stale branch references.

## Use Cases

- Start Feature Work: Create a feature branch and isolated worktree before implementing new application behavior.
- Prepare Bug Fixes: Open a focused worktree for a fix while keeping the main checkout untouched.
- Run Parallel AI Tasks: Give an AI coding assistant separate workspaces for independent tasks in one repository.

## Prompt Templates

### Create a Feature Workspace

```
Use git-workspace-init for a feat branch named user authentication. Use main as the base branch.
```

### Create a Bug Fix Workspace

```
Create an isolated worktree for a fix called login validation error. Show the branch name and path before running commands.
```

### Use a Release Base

```
Initialize a docs worktree for API reference update from release/2.0. Confirm the Git commands before pushing the branch.
```

### Plan Parallel Worktrees

```
Plan two separate worktrees for a refactor and a test update. Use concise branch names and explain cleanup steps.
```

## Limitations

- Requires an existing Git repository with a configured remote.
- Assumes origin/main unless the user supplies another base branch.
- Does not inspect repository branch protection or team naming policies.
- Git commands can change local and remote repository state when executed.

## Best Practices

- Review the proposed branch name before any Git command runs.
- Confirm the base branch matches the repository workflow.
- Remove worktrees after merge to keep the repository clean.

## Anti Patterns

- Do not run the workflow outside a Git repository.
- Do not push a branch before confirming the target remote.
- Do not reuse an existing branch name for unrelated work.

## Security Audit

- Audited at: 2026-07-05T04:14:05.157\+00:00
- Summary: AI review found the high static score was caused by Markdown examples and intended Git workflow commands. The subprocess and shell examples use fixed Git commands or argument-list subprocess calls, with no prompt injection, stealth exfiltration, or arbitrary command execution evidence. The remaining risk is operational because the workflow can create worktrees, fetch from origin, and push branches when executed.

## Stats

- Views: 198
- Downloads: 7
- Favorites: 0
- Popularity score: 0