Results for “merge-tree”

Merge the winning agent's branch into base, archive losers, and clean up worktrees. Use when the user runs /hub:merge or asks to land the winning AgentHub result and tidy the session.

Merge the winning agent's branch into base, archive losers, and clean up worktrees.

Merge the winning agent's branch into the base branch, archive losing branches via git tags, and clean up worktrees after an AgentHub competition session.

Merge multiple fine-tuned models using mergekit to combine capabilities without retraining, covering SLERP, TIES-Merging, DARE, Task Arithmetic, linear merging, and production deployment strategies.

Merge the winning agent's branch into base, archive losers, and clean up worktrees.

Merge the winning agent's branch into base, archive losers, and clean up worktrees. Use when the user runs /hub:merge or asks to land the winning AgentHub result and tidy the session.

Use when closing a herdr workspace or worktree. Merges the workspace's completed, reviewed branch into the default branch, confirms origin is in sync, then removes the worktree and closes the workspace.

Sync main, rebase active worktrees, and clean up merged branches safely.

Tears down a merged PR's worktree and feature branch, verifying merge status on GitHub before deleting local and remote branches and switching back to the main worktree.

Use when merging a single GitHub pull request. Handles pre-flight checks, waits for CI, and executes the merge with the repo's default method or merge queue.

Sync the branch with the latest `origin/main`, merge `origin/main`, resolve conflicts end-to-end, then commit and push the current branch.

Integrate an exact reviewed PR under repository policy, choose truthful history semantics, and verify cleanup

Safely upsert, inspect, review, or explicitly merge the pull request for an issue-backed work branch

동시에 굴리던 여러 워크트리를 한 번에 통합합니다. 각 워크트리와 연결된 이슈를 확인하고 증거로 실제 해결 여부를 판정한 뒤, merge 를 시도하기 전에 충돌을 확정하고 계획한 순서대로 누적 검증해 순서 때문에 깨지는 경우까지 잡아냅니다. 충돌은 작업 브랜치 쪽에서 양쪽 의도를 보존하는 방향으로 해소해 승인받고, 비판 서브에이전트로 모호성을 걸러낸 다음 PR 을 merge 하고 통합 테스트로 재검증하고 이슈를 닫습니다. `$issue-merge`, "워크트리 전부 merge", "이슈들 통합", "PR 충돌 해결하고 합쳐줘" 요청과 issue-end 에서 merge 를 선택했을 때 사용합니다.

Audit all git worktrees in the current project. Use when the user asks about worktree status, which branches are merged, which have uncommitted changes, or which worktrees can be safely cleaned up.

Combines multiple pipe-format blocks from conversation context into one unified output, handling deduplication, source attribution, and confidence upgrades.

Merge multiple fine-tuned models using mergekit to combine capabilities without retraining. Use when creating specialized models by blending domain-specific expertise (math + coding + chat), improving performance beyond single models, or experimenting rapidly with model variants. Covers SLERP, TIES-Merging, DARE, Task Arithmetic, linear merging, and production deployment strategies.

Process the Refinery merge queue - collect agent work, detect and resolve conflicts, merge in dependency order, and verify integration.

Merge multiple fine-tuned models using mergekit to combine capabilities without retraining. Use when creating specialized models by blending domain-specific expertise (math + coding + chat), improving performance beyond single models, or experimenting rapidly with model variants. Covers SLERP, TIES-Merging, DARE, Task Arithmetic, linear merging, and production deployment strategies.

Merges mature lessons from a domain memory file into its instruction file, preserving knowledge with minimal redundancy.

Merges CSV/TSV data with an InDesign template to generate personalized PDFs like certificates, badges, and catalogs.

Safely analyzes and cleans up local git branches and worktrees by categorizing them as merged, squash-merged, superseded, or active work.

Facilitates a read-only standup across git worktrees, branches, or PRs to compare changes and produce one consolidation plan.

Use when you need to resolve an in-progress git merge/rebase conflict.

Use when you need to resolve an in-progress git merge/rebase conflict.

Manage document merger operations. Auto-activating skill for Business Automation. Triggers on: document merger, document merger Part of the Business Automation skill category. Use when working with document merger functionality. Trigger with phrases like "document merger", "document merger", "document".

Manage git worktrees using a centralized worktrees folder. Use for parallel development, PR reviews, or isolated work.

A powerful tree component for displaying hierarchical data with features like selection, checking, drag-and-drop, virtual scrolling, async loading, and search filtering.

Git Worktree Manager

Plans parallel agents or worktrees with isolated ownership, validation lanes, and merge rules. Use only for safely separable work.

Composite skill — one-pass cleanup of stale local branches, dead worktrees, merged branches, and abandoned remote PR branches. Chains `git fetch --prune` → `clean_gone` (kill [gone] branches) → worktree prune + offer-to-remove dead worktrees → list-and-delete branches merged to main and release → delete remote PR branches whose PRs merged >7 days ago. Use instead of running `clean_gone` alone — that only catches half the rot. Daily-friction composite; fires on "clean up branches", "branch hygiene", "stale worktrees", and on session start when local branch count > 30.

Pre-Merge Brief

Merges agent or review outputs into one deduplicated, evidence-linked, severity-ranked actionable report.

Multi-agent collaboration plugin that spawns N parallel subagents competing on the same task via git worktree isolation. Agents work independently, results are evaluated by metric or LLM judge, and the best branch is merged. Use when: user wants multiple approaches tried in parallel — code optimization, content variation, research exploration, or any task that benefits from parallel competition. Requires: a git repo.

Multi-agent collaboration plugin that spawns N parallel subagents competing on the same task via git worktree isolation. Agents work independently, results are evaluated by metric or LLM judge, and the best branch is merged. Use when: user wants multiple approaches tried in parallel — code optimization, content variation, research exploration, or any task that benefits from parallel competition. Requires: a git repo.