merge-protocol

Validate test suites and present merge, pull request, deferral, or abandonment options.

78|20|Updated Mar 9, 2026

Search Tags:#git #workflow #testing #pull request #code integration #merge

Ready to run

npx skills add https://github.com/NoobyGains/godmode --skill merge-protocol

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: merge-protocol
Source: https://github.com/NoobyGains/godmode/tree/main/skills/merge-protocol
Command: npx skills add https://github.com/NoobyGains/godmode --skill merge-protocol

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured and safe process for integrating completed code changes, ensuring tests pass and offering clear options for merging, creating pull requests, deferring, or abandoning work.

Core Features & Use Cases

Test Validation: Ensures the test suite is green before any integration action.
Integration Path Selection: Presents four distinct, clear options: local merge, pull request, deferral, or abandonment.
Worktree Management: Handles the cleanup of temporary worktrees when appropriate.
Use Case: After finishing a feature and confirming tests pass, you can use this Skill to decide whether to merge directly into main, open a PR, keep the branch for later, or discard the work entirely.

Quick Start

Use the merge-protocol skill to finalize the current work and select an integration path.

Frequently Asked Questions about merge-protocol

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

FAQPage Schema

How do I safely merge code changes only after tests pass?▼

You can enforce safe code integration by running a gated workflow that validates your test suite is green before allowing any merge, pull request creation, or branch abandonment actions.

What is the best way to manage git workflow options for a completed feature?▼

A structured merge protocol presents four distinct integration paths for completed features: local merge into main, opening a pull request, deferring the work, or completely abandoning the code changes.

How do I clean up temporary worktrees after finishing code integration?▼

When finalizing code integration through a gated workflow, the protocol coordinates with workspace isolation to properly tear down and clean up temporary worktrees after you select an integration path.

Can I use this merge protocol to abandon or defer a git branch instead of merging?▼

Yes, the protocol provides structured options to defer your branch for later work or abandon the code changes entirely, ensuring proper workspace teardown without forcing a direct merge into main.

Does this code integration workflow require any specific dependencies or tools?▼

No, this merge protocol operates with zero dependencies, relying only on your existing git workflow and testing suite to validate code quality before presenting structured integration options.