using-git-worktrees

Creates isolated git worktrees with branch setup and baseline test verification for parallel development.

Updated Oct 2, 2025
One-click install
npx skills add https://github.com/YuriiYInno/Innogram --skill using-git-worktrees-yuriiyinno
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: using-git-worktrees
Source: https://github.com/YuriiYInno/Innogram/tree/main/.codex/skills/using-git-worktrees
Command: npx skills add https://github.com/YuriiYInno/Innogram --skill using-git-worktrees-yuriiyinno

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Working on multiple features or parallel backend/frontend streams in one repository forces constant branch switching and risks mixing unrelated changes. This Skill sets up isolated git worktrees so each feature gets its own directory and branch without disturbing the current workspace. ## Core Features & Use Cases - Flexible Worktree Layouts: Create a single unified worktree, a backend-only or frontend-only worktree, or separate backend and frontend worktrees with matching branch naming conventions. - Safety Verification: Detects or prompts for the worktree directory, ensures it is git-ignored before creation, and enforces a clean backend/frontend project structure to prevent merge conflicts. - Baseline Validation: Auto-detects the project stack (Node.js, Rust, Python, Go), installs dependencies, and runs tests to confirm a clean starting point. - Use Case: A developer starting a large feature that touches both API and UI asks for separate worktrees, gets feature/<name>-backend and feature/<name>-frontend branches in isolated directories, each verified with passing tests before implementation begins. ## Quick Start Ask the AI to set up isolated git worktrees for a new feature, choosing unified, backend-only, frontend-only, or separate backend and frontend worktrees.

Frequently Asked Questions about using-git-worktrees

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a git worktree for a new feature branch?▼

Run git worktree add with a target directory and the -b flag to create a new branch, for example git worktree add .worktrees/my-feature -b feature/my-feature. The Skill automates this along with directory selection and safety checks.

When should I use separate backend and frontend worktrees?▼

Use separate worktrees for large features, parallel development by different sessions, or when backend and frontend have independent lifecycles. Tightly coupled or small features work better in a single unified worktree.

Where should git worktrees be stored in a project?▼

The Skill checks for an existing .worktrees or worktrees directory first, then any preference in codex.md, and otherwise asks the user. Project-local directories must be added to .gitignore before worktree creation.

Why must the worktree directory be in .gitignore?▼

If the worktree directory is not ignored, its contents get tracked by the parent repository, polluting git status and risking accidental commits. The Skill verifies with git check-ignore and commits a .gitignore update if needed.

What happens if baseline tests fail in a new worktree?▼

The Skill reports the failures and asks whether to proceed or investigate rather than continuing silently. This ensures new bugs can be distinguished from pre-existing failures before implementation starts.