pull

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.

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.codex/skills/pull/SKILL.md

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable instruction skill with a clear sequenced workflow, embedded validation, and concrete git commands for both the merge and conflict-resolution phases. Minor improvements are possible around trimming explanatory prose, specifying the verification step inline, and splitting the conflict guidance into a reference.

Suggestions

Replace 'Verify with project checks (follow repo policy in AGENTS.md)' with an explicit inline validation command or a concrete fallback so the workflow's checkpoint is self-contained.

Trim explanatory asides like 'This pulls branch updates made remotely (for example, a GitHub auto-commit) before merging origin/main.' to keep the workflow purely procedural.

Consider moving the detailed Conflict Resolution Guidance into a references/ file (e.g. CONFLICTS.md) and summarizing the key rules inline, improving both conciseness and progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Lean, command-driven body that does not explain basic git concepts, with only minor explanatory asides (e.g. 'This pulls branch updates made remotely (for example, a GitHub auto-commit)...'); not a 5 because a few sentences could be trimmed.	4 / 5
Actionability	Concrete, copy-paste-ready git commands throughout ('git config rerere.enabled true', 'git pull --ff-only origin $(git branch --show-current)', 'git -c merge.conflictstyle=zdiff3 merge origin/main', 'git diff --check'); not a 5 due to the '<files>' placeholder and absence of a worked before/after conflict example.	4 / 5
Workflow Clarity	Clear 9-step numbered sequence with validation checkpoints ('Verify git status is clean', conflict-resolution loop, 'Verify with project checks', 'git diff --check'); not a 5 because verification is partly deferred to an external AGENTS.md rather than specified inline.	4 / 5
Progressive Disclosure	Well-organized into Workflow / Conflict Resolution / When To Ask sections with no nesting and no bundle files to navigate; not a 5 because the ~40-line conflict guidance is borderline content that could live in a separate reference, and the skill exceeds the 50-line simple-skill exception.	4 / 5
	Total	16 / 20 Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, concrete description that clearly states what the skill does and gives explicit 'Use when' trigger guidance, with good natural keywords and useful disambiguation from rebase skills. Its only weakness is mild redundancy across the pull/sync/merge actions and modest keyword breadth.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('Pull latest origin/main', 'resolve merge conflicts', 'sync a feature branch', 'perform a merge-based update (not rebase)', 'guide conflict resolution'); not a 5 because pull/sync/merge-update overlap rather than providing comprehensive distinct coverage.	4 / 5
Completeness	Explicitly answers both what ('Pull latest origin/main...resolve merge conflicts') and when ('Use when Codex needs to sync...perform a merge-based update (not rebase)...guide conflict resolution best practices') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good natural-term coverage ('Pull', 'merge conflicts', 'update-branch', 'sync a feature branch with origin', 'rebase') that users would actually say; not a 5 since it lacks synonym and file-extension breadth.	4 / 5
Distinctiveness Conflict Risk	Clear niche (merge-based branch update) with disambiguating cues ('aka update-branch', 'not rebase'); not a 5 due to minor overlap risk with a generic git-pull or rebase skill.	4 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: openai/symphony
Path: .codex/skills/pull/SKILL.md
Commit: 8001b52

Reviewed: 24 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.