smithery/doodledood

rebase-on-main

Update main/master from origin, rebase current branch on it, resolve conflicts, and push.

Installation

$ npx skills add smithery/doodledood --skill rebase-on-main

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/doodledood · top by installs.

npx skills add smithery/doodledood

Browse all from smithery/doodledood

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,382 B
  • docs SUMMARY.md 111 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Perform a rebase workflow for the current branch:

Steps

  1. Identify the main branch: Check if main or master exists as the default branch
  2. Save current branch name: Store the current branch name for later
  3. Fetch latest from origin: Run git fetch origin
  4. Update main/master locally: Checkout main/master and pull latest changes
  5. Return to feature branch: Checkout the original branch
  6. Rebase on main/master: Run git rebase main (or master)
  7. Handle conflicts if any:

- If conflicts occur, analyze each conflicting file - Read the conflicting files to understand the context - Resolve conflicts intelligently by understanding both changes - Use git add to mark resolved files - Continue rebase with git rebase --continue - Repeat until all conflicts are resolved

  1. Push changes: Force push with lease using git push --force-with-lease

Important Guidelines

  • Always use --force-with-lease instead of --force for safety
  • When resolving conflicts, prefer keeping functionality from both sides when possible
  • If a conflict resolution is ambiguous, explain the choice made
  • Report a summary of what was done at the end (commits rebased, conflicts resolved, etc.)