Create Git branches or worktrees from issue data or descriptions.
npx skills add https://github.com/lgtm-hq/claude-skills --skill branch-lgtm-hq
Please help me install this Agent Skill. Skill: branch Source: https://github.com/lgtm-hq/claude-skills/tree/main/skills/branch Command: npx skills add https://github.com/lgtm-hq/claude-skills --skill branch-lgtm-hq
This Skill simplifies the process of starting new branches or worktrees in Git by automating naming conventions and setup steps, reducing manual errors and effort.
feat/add-dark-mode and set up a worktree in a separate directory for concurrent work.Ask the AI to create a new branch from the current repository, specifying the change description or issue number as needed.
High-intent search queries and answers about installing and using this skill.
Git worktree management automates setting up sibling worktrees for parallel development in separate directories. This mechanism allows developers to concurrently work on multiple features or fixes without switching branches in a single working directory.
The best way to name git branches for feature and fix workflows is using semantic naming conventions derived from issue numbers or descriptive prompts. This approach ensures clean working states and consistent version control practices across documentation and bug fix tasks.
Yes, you can set up sibling git worktrees automatically. Worktree management creates separate directories for concurrent work, allowing parallel development on multiple features or fixes while maintaining a clean working state in the main repository.
Git branch automation supports various version control workflows, including feature, bug fix, and documentation tasks. It ensures proper branch naming conventions and clean working states, integrating seamlessly with existing version control processes.
You should use git worktrees instead of standard branch switching when you need to set up parallel development in separate directories. Worktrees allow concurrent work on multiple tasks without disrupting your current working state or requiring stashing.
jonnymuirManage Git worktrees and PRs with a dev-first branching model.
VYRE-StudiosCommit staged changes, push the branch, and open a pull request via GitHub CLI.
cattboyStage changes and commit with conventional messages enriched by GitHub context.
phenobarbitalCreate and manage isolated git worktrees for feature branches.