chunk-rebase

Merge trunk into the worktree and validate with tests before review.

3|1|Updated Jan 8, 2026
One-click install
npx skills add https://github.com/netguy204/vibe-engineer --skill chunk-rebase
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: chunk-rebase
Source: https://github.com/netguy204/vibe-engineer/tree/main/.agents/skills/chunk-rebase
Command: npx skills add https://github.com/netguy204/vibe-engineer --skill chunk-rebase

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Merge trunk into the worktree before review to ensure the REVIEW phase sees code that has already been synchronized with concurrent changes from other chunks.

Core Features & Use Cases

  • Integrates the current trunk/main into the worktree to prepare for review.
  • Guidance for resolving merge conflicts while preserving chunk goals.
  • Validates the integrated state by running tests to confirm compatibility before progression to REVIEW.

Quick Start

Commit any work, run the rebase step as part of the chunk workflow, and fix conflicts as directed.

Frequently Asked Questions about chunk-rebase

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

FAQPage Schema
How do I merge trunk into a git worktree before code review?

To merge trunk into a git worktree, you commit any current work and run the rebase step to integrate concurrent changes. This ensures the review phase sees synchronized code and validates compatibility by running tests.

What is the best way to resolve git merge conflicts during a chunk workflow?

Resolving git merge conflicts during a chunk workflow involves following guided resolution steps that preserve your specific chunk goals. The process integrates trunk changes into the worktree while maintaining the integrity of your concurrent work.

Why should I run tests after integrating trunk changes into my worktree?

You should run tests after integrating trunk changes to validate the integrated state and confirm compatibility before progression to the review phase. This test verification ensures the rebase step produced a stable, conflict-free codebase.

Can I use git worktree rebase for parallel chunk development?

Yes, git worktree rebase is designed for parallel chunk development. It performs pre-merge integration to synchronize your active worktree with concurrent changes from other chunks, ensuring the review phase evaluates fully integrated code.

Do I need to commit my work before merging trunk into the worktree?

Yes, you need to commit any current work before starting the rebase step. Committing ensures your changes are safely integrated with the trunk during the merge orchestration and prevents data loss during conflict resolution.