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

88%

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

Quality

Content

77%Weight 40%Scale 1-3

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

Highly actionable and clearly sequenced with proper validation, but it carries some redundancy (explaining git concepts Claude knows) and keeps everything inline rather than splitting the detailed conflict guidance into a reference file.

Suggestions

Trim explanations of concepts Claude already knows — e.g. remove the zdiff3 conflict-marker legend and the "State what each side is trying to achieve / Identify the shared goal" prose, keeping only the non-obvious guidance.

Move the detailed "Conflict Resolution Guidance (Best Practices)" section into a references file (e.g. CONFLICTS.md) and link to it from the workflow, so the SKILL.md body stays a lean overview.

Tighten the "When To Ask The User" section to a short checklist; the preamble ("Do not ask for input unless...") largely restates the bullet conditions.

Dimension	Reasoning	Score
Conciseness	Mostly efficient command lists, but pads with concepts Claude already knows — e.g. explaining zdiff3 conflict markers ("<<<<<<< ours, \|\|\|\|\|\|\| base, ======= split, >>>>>>> theirs") and intent-summarizing prose ("State what each side is trying to achieve..."). Not 3 because of this padding; not 1 because it is far from a concept-explaining wall of text.	2 / 3
Actionability	Fully executable, copy-paste-ready commands throughout (e.g. `git -c merge.conflictstyle=zdiff3 merge origin/main`, `ruff check app tests`, `npm run typecheck`), matching the executable-code anchor rather than the pseudocode anchor at 2.	3 / 3
Workflow Clarity	A clear 9-step sequenced workflow with explicit validation (step 8: `git diff --check`, ruff, pytest, frontend checks) and a retry loop (step 7 conflict resolution, plus "rerun tests after each logical batch"). Validation is present, so it is not capped at 2.	3 / 3
Progressive Disclosure	Well-sectioned but a single ~95-line file with no external references; the sizable inline Conflict Resolution Guidance block is content that could be split into a reference. Not 3 because nothing is offloaded into one-level-deep references; not 1 because sections are clearly organized rather than a monolithic wall.	2 / 3
	Total	10 / 12 Passed

Description

100%Weight 40%Scale 1-3

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 description: concrete actions, explicit "Use when" trigger, good natural keyword coverage, and a distinctive merge-not-rebase niche. No real weaknesses.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Pull latest origin/main into the current local branch" and "resolve merge conflicts" — matching the multiple-specific-actions anchor rather than the single-domain anchor at 2.	3 / 3
Completeness	Explicitly answers what (pull origin/main, resolve conflicts) and when via a clear "Use when Codex needs to sync a feature branch..." clause, satisfying both halves; not capped at 2 since the trigger is explicit.	3 / 3
Trigger Term Quality	Covers natural terms a user would say ("pull", "sync a feature branch", "merge conflicts", "update-branch"), giving good coverage of common variations; not the sparse-keyword case at 2.	3 / 3
Distinctiveness Conflict Risk	Targets a clear niche (merge-based branch update, explicitly "not rebase", conflict resolution) with distinct triggers unlikely to collide with other skills.	3 / 3
	Total	12 / 12 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: karanhudia/borg-ui
Path: .codex/skills/pull/SKILL.md
Commit: 380827d

Reviewed: 12 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.