'branch' 검색 결과

Create and check Git branch names using Conventional Branch rules. Choose a prefix for the task, normalize the description, detect the repository’s base branch, and create and switch to the new branch.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Create a branch for a new feature or bug fix
• Check whether a branch name follows naming rules
• Include an issue number in a branch name

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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

Creates feature branches with optimized short naming, auto-incrementing, and commit type detection (feat/fix/refactor). Supports manual descriptions and auto-generation from uncommitted git changes. Use when user requests to create branch, start new branch, make branch, checkout new branch, switch branch, new task, start working on, begin work on feature, begin feature, create feature branch, run /create-branch command, or mentions "branch", "feature", "new feature", "feat", "fix", or "checkout".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Bring a Remotion branch up to date with the official main branch while preserving local changes and published history. Handle temporary change storage, merges, conflicts, validation, and a normal push when requested.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Merge the latest main into a feature branch
• Fast-forward a local main branch
• Update a pull request branch while preserving published history

Analyze current Git changes to choose a branch for a feature, release, or urgent fix. Create a descriptive name and switch to the new branch using Git Flow, a structured approach to managing development branches.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Create a branch for a new feature
• Separate release preparation changes
• Create a branch for an urgent production fix

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Update a working Git branch with the latest origin/main through a merge. The skill checks branch state, resolves conflicting edits with attention to both changes’ intent, runs project checks, and summarizes the resolution.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Bring the latest main changes into a feature branch
• Resolve conflicts while preserving both changes’ intent
• Sync remote feature branch updates before merging

Review captured agent sessions related to a GitButler branch, pull request, or change. Start with a chronological overview of previous discussions and actions, then inspect specific turns when the rationale or supporting evidence needs clarification.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Catch up on previous work on the current branch
• Review discussions related to a pull request
• Understand the reasons behind earlier changes

Create a pull request branch from the current branch while excluding .planning/ commits. This keeps planning documents out of the review so reviewers can focus on the code changes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Prepare a PR branch focused on code changes
• Exclude planning document commits from review
• Create a review branch for a chosen target branch

Create a git branch following Sentry naming conventions. Use when asked to "create a branch", "new branch", "start a branch", "make a branch", "switch to a new branch", or when starting new work on the default branch.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create a git branch following Sentry naming conventions. Use when asked to "create a branch", "new branch", "start a branch", "make a branch", "switch to a new branch", or when starting new work on the default branch.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Clean up the local workspace after a dev branch has been merged into main. Verifies the current dev branch is fully merged into origin/main, then switches to main, pulls the latest, deletes the local dev branch, and deletes the remote dev branch if it still exists. STOPS and warns the user if the current branch is not yet merged. Triggers: cleanup workspace, cleanup branch, delete merged branch, finish dev branch, post-merge cleanup

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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

Use when asked to publish the checked-out branch: commit and push it on whatever branch it is, the default branch included. Not for creating branches, PRs, force pushes, or pushing any other branch; when the request excludes the default branch, use commit-push-current.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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 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

Publish a Mastra preview package from a pull request or branch. Check the exact commit, confirm publication, monitor the release workflow, and report verified npm tags with a ready-to-copy installation command.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Publishing a preview package from a pull request
• Sharing a branch build under a custom npm tag
• Checking publication results and installation commands

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

Create or update a pull request from the current branch using its actual commits and changes. Fill the repository template with a concrete description, reviewer test steps, and accurately reported checks, then push the branch.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Opening a pull request from the current branch
• Updating a pull request after additional changes
• Writing reviewer test steps from the actual changes

Prepare Handsontable changes for review by checking branch names, running required checks, and creating or updating draft pull requests. Fill the project template with test evidence and add changelog entries in the required order.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Submitting a feature or documentation branch for review
• Updating a pull request description with test evidence
• Adding a changelog entry after opening a pull request