rebase

Rebase a Git branch onto a target branch and resolve conflicts.

10|5|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/JHostalek/dotclaude --skill rebase-jhostalek
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rebase
Source: https://github.com/JHostalek/dotclaude/tree/main/skills/rebase
Command: npx skills add https://github.com/JHostalek/dotclaude --skill rebase-jhostalek

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill updates branch history without merging, producing a clean linear branch that is ready to push while managing conflicts and post-rebase validation.

Core Features & Use Cases

  • Targeted Rebasing: Rebase the current branch onto a specified target branch, defaulting to the repository's master or main branch.
  • Conflict Resolution: Apply documented conflict heuristics when rebase conflicts occur and report the commits affected.
  • Migration Safety: Reconcile migration files after rebasing by re-chaining migrations and applying them to the local database when appropriate.
  • Quality Validation: Inspect and run the repository's configured quality gates because rebasing bypasses pre-commit hooks.
  • Safe Synchronization: Force-push the rebased branch using force-with-lease and summarize the completed operation.

Quick Start

Use the rebase skill to rebase the current branch onto the specified target branch, resolve conflicts, run quality gates, reconcile migrations, and push the result safely.

Frequently Asked Questions about rebase

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

FAQPage Schema
How do I rebase a branch and resolve conflicts to keep my git history linear?

Git rebase updates your current branch onto a target branch to produce clean linear history. It applies documented conflict heuristics to resolve rebase conflicts and reports the affected commits.

How do I reconcile database migration files after a git rebase?

Migration reconciliation after a git rebase re-chains migration files and applies them to your local database. This ensures database schema changes remain sequentially valid across the updated branch history.

Do I need to run quality gates after rebasing if I have pre-commit hooks?

Yes, you need to run quality gates after rebasing because the rebase process bypasses pre-commit hooks. The skill inspects and runs your repository's configured quality gates to validate the codebase.

What is the safest way to force-push a rebased branch to a remote repository?

Force-push a rebased branch using force-with-lease to safely synchronize with the remote. This prevents overwriting concurrent remote commits while pushing your updated linear history.

Can I rebase my current branch onto a specific target branch instead of main?

Yes, you can rebase the current branch onto a specified target branch. If no target is provided, the rebase defaults to the repository's master or main branch.