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.
91
87%
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 other git-related skills. The specificity and distinctiveness are excellent.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to rebase a feature branch, update a branch with upstream changes, or asks about resolving rebase conflicts.'
| 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, 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
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill with clear, actionable workflows, strong safety rails, and explicit confirmation gates before destructive operations. The conflict handling loop with targeted clarification questions and abort options is particularly well-designed. The content is concise and respects Claude's intelligence throughout, with only minor room for improvement in progressive disclosure for the longer sections.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section earns its place. No unnecessary explanations of what git rebase is or how git works. The content is dense with actionable commands and constraints, with no padding or concept explanations Claude would already know. | 3 / 3 |
Actionability | Every step includes exact, copy-paste-ready git commands. The conflict handling loop provides specific strategies and example clarification questions. Commands are concrete and executable, not pseudocode. | 3 / 3 |
Workflow Clarity | The 8-step workflow is clearly sequenced with explicit validation checkpoints: preflight safety checks (step 2), confirmation gates before destructive commands (steps 5, 8), a detailed conflict handling feedback loop (step 6) with abort options, and post-rebase verification (step 7). Recovery instructions are also included. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and headers, but it's entirely self-contained in one file at ~100 lines. For this length, some content (e.g., the conflict handling loop details or recovery section) could be split out, though the current organization is reasonable for the complexity level. | 2 / 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
e437c3c
- 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.