git-rebase-sync

Sync a feature branch onto the latest origin base branch via git rebase, with safety rails, deliberate conflict resolution, and safe force-with-lease pushing.

1.67x

Quality

87%

Does it follow best practices?

Impact

99%

1.67x

Average score across 3 eval scenarios

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 an excellent, lean, executable workflow with strong validation feedback loops appropriate for a destructive history-rewriting operation. It needs no changes.

Dimension	Reasoning	Score
Conciseness	The body is lean and efficient: it assumes Claude knows git, presents commands as bullets, and avoids explaining what a rebase is, so every token earns its place.	5 / 5
Actionability	Fully executable, copy-paste-ready commands cover every step (e.g. 'git rebase origin/{base_branch}', 'git push --force-with-lease origin HEAD:{branch_name}', 'git tag -a {branch_name}-rebase-backup-...').	5 / 5
Workflow Clarity	An explicit 8-step sequence with validation checkpoints (preflight safety checks, conflict-resolution loop with stop-and-ask, post-rebase verification) and confirmation gates before every history-rewriting command.	5 / 5
Progressive Disclosure	Self-contained SKILL.md with clearly organized sections (Goals, Hard Rules, Workflow, Recovery) and no nested or buried references; no bundle files are needed and none are present.	5 / 5
	Total	20 / 20 Passed

Description

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

The description is specific, third-person, and clearly distinguishable, but it omits any explicit 'when to use' trigger guidance, which caps its completeness. Adding a 'Use when ...' clause would lift the weakest dimension.

Suggestions

Add an explicit trigger clause, e.g. 'Use when syncing a feature branch onto the latest base branch, resolving rebase conflicts, or needing to force-push rebased commits.'

Include natural synonyms users say, such as 'sync/update branch' and 'merge conflicts', to broaden trigger term coverage.

Keep the third-person voice and concrete action list as-is — these are already strong.

Dimension	Reasoning	Score
Specificity	Names the domain and multiple concrete actions — 'Sync a feature branch ... via git rebase', 'deliberate conflict resolution', and 'safe force-with-lease pushing' — giving comprehensive coverage of the skill's lifecycle rather than just a few actions with gaps.	5 / 5
Completeness	It clearly states what the skill does but has no 'Use when...' clause or equivalent explicit trigger guidance, so per the rubric guideline completeness is capped at 3.	3 / 5
Trigger Term Quality	Good natural keywords ('git rebase', 'feature branch', 'conflict resolution', 'force-with-lease') that users would say, but a few common variations like 'sync/update branch' or 'merge conflicts' are missing, so it is not fully comprehensive.	4 / 5
Distinctiveness Conflict Risk	It carves a clear niche — rebase-based branch sync with force-with-lease — with distinct triggers and minimal overlap risk against merge-based or general git skills.	5 / 5
	Total	17 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: NeverSight/skills_feed
Path: data/skills-md/0xbigboss/claude-code/git-rebase-sync/SKILL.md
Commit: 2f57aec

Reviewed: about 23 hours 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.