sync

Sync the current session branch with its upstream branch, or publish the current session branch to a remote. Use when the user asks to sync a branch, pull latest changes, rebase onto upstream, push current branch, publish branch, or set upstream.

Quality

91%

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

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

The body is a tight, fully executable runbook: safety guardrails up front, a correctly sequenced workflow with real commands and decision points, and an explicit validation section with feedback loops for conflict and rejected-push recovery. Structure is appropriately self-contained for the skill's scope.

Dimension	Reasoning	Score
Conciseness	The body assumes Claude's git competence: no explanations of what rebase or upstream tracking means, four terse guideline bullets, and every command earns its place. The only redundancy is the intro sentence restating the description, which is conventional and minor — this fits anchor 5 (lean, every token earns its place) better than anchor 4.	5 / 5
Actionability	Every workflow step is paired with a real, executable git command ("git fetch <upstream-remote>", "git rev-list --left-right --count HEAD...@{u}", "git rebase @{u}", "git push -u <remote> HEAD"), and the validation section gives three concrete verification commands. Placeholders are standard parameterization, not pseudocode, matching anchor 5 (copy-paste ready, covers the common cases).	5 / 5
Workflow Clarity	The workflow is a clearly numbered sequence with explicit checkpoints: stop-and-report when 0 ahead/0 behind, conflict resolution with continue/abort feedback loops, a force-push approval gate, and a dedicated Validation section with explicit post-run checks. Validation for risky operations is present, so the destructive-operation cap does not apply — anchor 5 fits.	5 / 5
Progressive Disclosure	No bundle files exist and none are needed for this single, focused procedure; the body is appropriately self-contained and organized into Guidelines / Workflow / Validation sections with no content that belongs in a separate file. Well-organized sections with no external-reference needs match the top anchor.	5 / 5
	Total	20 / 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 well-constructed description that explicitly pairs a concrete 'what' with a broad, natural-language 'when' clause in third person. Trigger coverage is strong but not exhaustive, and a few common synonyms would push trigger quality and distinctiveness to the top anchor.

Suggestions

Add common synonyms to the trigger clause, e.g. "update the branch", "git pull", or "fetch and integrate upstream changes", to broaden natural-term coverage.

Consider narrowing overlap-prone triggers like "push current branch" with a qualifier (e.g. "push current branch to its upstream") to reduce conflict risk with related git skills.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions ("Sync the current session branch with its upstream branch", "publish the current session branch to a remote") with sub-actions surfaced via "pull latest changes, rebase onto upstream, push current branch, or set upstream". Minor gaps in coverage keep it at anchor 4 rather than the comprehensive anchor 5.	4 / 5
Completeness	Explicitly answers both questions: what ("Sync the current session branch with its upstream branch, or publish the current session branch to a remote") and when ("Use when the user asks to sync a branch, pull latest changes, rebase onto upstream, push current branch, publish branch, or set upstream"). This mirrors the anchor-5 example structure with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural trigger phrases like "sync a branch", "pull latest changes", "rebase onto upstream", "push current branch", "publish branch", and "set upstream" cover the space well. Common synonyms such as "update branch", "fetch", or "git pull" are missing, which fits anchor 4 (a few natural terms missing) rather than anchor 5's comprehensive synonym coverage.	4 / 5
Distinctiveness Conflict Risk	The skill occupies a clear git branch sync/publish niche with specific triggers, but phrases like "pull latest changes" and "push current branch" carry minor overlap risk with closely related git skills (fetch, push, PR-merge). Anchor 4 ("mostly distinct; minor overlap risk") is the best fit — anchor 3 overstates the conflict and anchor 5 ignores it.	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: posit-dev/positron
Path: src/vs/sessions/skills/sync/SKILL.md
Commit: b0258bc

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