beads-integrator

Merge Beads task branches into the base branch with serialized metadata recording.

Updated Jan 26, 2026

Search Tags:#automation #git #rollback #beads #worktree #merge #pipeline

Ready to run

npx skills add https://github.com/vega113/beads-orchestration-skills --skill beads-integrator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: beads-integrator
Source: https://github.com/vega113/beads-orchestration-skills/tree/main/beads-integrator
Command: npx skills add https://github.com/vega113/beads-orchestration-skills --skill beads-integrator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Merges per-task Beads branches into the base branch in a serialized, auditable manner, ensuring clean worktrees, validated merges, and task-state updates.

Core Features & Use Cases

Serialized merge flow for per-task branches into base
Automatic worktree creation, validation, and cleanup
Recording merge SHAs, verification outcomes, and follow-up tasks into Beads
Rollback and recovery procedures if a merge breaks the base branch
Clear handling of conflicts with consults to architects when needed

Quick Start

Run beads-integrator for the prepared task branch to merge it into the base and update the task with the merge details.

Frequently Asked Questions about beads-integrator

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

FAQPage Schema

How do I serialize merges for multiple task branches into a base branch?▼

Serialized merges for multiple task branches are automated by processing each branch sequentially into the base branch, ensuring validated merges and recording merge SHAs. This prevents concurrent integration conflicts and maintains a stable main branch.

What is the best way to automate git worktree cleanup after merging branches?▼

Git worktree cleanup after merging branches is handled automatically during the serialized merge flow. The process creates, validates, and cleans up worktrees for each task branch, ensuring a clean local environment before and after the remote push.

How do I rollback a base branch if an automated merge breaks the build?▼

Rollback and recovery procedures are triggered if an automated merge breaks the base branch. The merge flow detects the failure, reverts the base branch to its previous stable state, and records the failed verification outcome for further review.

Can I use automated merge pipelines with Beads orchestration runs?▼

Automated merge pipelines are designed specifically for Beads orchestration runs involving multiple task branches, reviewers, and QA steps. The pipeline handles base-branch detection, rebasing, and task-state updates directly within the Beads environment.

How are merge conflicts handled during serialized branch integration?▼

Merge conflicts during serialized branch integration trigger clear handling procedures that initiate consults to architects. The process pauses the automated merge flow, records the conflict state, and awaits manual resolution before retrying the integration.

What happens to task-state updates in Beads after a successful merge?▼

Task-state updates in Beads are applied automatically after a successful merge. The automation records merge SHAs, verification outcomes, and any follow-up tasks directly into Beads, ensuring full auditability and synchronization across the orchestration run.