consensus-loop:merge

Squash-merge a git worktree into the target branch with a structured commit message.

15|4|Updated Mar 15, 2026

Search Tags:#audit #retrospective #merge #consensus #commit-message #git-worktree #squash-merge

Ready to run

npx skills add https://github.com/berrzebb/consensus-loop --skill consensus-loop-merge

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: consensus-loop:merge
Source: https://github.com/berrzebb/consensus-loop/tree/main/skills/merge-worktree
Command: npx skills add https://github.com/berrzebb/consensus-loop --skill consensus-loop-merge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Squash-merge a worktree branch back into the target branch with a single, structured commit message after audit consensus and retrospective completion.

Core Features & Use Cases

End-to-end merge workflow with pre-merge validation
Generates a standardized, structured commit message for auditability
Phase-aware execution aligned with retrospective gates and consensus status

Quick Start

Instruct the orchestrator to squash-merge the current worktree into the target branch.

Frequently Asked Questions about consensus-loop:merge

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

FAQPage Schema

How do I squash-merge a git worktree with a structured commit message?▼

To squash-merge a git worktree, the workflow validates the worktree context, enforces pre-merge checks, and generates a standardized, structured commit message to finalize work as a clean, single-commit history.

What is the best way to finalize a git branch after audit consensus?▼

The best way to finalize a git branch after audit consensus is to apply a squash-merge that completes the retrospective phase and consolidates all worktree commits into one structured commit for full auditability.

When should I use a squash-merge for my git worktree integration?▼

You should use a squash-merge for git worktree integration when you need to finalize work after an audit consensus and retrospective completion, ensuring a clean history with a standardized commit message for traceability.

Does this squash-merge workflow require a completed retrospective phase?▼

Yes, this squash-merge workflow is phase-aware and requires retrospective completion and audit consensus before merging the worktree, ensuring that pre-merge validation gates are successfully passed.

What pre-merge checks are enforced during a worktree squash-merge?▼

During a worktree squash-merge, the workflow enforces pre-merge checks by validating the worktree context and verifying phase-aware execution aligned with retrospective gates and consensus status before creating the structured commit.

How do I generate a standardized commit message for a squash merge?▼

To generate a standardized commit message for a squash merge, the workflow automatically creates a structured commit during the worktree integration, ensuring end-to-end auditability and a clean single-commit history.