rebase

Rebase local changes on top of remote branch updates

Quality

55%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/git-workflow/skills/rebase/SKILL.md

Quality

Discovery

32%

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 identifies a specific git operation but lacks completeness by omitting explicit trigger guidance. It provides minimal context for when Claude should choose this skill over other git-related skills, and doesn't cover the full range of user language that might indicate a need for rebasing.

Suggestions

Add a 'Use when...' clause with trigger scenarios like 'when user wants to sync their branch with upstream', 'when branch is behind remote', or 'when user mentions rebase or pull --rebase'

Include common user phrases and variations: 'git rebase', 'sync with main', 'update my branch', 'behind origin/main', 'incorporate upstream changes'

Clarify when to use this skill vs merge-based approaches to reduce conflict with other git skills

Dimension	Reasoning	Score
Specificity	Names the domain (git/version control) and describes one specific action (rebase local changes on remote), but doesn't list multiple concrete actions or variations of what the skill can do.	2 / 3
Completeness	Only answers 'what' (rebase local changes on remote). Missing any 'Use when...' clause or explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Contains 'rebase', 'local changes', and 'remote branch' which are relevant terms, but misses common variations users might say like 'git rebase', 'pull --rebase', 'sync branch', 'update branch', or 'behind origin'.	2 / 3
Distinctiveness Conflict Risk	Somewhat specific to rebasing operations, but could overlap with general git skills, merge skills, or branch management skills without clearer boundaries on when to use rebase vs other git operations.	2 / 3
	Total	7 / 12 Passed

Implementation

77%

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

This is a well-structured skill with excellent workflow clarity and actionable guidance. The main weaknesses are moderate verbosity (explaining rebase vs merge concepts Claude knows) and keeping all content inline rather than using progressive disclosure to separate detailed examples from the core instructions.

Suggestions

Remove the 'When to Use Rebase vs Merge' section - Claude already understands these git concepts

Consider moving the detailed 'Interactive Flow' output examples to a separate EXAMPLES.md file, keeping only a brief example in the main skill

Condense the error handling section to just the commands/solutions without the emoji-heavy formatting

Dimension	Reasoning	Score
Conciseness	The skill includes some unnecessary verbosity like the 'When to Use Rebase vs Merge' section explaining concepts Claude already knows, and the extensive ASCII-art style output examples could be condensed. However, the core instructions are reasonably efficient.	2 / 3
Actionability	Provides concrete, executable git commands throughout (git fetch, git rebase, git stash, etc.), specific Task tool delegation syntax, and clear step-by-step instructions that are copy-paste ready.	3 / 3
Workflow Clarity	Excellent multi-step workflow with clear sequencing (verify state → fetch → check conflicts → execute → confirm), explicit validation checkpoints, and comprehensive conflict/error handling with recovery paths.	3 / 3
Progressive Disclosure	Content is well-organized with clear sections, but everything is inline in one file. The extensive output examples and error handling could be split into separate reference files for a cleaner overview.	2 / 3
	Total	10 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: jpoutrin/product-forge
Commit: 0ebe7ae

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