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

82%

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

81%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.

Highly actionable content with concrete, executable git commands and an explicit, well-validated workflow that matches the project's checks. The main weaknesses are generic conflict-resolution prose that pads the token budget and a monolithic structure where the conflict guidance could live in a reference file.

Suggestions

Trim the Conflict Resolution Guidance section to the non-obvious specifics (zdiff3 marker behavior, :1/:2/:3 diff comparison, regenerate-generated-files strategy, accept-both-then-lint for imports) and cut generic advice Claude already knows about understanding both sides' intent.

Move detailed conflict-resolution tactics into a references/ file (e.g., references/conflicts.md) and keep a short pointer in SKILL.md, tightening the main body toward an overview.

State the Borg UI check commands once with a brief condition (backend vs. frontend) instead of nesting them inside the workflow step to reduce inline command listing.

Dimension	Reasoning	Score
Conciseness	The workflow steps are tight and command-driven, but the Conflict Resolution section spends many lines on generic guidance Claude already knows ("State what each side is trying to achieve", "Avoid accidental deletions or silent behavior changes", "Open files and understand intent on both sides"). Mostly efficient with some unnecessary explanation, matching the 3 anchor; the zdiff3-specific notes are genuinely additive, keeping it above a 2.	3 / 5
Actionability	Fully executable 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 :1:path/to/file :2:path/to/file", plus concrete project checks ("ruff check app tests", "npm run check:locales && npm run typecheck"). Copy-paste ready commands covering the common cases.	5 / 5
Workflow Clarity	A clear 9-step sequence with explicit validation (step 8: "git diff --check" plus ruff/pytest/npm checks), feedback loops ("rerun tests after each logical batch"; resolve → add → commit → merge --continue), and a final summarize step. This matches the 5 anchor with validation checkpoints and error-recovery guidance, so the destructive-operation cap does not apply.	5 / 5
Progressive Disclosure	No bundle files exist; the ~95-line body is well-organized with clear section headers (Workflow, Conflict Resolution Guidance, When To Ask The User) and no nested references. However, the ~40-line conflict-resolution guidance is reference-grade detail inlined in SKILL.md, so structure is good but not the clear overview-with-references pattern of the 5 anchor.	4 / 5
	Total	17 / 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 description that clearly states what the skill does and when to use it, with concrete actions and good trigger terms including the "update-branch" synonym. The main gap is slightly limited keyword variation for how users might phrase branch-syncing requests.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — "Pull latest origin/main into the current local branch", "resolve merge conflicts", "guide conflict resolution best practices" — with only minor coverage gaps (e.g., verification steps). It exceeds the 3 anchor (1-2 actions) but is not comprehensive enough for a 5.	4 / 5
Completeness	Explicitly answers both: what ("Pull latest origin/main into the current local branch and resolve merge conflicts") and when ("Use when Codex needs to sync a feature branch with origin, perform a merge-based update (not rebase)"). Matches the 5 anchor with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good natural keyword coverage: "pull", "merge conflicts", "sync a feature branch", "aka update-branch", "merge-based update (not rebase)", including a synonym via "update-branch". Missing common variations like "update my branch" or "merge main into my branch", so not a 5.	4 / 5
Distinctiveness Conflict Risk	Scoped by distinct constraints ("merge-based update (not rebase)", "origin", "feature branch") making it mostly distinct from generic git skills. Minor overlap risk with other branch-update/merge skills keeps it below a 5.	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: karanhudia/borg-ui
Path: .codex/skills/pull/SKILL.md
Commit: 47dfb3e

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