Syncs feature branches with origin/main using structured merge workflows and conflict resolution.

Install

mkdir -p .claude/skills/pull && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/9510" && unzip -o skill.zip -d .claude/skills/pull && rm skill.zip

Installs to .claude/skills/pull

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Pull latest origin/main into the current local branch and resolve merge
71 chars · catalog descriptionno explicit “when” trigger
Intermediate

Key capabilities

  • Pull latest changes from origin/main
  • Resolve merge conflicts
  • Sync feature branches
  • Maintain history integrity

How it works

It fetches the latest refs and performs a merge-based update from origin/main, resolving conflicts safely.

Inputs & outputs

You give it
Local feature branch
You get back
Updated branch with origin/main changes

When to use pull

  • Sync a feature branch with main
  • Resolve complex merge conflicts
  • Update local environment before pushing code

About this skill

Pull

Workflow

  1. Verify the git status is clean or commit/stash changes before merging.
  2. Ensure rerere is enabled locally:
    • git config rerere.enabled true
    • git config rerere.autoupdate true
  3. Confirm remotes and branches:
    • Ensure the origin remote exists.
    • Ensure the current branch is the one to receive the merge.
  4. Fetch latest refs:
    • git fetch origin
  5. Sync the remote feature branch first:
    • git pull --ff-only origin $(git branch --show-current)
  6. Merge origin/main:
    • Prefer git -c merge.conflictstyle=zdiff3 merge origin/main
  7. If conflicts appear, resolve them, then stage the resolved files and complete the merge.
  8. Verify with project checks appropriate to the scope.
  9. Summarize the merge, including the main conflicts and how they were resolved.

Conflict guidance

  • Inspect context before editing with git status, git diff, and file-level diffs.
  • Decide the final behavior before editing conflict markers.
  • Prefer minimal, intention-preserving edits.
  • Resolve one file at a time and rerun checks after each logical batch.
  • For generated files, resolve source conflicts first and regenerate if needed.
  • After resolving, ensure no conflict markers remain with git diff --check.

Ask the user only when necessary

Ask only when the correct resolution depends on product intent that is not inferable from code, tests, or nearby documentation, or when the conflict would introduce irreversible risk without an obvious safe default.

When not to use it

  • When the user wants to rebase instead of merge
  • When the branch is not intended to be synced

Prerequisites

gitorigin remote

Limitations

  • Merge-based only
  • Requires git repository context

How it compares

It uses specific git configurations like rerere and zdiff3 to ensure safe and consistent merge conflict resolution.

Compared to similar skills

pull side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
pull (this skill)02moNo flagsIntermediate
resolve-conflicts818moReviewIntermediate
openspec-onboard106moReviewBeginner
codex-cli-bridge99moReviewIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry