pull Skill
Pull latest origin/main into the current local branch and resolve merge conflicts (aka update-branch). Use when Codex needs to sync a feature branch with origin, perform a merge-based update (not rebase), and guide conflict resolution best practices. Published by openai in symphony.
Decision snapshot
Is this a fit?
Developers using symphony, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
28 days ago · Apache-2.0 license
No specific cautions were detected. Review the source and requested permissions before installing.
What is pull Skill?
Pull latest origin/main into the current local branch and resolve merge conflicts (aka update-branch). Use when Codex needs to sync a feature branch with origin, perform a merge-based update (not rebase), and guide conflict resolution best practices. Published by openai in symphony. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Developers using symphony
Declared skill metadata
- Source file: .codex/skills/pull/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use pull Skill
- Use it for developers using symphony.
Built with
Editorial notes
Source
- Creator: openai
- Repository: openai/symphony
- Skill file: .codex/skills/pull/SKILL.md
What it does
Pull latest origin/main into the current local branch and resolve merge conflicts (aka update-branch). Use when Codex needs to sync a feature branch with origin, perform a merge-based update (not rebase), and guide conflict resolution best practices.
Skill instructions
Pull Workflow 1. Verify 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) - This pulls branch updates made remotely (for example, a GitHub auto-commit) before merging origin/main. 6. Merge in order: - Prefer git -c merge.conflictstyle=zdiff3 merge origin/main for clearer conflict context. 7. If conflicts appear, resolve them (see conflict guidance below), then: - git add <files - git commit (or git merge --continue if the merge is paused) 8. Verify with project checks (follow repo policy in AGENTS.md). 9. Summarize the merge: - Call out the most challenging conflicts/files and how they were resolved. - Note a
Verified compatibility and discovery
Frequently asked questions
What is pull?
pull is a open-source AI agent skill with Copy skill directory. Pull latest origin/main into the current local branch and resolve merge conflicts (aka update-branch).
Who is pull best for?
pull is best for reusing agent instructions, scripts, and references.
How do I install pull?
Install or run pull using Copy skill directory. Check pull for the latest setup command.
Is pull actively maintained?
pull may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
