Skip to content
Back to skills

Vibe Cherry Pick Integration

ASecurity

Safely integrates commits from parallel agent branches using sequential cherry-pick. Use after parallel work completes in isolated branches or worktrees.

  • 163 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 25, 2026
ai-agentsbashgitapi

Works with

  • api

Security analysis

A100/100

Scanned September 25, 2026

npx -y skills add ash1794/vibe-engineering --skill vibe-cherry-pick-integration --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Vibe Cherry Pick Integration?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Vibe Cherry Pick Integration
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ash1794-vibe-cherry-pick-integration/badge)](https://www.skillsdirectory.com/skills/ash1794-vibe-cherry-pick-integration)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: vibe-cherry-pick-integration
description: Safely integrates commits from parallel agent branches using sequential cherry-pick. Use after parallel work completes in isolated branches or worktrees.
user-invocable: true
---

# vibe-cherry-pick-integration

Parallel agents produce parallel branches. This skill integrates them safely without merge conflicts destroying work.

## When to Use This Skill

- Multiple agents completed work in isolated branches/worktrees
- Need to combine parallel work onto a single integration branch
- After `vibe-parallel-task-decomposition` dispatched work

## When NOT to Use This Skill

- Single branch with sequential work (just push)
- Merge conflicts are expected and desired for resolution
- The parallel work was all in the same files (this won't help — resolve manually)

## Steps

1. **Inventory branches** — List the branches and worktrees with completed work. Harnesses name them differently, so list rather than guess a pattern:
   ```bash
   git worktree list
   git branch --sort=-committerdate | head -20
   ```

2. **Determine integration order** — Cherry-pick in dependency order:
   - Independent tasks first (any order within batch)
   - Dependent tasks after their dependencies

3. **For each branch**:
   a. Identify commits to cherry-pick: `git log main..branch-name --oneline`
   b. Cherry-pick onto integration branch: `git cherry-pick <commit-hash>`
   c. If conflict:
      - Examine both sides
      - Resolve keeping the semantic intent of both
      - `git cherry-pick --continue`
   d. Run tests after each cherry-pick: `[test command]`
   e. If tests fail: fix before proceeding to next branch

4. **Verify integration** — Run full test suite after all cherry-picks

5. **Clean up** — Remove integrated branches if desired

## Output Format

### Cherry-Pick Integration

**Branches integrated**: X
**Commits cherry-picked**: Y
**Conflicts resolved**: Z
**Tests**: PASS/FAIL after integration

| Branch | Commits | Conflicts | Tests After |
|--------|---------|-----------|------------|
| agent/auth-stream | 3 | 0 | PASS |
| agent/api-stream | 2 | 1 | PASS |

### Conflict Resolutions
1. [File]: [How it was resolved]

### Final Status
- All tests passing: Yes/No
- Integration branch: [name]
- Ready to merge: Yes/No

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.