Results for “branches”

Lists local and remote git branches that are candidates for cleanup — merged but not deleted, and inactive branches with no commits in a configurable period (default 3 months). Use when user mentions "stale branches", "old branches", "branch cleanup", "prune branches", "dead branches", "unused branches", "inactive branches", "branch hygiene", or asks to "list branches to delete", "find stale branches", or runs /stale-branches command.

The English summary is being prepared. Showing the original description.

Find Git branches that have been merged or inactive for a chosen period. Preview cleanup candidates, exclude protected branches, and delete local or remote branches using a selected base branch and confirmation options.

• Find merged branches to clean up
• Review branches with no recent commits
• Clean up branches merged into a release

Find merged or inactive Git branches, preview cleanup candidates, and delete selected branches after confirmation. Choose a comparison branch, protect important branches with configurable rules, and optionally include remote branches.

• Previewing branch cleanup candidates
• Removing branches already merged into a release branch
• Finding branches with no recent commits

Deletes merged git branches (local and remote) and flags stale unmerged branches for manual review. Use when user mentions "cleanup branches", "delete merged branches", "prune old branches", "remove stale branches", "branch cleanup", or runs /cleanup-branches command.

The English summary is being prepared. Showing the original description.

Distribute edits across the appropriate branches in a Graphite stack, a chain of dependent branches. Use manual grouping when automatic absorption misplaces changes, then update commits, resolve restack conflicts, and verify the affected branches locally.

• Splitting working changes across stacked branches
• Moving a fix to the branch that owns the feature
• Assigning new files that automatic absorption skips

Curate Gaia bot crawler branches into real-skill catalog entries and clean up processed bot/* branches. Use when the user says: "process bot branches", "curate the crawl output", "clean up bot proposals", "run bot curation", "merge the crawler results", "review bot/* branches", "ingest crawler data", or explicitly types /gaia-bot-curate. Also triggers when the user asks to review pending `bot/*` branches, turn crawler JSON proposals into registry nodes, decide which crawled skills to accept vs reject, or batch-add skills from an automated crawl run. This skill handles the full pipeline: fetch remote bot branches, triage proposals, run `gaia dev` mutations, validate, open a PR, and delete consumed bot branches.

The English summary is being prepared. Showing the original description.

Clean up local Git branches and remote connections left after pull request reviews. The workflow checks unfinished work, preserves main and the current branch, and requests confirmation before force-deleting branches that have not been merged.

• Clean up branches after pull request reviews
• Remove contributor remotes other than origin
• Review unmerged branches before deletion

Create, track, switch, sync, and clean up Git branches. Covers naming conventions, safe branch switching with stash, upstream synchronization, and pruning merged branches. Use when starting work on a new feature or bug fix, switching between tasks on different branches, keeping a feature branch up to date with main, or cleaning up branches after merging pull requests.

The English summary is being prepared. Showing the original description.

Cleans up local git branches marked as [gone] (deleted on the remote but still present locally), including removing any associated worktrees. Use when the user says "prune branches", "clean up gone branches", "/prune-branches", or asks to delete stale local branches whose remotes are gone.

The English summary is being prepared. Showing the original description.

Manage complex Git histories with guidance for reorganizing commits, copying selected changes between branches, and finding bug-introducing commits. It also covers working on multiple branches at once and recovering lost commits through Git's reference history.

• Clean up commit history before opening a pull request
• Apply selected commits to another branch
• Find the commit that introduced a bug

Clean up a feature branch after its pull request is merged into main. Switch to main, pull the latest changes, and delete both local and remote branches, including branches merged through a squash merge.

• Cleaning up after a pull request is merged into main
• Deleting local and remote feature branches
• Removing branches after a squash merge

This skill should be used when user asks to "clean gone branches", "remove deleted local branches", "prune branches removed from remote", or explicitly invokes "clean-gone-branches".

The English summary is being prepared. Showing the original description.

Delete the `-bak` backup branches that `/prepare-merge` leaves behind, local and on origin, once the work they back up has merged. Use when the user says "remove my bak branches", "clean up bak branches", "delete the backups", or "/clean-bak-branches".

The English summary is being prepared. Showing the original description.

Organize dependent changes into a chain of branches and pull requests so reviewers can inspect one layer at a time. Use the GitHub CLI extension to create, update, synchronize, and merge the chain.

• Splitting a large change into reviewable pull requests
• Updating a lower branch and rebasing dependent branches
• Synchronizing local branches with GitHub

Manage dependent branches and pull requests with the GitHub gh-stack extension. Plan their order, inspect relationships, propagate changes through higher branches, and handle synchronization or conflict recovery using the documented workflow.

• Plan dependent changes across multiple pull requests
• Propagate lower-branch fixes through dependent branches
• Inspect and link existing pull requests

Manage parallel feature development with Git worktrees, separate working folders for different branches. Assign distinct ports, copy environment files, optionally install dependencies, and check for uncommitted changes and merged branches before removing outdated worktrees.

• Develop several feature branches at the same time
• Prepare a separate workspace for an urgent hotfix
• Give each AI agent its own branch and working folder

Manage version control through GitButler’s but CLI. Select files or hunks, meaning sections of a diff, for commits; organize dependent branches, split or combine history, resolve conflicts, and create pull requests using task-specific command workflows.

• Commit selected files or sections of a diff
• Split, combine, or reorder commits
• Arrange branches by dependency

Clean up Git worktrees, separate working folders for branches, by identifying merged branches and reviewing unmerged ones. Preview deletions, preserve protected branches, and receive a report of removed folders and reclaimed disk space.

• Clean up worktrees after merging branches
• Preview deletions and potential disk savings
• Review unmerged worktrees individually

Structures git branches and worktrees: keeps unrelated changes on separate branches, isolates each in its own worktree created so the repository's setup runs, records dependencies with git-machete, and recombines them into a temporary mixdown branch for local testing. Use before creating any branch or worktree in a codebase that works on more than one branch, including branching off the default branch to start a change; when starting work in a fork, clone, or third-party checkout; when choosing what a new branch should be based on; when a branch is growing a second unrelated concern; when deciding whether to stack branches or keep them independent; when preparing a change for a pull request or patch submission; when handed an existing worktree or branch to implement and commit in a fork; or when a local build needs several in-progress branches combined. Not needed where the repository clearly commits everything to the trunk, or holds notes or personal data rather than code.

The English summary is being prepared. Showing the original description.

Cascade merge changes through a chain of dependent branches. Use when updating stacked/chained PRs, propagating changes from a parent branch to all downstream branches, or when the user mentions "cascade merge", "propagate changes", "update dependent branches", or "merge to downstream branches".

The English summary is being prepared. Showing the original description.

Coordinate multiple AI agents with assigned owners, clear work boundaries, and a Kanban board that tracks progress. Organize separate branches or worktrees, collect test and handoff evidence, and define checks that must pass before combining their work.

• Assign parallel tasks to multiple AI agents
• Track progress and blockers across sessions
• Separate editing work across branches or worktrees

Compare changes across Git worktrees, branches, and pull requests through a facilitated discussion between agents. Produce one consolidation plan covering the target worktree, merge order, conflicts, and decisions that need human input.

• Planning how to combine work from multiple branches
• Comparing overlapping changes and competing implementations
• Reviewing recent worktrees together

Manage separate local development environments for multiple branches using the project's pnpm worktree CLI. Each environment has its own ports and dependencies, with options to share Supabase or isolate database changes for testing.

• Running and testing multiple branches at the same time
• Testing database migrations in a separate database
• Reusing an existing worktree for related fixes

Research new models and API capabilities offered by providers behind Pipecat services. Produce dated reports for each service and local committed branches for clear updates, with review commands and separate publishing steps.

• Checking providers for new models and API features
• Researching selected providers or service units
• Preparing local branches for clear updates