pull

Rebases the current branch onto its PR base or origin/main.

16|2|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/hojinzs/github-symphony --skill pull-hojinzs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pull
Source: https://github.com/hojinzs/github-symphony/tree/main/.codex/skills/pull
Command: npx skills add https://github.com/hojinzs/github-symphony --skill pull-hojinzs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers keep their current feature branch aligned with the latest base branch, preventing merge conflicts and preserving a clean history before PRs.

Core Features & Use Cases

  • Detects the PR base when a PR exists, otherwise uses origin/main as the base.
  • Fetches the latest changes and rebases the current branch onto the identified base.
  • Handles conflict scenarios with guidance and, after resolution, pushes updates using a safe lease.

Quick Start

Run the pull skill on your current branch to rebase onto its base and update the branch.

Frequently Asked Questions about pull

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

FAQPage Schema
How do I rebase my feature branch onto the latest base branch before a PR?

You can sync your current branch by running the pull Skill, which automatically detects the PR base or defaults to origin/main, fetches latest changes, and initiates the rebase process.

When should I rebase my branch to keep it in sync with the base?

You should sync your branch before creating a PR, before starting work on a feature branch, or when preparing for squash-merge workflows to prevent merge conflicts and preserve a clean history.

How are merge conflicts handled during a branch rebase?

During a branch rebase, conflict scenarios are handled with guidance, and after manual resolution, the Skill pushes updates safely using a force-push with lease.

Do I need git and gh tooling to sync my branch with origin/main?

Yes, you need git and gh tooling with access to the repository origin to sync your branch with origin/main, as the Skill requires both to detect the base, fetch, and rebase.

What is the best way to prepare a feature branch for a squash-merge workflow?

The best way to prepare a feature branch for a squash-merge workflow is to rebase it onto the PR base or origin/main, ensuring the branch is aligned with the latest changes and has a clean history.