merge

Commits staged changes, rebases onto the base branch, and merges via workmux.

1|Updated May 4, 2026
One-click install
npx skills add https://github.com/wesbragagt/nixos-config --skill merge-wesbragagt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: merge
Source: https://github.com/wesbragagt/nixos-config/tree/main/home/skills/merge
Command: npx skills add https://github.com/wesbragagt/nixos-config --skill merge-wesbragagt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Finishing a feature branch involves repetitive git steps—committing staged work, rebasing onto the base branch, resolving conflicts, and merging—which are easy to do inconsistently or in the wrong order. ## Core Features & Use Cases - Automated Commit: Commits any staged changes using lowercase, imperative-mood messages without conventional commit prefixes. - Local Rebase: Rebases onto the base branch read from git config (defaulting to main) without fetching from origin, with guided conflict resolution that inspects recent base-branch changes per file. - Workmux Merge: Runs workmux merge --rebase --notification to merge and clean up the worktree and tmux window, with optional --keep and --no-verify flags. - Use Case: After finishing work in a workmux-managed worktree, invoke the command to commit, rebase onto main, and merge in one flow, optionally keeping the worktree alive with --keep. ## Quick Start Ask the assistant to run the merge command to commit staged changes, rebase onto the base branch, and merge the current branch with workmux.

Frequently Asked Questions about merge

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I commit, rebase, and merge a git branch in one step?

Run the merge command, which commits any staged changes, rebases onto the configured base branch, and then runs workmux merge to finish the branch. Flags like --keep and --no-verify are forwarded to workmux merge.

How does the rebase step choose the base branch?

The base branch is read from the git config key branch.<current-branch>.workmux-base. If no base branch is configured, it defaults to main, and the rebase always targets the local branch rather than origin.

What happens when rebase conflicts occur?

Before resolving a conflict, the workflow runs git log -p -n 3 on the base branch for each conflicting file to understand recent changes. The goal is to preserve both sides' changes, then stage the file and run git rebase --continue.

Can I keep the worktree and tmux window after merging?

Yes, pass the --keep or -k flag, which forwards --keep to workmux merge so the worktree and tmux window are not cleaned up. The --no-verify or -n flag similarly skips verification hooks.

Does the merge workflow fetch from the remote before rebasing?

No, the instructions explicitly prohibit running git fetch or rebasing onto origin/<branch>. The rebase only targets the local base branch, such as git rebase main.