merge

Merge changes from the topic branch to the merge base branch. Use when the user wants to merge their session's work back to the base branch.

Quality

87%

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%

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

The content is lean, fully actionable, and well-structured with a clear sequenced workflow and explicit validation checkpoints; it is a strong, self-contained skill body.

Dimension	Reasoning	Score
Conciseness	The body is lean and operational — a short intro, terse guidelines, and command blocks with no padding or explanation of concepts Claude already knows, matching the 'lean and efficient' top anchor.	3 / 3
Actionability	It provides fully executable git commands (e.g. 'git -C <main-worktree-path> merge <topic-branch>', 'git -C <main-worktree-path> merge-base --is-ancestor <topic-branch> HEAD') with clearly marked placeholders, matching the copy-paste-ready top anchor.	3 / 3
Workflow Clarity	The three-step workflow is clearly sequenced and includes an explicit Validation section with two verification commands plus conflict-resolution and abort paths, providing the checkpoints and feedback loop the top anchor requires.	3 / 3
Progressive Disclosure	This is a simple, single-purpose skill under 50 lines with well-organized Guidelines/Workflow/Validation sections and no need for external references, qualifying for the top anchor under the simple-skills scoring note.	3 / 3
	Total	12 / 12 Passed

Description

75%

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

The description is clear and complete with an explicit trigger clause and a well-scoped niche, but it is single-action and lacks keyword variations, capping specificity and trigger_term_quality at 2.

Suggestions

List multiple concrete actions (e.g. 'merge, resolve conflicts, and verify the result') to lift specificity to the top anchor.

Add natural keyword variations users might say, such as 'integrate changes' or 'sync my branch back', to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the concrete action ('Merge changes') and the branch domain, but describes a single action rather than listing multiple specific actions, matching the 'names domain and some actions' anchor rather than the multi-action anchor 3.	2 / 3
Completeness	It explicitly states what ('Merge changes from the topic branch to the merge base branch') and when ('Use when the user wants to merge their session's work back to the base branch'), with an explicit 'Use when' trigger matching the top anchor.	3 / 3
Trigger Term Quality	'merge' is a natural term users would say, but the description lacks common variations or synonyms (e.g. 'integrate', 'sync branch'), so it matches 'some relevant keywords but missing common variations' rather than full coverage.	2 / 3
Distinctiveness Conflict Risk	The session topic-to-base-branch merge-back framing is a clear, narrow niche with distinct triggers unlikely to fire for unrelated skills.	3 / 3
	Total	10 / 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: posit-dev/positron
Path: src/vs/sessions/skills/merge/SKILL.md
Commit: b87c504

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