Merge Bean

Name: Merge Bean
Availability: InStock
Author: beekeeper-lab

Automates bean feature branch merging into the test integration branch with reporting.

1|Updated Feb 7, 2026

Search Tags:#automation #git #merge #branch #code-review #bean

Ready to run

npx skills add https://github.com/beekeeper-lab/foundry --skill merge-bean

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Merge Bean
Source: https://github.com/beekeeper-lab/foundry/tree/main/.claude/skills/merge-bean
Command: npx skills add https://github.com/beekeeper-lab/foundry --skill merge-bean

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Safely merges a bean's feature branch into the test integration branch, ensuring changes are integrated in a controlled, auditable way and outcomes are reported.

Core Features & Use Cases

Validates bean readiness (status Done) and existence of the feature branch.
Performs a deterministic merge with --no-ff to preserve history and makes conflicts visible.
Pushes results to the remote and reports the merge commit hash or conflict details.

Quick Start

Execute the merge-bean command after a bean is verified as Done to merge its feature branch into test and report the outcome.

Frequently Asked Questions about Merge Bean

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

FAQPage Schema

How do I automate merging a feature branch into a test integration branch?▼

Automating a feature branch merge into a test integration branch requires validating branch readiness, executing a deterministic merge with --no-ff to preserve history, and pushing results to the remote while reporting the merge commit hash or conflicts.

What is the best way to handle merge conflicts when integrating feature branches?▼

Handling merge conflicts during feature branch integration is best managed by a merge process that makes conflicts visible during validation, reports conflict details clearly, and initiates rollbacks if needed to maintain branch stability.

How does a no-ff merge preserve git history when integrating code?▼

A no-ff merge preserves git history by creating an explicit merge commit even when fast-forwarding is possible, ensuring the branch context is maintained within the test integration branch history.

Can I integrate a code review branch before its status is marked as done?▼

Integrating a code review branch before its status is marked as done is not recommended, as the merge automation validates that the branch status is Done and the feature branch exists before proceeding with the integration.

Why does my automated git merge to test fail during validation?▼

An automated git merge to test fails during validation if the bean status is not marked as Done or if the feature branch does not exist, preventing unauthorized or incomplete changes from entering the test integration branch.

Do I need to manually push the merge commit after resolving git conflicts?▼

You do not need to manually push the merge commit after resolving git conflicts, as the automated merge process handles pushing results to the remote repository and reports the final merge commit hash during post-merge reporting.