rebase-main

Rebase the current feature branch onto origin/main with conflict handling and status reporting.

6|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/flurdy/agent-skills --skill rebase-main
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rebase-main
Source: https://github.com/flurdy/agent-skills/tree/main/skills/rebase-main
Command: npx skills add https://github.com/flurdy/agent-skills --skill rebase-main

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Rebase the current branch onto the latest main branch to incorporate updates from main into your feature branch.

Core Features & Use Cases

  • Rebase your feature branch onto origin/main to synchronize with updated main history.
  • Detect and guide you through conflicts during rebase, with steps to resolve and continue.
  • Verify that the branch is up-to-date and report outcomes, including commit counts and status.

Quick Start

From your feature branch, run the /rebase-main command to apply the latest main updates onto your branch.

Frequently Asked Questions about rebase-main

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

FAQPage Schema
How do I rebase my feature branch onto the latest main branch?

To rebase a feature branch onto main, run the command to fetch origin main and then rebase onto origin/main, integrating updated commits from main into your branch while keeping it synchronized.

What happens if there are conflicts when rebasing onto main?

When conflicts occur during a rebase onto main, the workflow detects them and guides you through resolution steps, allowing you to resolve the conflicts, continue the rebase, or abort it entirely.

When do I need to rebase a feature branch against main?

You need to rebase a feature branch against main when the main branch has progressed and you must incorporate those updates into your branch, such as when preparing a pull request or maintaining collaborative workflows.

Does this rebase workflow provide a status report after completion?

Yes, the rebase workflow verifies the branch is up-to-date and generates a final status report that includes commit counts and the synchronization outcome after applying main updates.

Can I abort a git rebase if conflicts become too complex to resolve?

Yes, if conflicts during the rebase process become too complex, the workflow includes an optional abort step to safely cancel the rebase and return your feature branch to its original state.