Enforce Git worktree naming, numbering, deletion, and permission conventions.
npx skills add https://github.com/ghbvf/gocell --skill git-worktree-ghbvf
Please help me install this Agent Skill. Skill: git-worktree Source: https://github.com/ghbvf/gocell/tree/main/.gemini/skills/git-worktree Command: npx skills add https://github.com/ghbvf/gocell --skill git-worktree-ghbvf
Git Worktree conventions streamline safe and consistent worktree usage across teams, ensuring predictable naming, permissions compatibility, and safe deletion.
Apply the Git Worktree conventions before creating or deleting worktrees to ensure safe operations.
High-intent search queries and answers about installing and using this skill.
Git worktree conventions are standardized rules for creating, naming, numbering, and deleting worktrees. You need them when managing multiple per-feature branches to prevent naming collisions, avoid orphaned worktrees, and maintain a clean repository state across your team.
To safely create Git worktrees, apply enforced naming and baseline branch rules that prevent collisions and confusion. This standardization ensures predictable permissions compatibility and auditability when teams generate multiple per-feature worktree instances simultaneously.
The best way to manage worktree deletion is applying safe lifecycle conventions for Per-PR and temporary worktrees. This approach enforces deletion safety and permission compatibility, preventing orphaned worktrees and maintaining a clean repository state.
Per-PR worktrees cause collisions due to inconsistent naming and unsafe deletion practices. Prevent them by enforcing standardized worktree conventions for creation, numbering, and deletion safety to ensure predictable permissions compatibility and maintain a clean repository state.
You need a standard Git environment to apply worktree conventions. The conventions standardize safe worktree usage across teams by enforcing rules for creation, numbering, deletion safety, and permission compatibility without requiring specialized dependencies.
cenmiaoCreate isolated Git worktrees with branch naming and baseline tests.
Clawdi-AIMerge GitHub pull requests via squash after validating checks and branch status.
Gaku52Establish and enforce Git workflows with branching, commit, and PR conventions.
cameronraysmithEvaluate Git repository metrics and update CLAUDE.md with sparse checkout recommendations.
