git-worktrees

This skill facilitates parallel software development by managing Git worktrees, allowing developers to work on multiple feature branches simultaneously without the overhead of constant branch switching or context loss. Designed specifically for the Langstar project, it enforces strict branch naming conventions and hierarchical dependency rules between parent and child issues. By automating the creation, maintenance, and cleanup of isolated worktree directories, it ensures that developers adhere to the project's issue-driven development cycle, where every pull request is explicitly tied to a specific issue.

• Enables simultaneous development of independent features and sub-issues by creating isolated working directories mapped to specific Git branches.

• Automates the complex task of branching sub-issues from parent issue branches, ensuring the PR hierarchy remains intact for easier code review and integration.

• Maintains project hygiene by providing structured cleanup commands for pruning stale worktrees and managing the wip/ directory.

• Supports standard git-worktree operations including add, list, remove, and prune with integrated support for complex branch naming formats like m<milestone>-p<parent>-i<issue>.

• Simplifies transition between different development tasks by allowing the agent to context-switch between worktrees instantly.

• Users should invoke this skill when starting a new task, managing sub-issue branching, or preparing a workspace for multiple simultaneous feature implementations.

• Inputs typically include the issue number, milestone information, and the targeted parent branch to ensure correct hierarchy alignment.

• Outputs consist of verified local worktree setups, branch synchronization commands, and automated cleanup notifications upon PR merging.

• The tool is best used in environments where developers frequently juggle top-level features alongside subordinate tasks within a milestone-based project structure.

• Integration with Git and the local shell environment is required to execute worktree commands directly. Users should ensure the wip/ directory is properly ignored in their local environment configurations to maintain repository cleanliness.