New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Merge Protocol

by NoobyGains in NoobyGains/godmode

A skill your agent uses when implementation is finished, tests are green, and you need to decide how to land the work - presents structured integration paths for local merge, pull request, deferral…

MITAuto-check passedDevelopment

Install Merge Protocol

skills CLI
$ npx skills add NoobyGains/godmode --skill merge-protocol -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install NoobyGains/godmode merge-protocol --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/NoobyGains/godmode.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/merge-protocol .claude/skills/merge-protocol && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
merge-protocol
GitHub stars
107
Token cost
~1.4k tokens
SKILL.md length
532 words
Files
1
Skills in repo
34
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when implementation is finished, tests are green, and you need to decide how to land the work - presents structured integration paths for local merge, pull request, deferral…

  • Works in 5 steps: Validate the Suite → Identify the Trunk Branch → Offer Integration Paths → …
  • Implementation is finished
  • SKILL.md covers Overview, Prime Directive, When to Use and Cognitive Traps, plus 5 more sections
  • Calls git, npm and gh

What it does

Merge Protocol is an agent skill from NoobyGains/godmode. Use when implementation is finished, tests are green, and you need to decide how to land the work - presents structured integration paths for local merge, pull request, deferral, or abandonment

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Pull requests and Git worktrees. The repository describes itself as: The AI development framework that thinks before it builds. 36 composable skills for Claude Code, Cursor, Codex, and OpenCode. The licence is MIT.

When your agent uses it

  • Implementation is finished
  • Tests are green
  • You need to decide how to land the work - presents structured integration paths for local merge

Example prompts

  • “/merge-protocol”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Validate the Suite
  2. Identify the Trunk Branch
  3. Offer Integration Paths
  4. Execute the Selected Path
  5. Worktree Teardown

What it can do on your machine

Read from SKILL.md and the folder at commit 441103a. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • npm
    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, npm and gh, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Merge Protocol loads about 1.4k tokens when it runs. Until then it costs about 52 tokens; SKILL.md has 532 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~52
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from NoobyGains/godmode at commit 441103a, republished under its MIT licence (© NoobyGains). 532 words, ~1,431 tokens.

Download SKILL.mdSave it as .claude/skills/merge-protocol/SKILL.md (or your agent's skills folder).
name
merge-protocol
description
Use when implementation is finished, tests are green, and you need to decide how to land the work - presents structured integration paths for local merge, pull request, deferral, or abandonment

Merge Protocol

Overview

Coordinate the final step of development: moving finished work into the mainline or disposing of it cleanly.

Core principle: Validate first, present choices, execute the selected path, then tidy up.

Announce at start: "I'm using the merge-protocol skill to finalize this work."

Prime Directive

NO INTEGRATION WITHOUT PASSING TESTS

No exceptions. No workarounds. No shortcuts.

When to Use

  • All planned implementation work is done and committed
  • The test suite runs green on the current branch
  • Review feedback (if solicited) has been resolved
  • You are ready to land, shelve, or abandon the branch
  • Following delegated-execution or task-runner completion
  • When a workspace-isolation branch needs teardown

Cognitive Traps

RationalizationTruth
"Tests were green an hour ago, no need to re-run"Any commit since then invalidates stale results. Re-verify now.
"Merging is mechanical — nothing breaks"Conflicts and integration regressions are real. Test the merged state.
"I'll remove the worktree tomorrow"Orphaned worktrees pile up and create confusion. Remove them immediately.
"Let me just merge — skip the menu"Always present all four paths. The human picks the workflow.
"Abandonment is obvious — no confirmation needed"Destroying work permanently demands explicit typed confirmation. Always.

The Workflow

Phase 1: Validate the Suite

Run the full test suite before anything else:

bash
# Execute the project's test runner
npm test / cargo test / pytest / go test ./...

On failure:

Suite failures detected (<N> failing). Resolution required before proceeding:

[Display failing tests]

Integration cannot continue until the suite is green.

Halt here. Do not advance to Phase 2.

On success: Proceed to Phase 2.

Phase 2: Identify the Trunk Branch
bash
# Determine the ancestor branch
git merge-base HEAD main 2>/dev/null || git merge-base HEAD master 2>/dev/null

Or confirm: "This branch diverged from main — correct?"

Phase 3: Offer Integration Paths

Present exactly these four choices:

Work is complete and verified. Select an integration path:

1. Merge into <trunk> locally
2. Push and open a Pull Request
3. Leave the branch untouched (I'll handle it myself)
4. Abandon this work entirely

Which path?

Keep it terse — no extra commentary.

Phase 4: Execute the Selected Path
Path 1: Local Merge
bash
# Switch to trunk
git checkout <trunk>

# Sync with remote
git pull

# Integrate the feature branch
git merge <feature-branch>

# Validate the merged state
<test command>

# Remove the merged branch
git branch -d <feature-branch>

Then: Proceed to Phase 5 (Worktree Teardown)

Path 2: Pull Request
bash
# Push the branch upstream
git push -u origin <feature-branch>

# Open the PR
gh pr create --title "<title>" --body "$(cat <<'EOF'
## Summary
<2-3 bullets describing the changes>

## Verification Steps
- [ ] <checklist items>
EOF
)"

Then: Proceed to Phase 5 (Worktree Teardown)

Path 3: Defer

Report: "Branch <name> preserved. Worktree remains at <path>."

Do not tear down the worktree.

Path 4: Abandon

Require explicit confirmation:

Permanent deletion warning:
- Branch <name>
- All commits: <commit-list>
- Worktree at <path>

Type 'abandon' to proceed.

Wait for the exact word.

After confirmation:

bash
git checkout <trunk>
git branch -D <feature-branch>

Then: Proceed to Phase 5 (Worktree Teardown)

Show full SKILL.md (216 more words)Show less
Phase 5: Worktree Teardown

Applies to Paths 1, 2, and 4:

Detect if the current branch lives in a worktree:

bash
git worktree list | grep $(git branch --show-current)

If so:

bash
git worktree remove <worktree-path>

Path 3: Worktree stays intact.

Decision Matrix

PathMergesPushesKeeps WorktreeRemoves Branch
1. Local mergeYesNoNoYes
2. Pull requestNoYesYesNo
3. DeferNoNoYesNo
4. AbandonNoNoNoYes (force)

Frequent Errors

Skipping validation

  • Consequence: Broken code lands on trunk, failing PR created
  • Correction: Always verify the suite before presenting paths

Open-ended prompting

  • Consequence: "What now?" leads to ambiguity and stalling
  • Correction: Present exactly four structured paths

Premature worktree removal

  • Consequence: Destroys workspace needed for PR or deferred work
  • Correction: Only tear down worktrees for Paths 1 and 4

Silent abandonment

  • Consequence: Work deleted without the human's awareness
  • Correction: Require typed "abandon" before any destructive action

Guardrails

Prohibited:

  • Proceeding when tests fail
  • Merging without validating the integrated result
  • Deleting branches without explicit confirmation
  • Force-pushing unless the human specifically asks

Mandatory:

  • Run suite before presenting paths
  • Present exactly four options
  • Obtain typed confirmation for Path 4
  • Tear down worktree only for Paths 1 and 4

Integration

Invoked by:

  • godmode:delegated-execution (final step) — After all delegated tasks finish
  • godmode:task-runner (final step) — After all execution batches complete

Complements:

  • godmode:workspace-isolation — Tears down the worktree created by that skill

© NoobyGains, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/merge-protocol of NoobyGains/godmode.

Open the folder on GitHubat commit 441103a

Compare with similar skills

Merge Protocol next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Merge Protocol compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Merge Protocol this skillNoobyGains/godmode107—~1.4kAutomated safety check: PassMIT
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
Pre-Release PR Triagejamiepine/voicebox57k—~3.1kAutomated safety check: PassMIT
Cap Feature Building WorkflowCapSoftware/Cap23k—~2.5kAutomated safety check: WarnCustom licence
Om Auto Fix Issuego-musicfox/go-musicfox2.6k1 repos~5kAutomated safety check: NotesGPL-3.0
Codewhale Landing Workflowcodewhale-hq/Codewhale41k—~1.6kAutomated safety check: PassMIT

Similar skills

  • Finishing a Development Branch

    obra/superpowers

    Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

  • Pre-Release PR Triage

    jamiepine/voicebox

    Sorts a backlog of open pull requests into must-merge, candidate, superseded and deferred, writes a triage doc and works the merge loop before a release.

    57k GitHub stars~3.1k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

  • Cap Feature Building Workflow

    CapSoftware/Cap

    Builds a Cap feature in an isolated Git worktree with disposable dev resources, verification, a recorded demo and a neutral pull request, started with /building.

    23k GitHub stars~2.5k tokensUpdated yesterday
    DevelopmentAuto-check: warnings

  • Om Auto Fix Issue

    go-musicfox/go-musicfox

    Fix or implement a tracker issue end to end from a single command — takes an issue id or a plain problem description (filed first via om-prepare-issue), classifies, then drives the bug autofix chain…

    2.6k GitHub starsUsed in 1 repo~5k tokens
    DevelopmentAuto-check: notes

  • Codewhale Landing Workflow

    codewhale-hq/Codewhale

    Decides how verified work should reach main, directly, in a worktree or on an integration branch, while keeping contributor credit and respecting merge gates.

    41k GitHub stars~1.6k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Clean Complete Branches

    jtenniswood/espcontrol

    Clean up completed Git branches and worktrees for this repository both locally and on GitHub.

    1.1k GitHub stars~820 tokensUpdated yesterday
    DevelopmentAuto-check passed

More from NoobyGains/godmode

All 34 skills in this repo

  • Activation

    NoobyGains/godmode

    A skill your agent uses when starting any conversation - establishes how to locate and invoke skills, mandating Skill tool usage before ANY response including clarifying questions

    107 GitHub stars~2.4k tokensUpdated 7 mo ago
    Auto-check passed

  • Agent Messaging

    NoobyGains/godmode

    A skill your agent uses when dispatching subagents, composing prompts for teammates, structuring handoff reports, or managing context boundaries between agents.

    107 GitHub stars~3k tokensUpdated 7 mo ago
    Auto-check passed

  • Codebase Research

    NoobyGains/godmode

    A skill your agent uses when building ANY feature within an existing project - search the current codebase for existing patterns, conventions, similar implementations, and established approaches…

    107 GitHub stars~3.2k tokensUpdated 7 mo ago
    Auto-check: notes

  • Completion Gate

    NoobyGains/godmode

    A skill your agent uses when about to declare work done, fixed, or passing, before committing or opening PRs - demands executing verification commands and reading their output before making any…

    107 GitHub stars~1.6k tokensUpdated 7 mo ago
    Auto-check passed

  • Comprehension Check

    NoobyGains/godmode

    A skill your agent uses when implementing any substantial feature, multi-file modification, or architectural change - produces a plain-language walkthrough of every alteration so the developer can…

    107 GitHub stars~1.5k tokensUpdated 7 mo ago
    Auto-check passed

  • Delegated Execution

    NoobyGains/godmode

    A skill your agent uses when executing implementation plans with independent tasks in the current session

    107 GitHub stars~2.4k tokensUpdated 7 mo ago
    Auto-check passed

Categories

Questions about Merge Protocol

What does Merge Protocol do?

A skill your agent uses when implementation is finished, tests are green, and you need to decide how to land the work - presents structured integration paths for local merge, pull request, deferral…. Merge Protocol is an agent skill from NoobyGains/godmode.

When should I use Merge Protocol?

Merge Protocol fits situations like: implementation is finished; tests are green; you need to decide how to land the work - presents structured integration paths for local merge.

How do I install Merge Protocol in Claude Code?

Run `npx skills add NoobyGains/godmode --skill merge-protocol -a claude-code`. Or copy the skill folder (skills/merge-protocol in NoobyGains/godmode) into .claude/skills/merge-protocol in your project. Claude Code loads it when a task matches its description.

How do I install Merge Protocol in Codex?

Run `npx skills add NoobyGains/godmode --skill merge-protocol -a codex`. Or copy the skill folder (skills/merge-protocol in NoobyGains/godmode) into .agents/skills/merge-protocol in your project. Codex loads it when a task matches its description.

Can I use Merge Protocol in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add NoobyGains/godmode --skill merge-protocol -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/merge-protocol, .gemini/skills/merge-protocol, .github/skills/merge-protocol and .opencode/skills/merge-protocol in your project.

What does Merge Protocol need to run?

Going by SKILL.md and its folder, Merge Protocol needs the command-line tools its instructions call (git, npm and gh).

Does Merge Protocol access the network?

SKILL.md contains no URLs. Its commands use git, npm and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Merge Protocol safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Merge Protocol use?

Merge Protocol is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Merge Protocol use?

About 1.4k tokens (SKILL.md is roughly 5.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Merge Protocol?

Skills that share tags, products or a category with Merge Protocol: Finishing a Development Branch (obra/superpowers, 296k stars), Pre-Release PR Triage (jamiepine/voicebox, 57k stars), Cap Feature Building Workflow (CapSoftware/Cap, 23k stars) and Om Auto Fix Issue (go-musicfox/go-musicfox, 2.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Merge Protocol?

NoobyGains (a GitHub user) maintains it in NoobyGains/godmode, which has 107 GitHub stars. The repository holds 34 skills in this directory. The repository was last updated on March 9, 2026.

Source: NoobyGains/godmode on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.