rebased

Resolve git rebase conflicts while preserving commit intent.

Updated Feb 2, 2026
One-click install
npx skills add https://github.com/dupe-com/skills --skill rebased
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rebased
Source: https://github.com/dupe-com/skills/tree/main/skills/rebased
Command: npx skills add https://github.com/dupe-com/skills --skill rebased

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually resolving git rebase conflicts when updating a feature branch against main is time-consuming, error-prone, and often leads to lost code intent if changes are blindly picked from one side. This skill automates the entire rebase workflow while preserving the purpose of all commits.

Core Features & Use Cases

  • Intent-preserving conflict resolution: Analyzes changes from both the main branch and the feature branch to merge conflicts semantically instead of discarding one side's changes.
  • Automated file handling: Regenerates lock files (bun.lockb, package-lock.json, yarn.lock) and generated files (migrations, snapshots) instead of requiring manual hand-merging.
  • Safe, guided workflow: Runs pre-flight checks to catch dirty working trees, in-progress rebases, and detached HEAD states, and never force-pushes or discards work without explicit user confirmation. Use case example: If your feature branch is 12 commits behind main with multiple merge conflicts across source code, lock files, and generated migration files, this skill will resolve each conflict while preserving your changes and main's updates, no manual merge work required.

Quick Start

Ask your AI agent to run the /rebased command to rebase your current branch onto origin/main and automatically resolve any merge conflicts that arise.

Frequently Asked Questions about rebased

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

FAQPage Schema
How do I automatically resolve git rebase conflicts when updating a feature branch?

To automatically resolve git rebase conflicts when updating a feature branch, you can use an intelligent tool that analyzes changes from both branches and merges them semantically to preserve the intent of all commits.

What is the best way to handle lock file and generated file conflicts during a git rebase?

Handling lock file and generated file conflicts during a git rebase is best achieved through automated regeneration, which rebuilds files like bun.lockb, package-lock.json, yarn.lock, and migrations instead of requiring manual hand-merging.

How can I safely rebase a branch without losing code intent or discarding changes?

Safely rebasing a branch without losing code intent requires a non-destructive workflow that validates repository state, preserves both upstream and branch changes, and requests explicit user confirmation before executing any force-push operations.

Does git rebase conflict resolution work if my working tree is dirty or has an in-progress rebase?

Git rebase conflict resolution tools typically run pre-flight checks to detect dirty working trees, in-progress rebases, or detached HEAD states, ensuring the repository is clean and stable before starting the automated conflict resolution process.

When do I need automated conflict resolution for git workflow synchronization?

Automated conflict resolution for git workflow synchronization is needed when your feature branch is multiple commits behind the main branch and contains overlapping changes across source code, lock files, and generated migration files that require intent-preserving merges.