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.
88
83%
Does it follow best practices?
Impact
99%
1.67xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
82%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong, specific description that clearly communicates the skill's purpose and uses natural developer terminology. Its main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill over others. The specificity and distinctiveness are excellent.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to rebase a branch, update a feature branch with latest changes, or sync with main/master.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: syncing a feature branch, git rebase onto latest origin base branch, conflict resolution, and force-with-lease pushing. Also mentions safety rails as a concrete characteristic. | 3 / 3 |
Completeness | Clearly answers 'what does this do' (sync feature branch via rebase with safety rails and conflict resolution), but lacks an explicit 'Use when...' clause specifying when Claude should select this skill. The 'when' is only implied. | 2 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'rebase', 'feature branch', 'base branch', 'conflict resolution', 'force-with-lease', 'sync'. These are terms developers naturally use when needing this workflow. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — the combination of git rebase, feature branch syncing, force-with-lease pushing, and conflict resolution creates a very clear niche that is unlikely to conflict with other git-related skills like commit message generation or merge workflows. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, well-structured skill that provides fully actionable git commands in a clear multi-step workflow with explicit confirmation gates and safety rails. The conflict handling loop is particularly well done with its feedback cycle and escalation path. Minor verbosity in the intro/goals section and a few redundant inline explanations prevent a perfect conciseness score.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient and avoids explaining basic git concepts, but some sections could be tightened—e.g., the 'Goals' section restates what the intro already says, and some inline comments are slightly redundant. Overall reasonably lean but not maximally tight. | 2 / 3 |
Actionability | Every step includes exact, copy-paste-ready git commands with proper flags and arguments. The conflict handling loop provides specific commands for each sub-step, and even the backup ref creation uses a concrete command with a timestamp pattern. | 3 / 3 |
Workflow Clarity | The workflow is clearly sequenced across 8 numbered phases with explicit validation checkpoints (preflight safety checks, confirmation gates before destructive commands, post-rebase verification). The conflict handling loop includes a clear feedback cycle (resolve → stage → continue → ask if unclear) and recovery instructions. | 3 / 3 |
Progressive Disclosure | For a standalone skill with no bundle files, the content is well-organized into clearly labeled sections (Hard Rules, Workflow steps 1-8, Recovery) that serve as a natural table of contents. The skill is appropriately sized for a single file with no need for external references. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
Total | 10 / 11 Passed | |
- Repository
- NeverSight/skills_feed
- Commit
aa009ea
- Reviewed
Table of Contents
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.