custom-rebase

Guide for rebasing feature branches onto main in the Fusion Framework monorepo, including handling pnpm-lock.yaml conflicts

1.42x

Quality

—

Does it follow best practices?

Impact

97%

1.42x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Quality

Content

77%

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

The content is highly actionable with executable commands, existing scripts, and a well-sequenced workflow including validation checkpoints. Its main weaknesses are some verbosity/conceptual explanation that Claude already knows and a monolithic structure that could split detailed material into referenced files.

Suggestions

Trim or move the 'Why Regenerate pnpm-lock.yaml?' rationale and the redundant 'Example: Complete rebase flow' to reduce token cost, since the standard workflow already conveys these steps.

Resolve the inconsistency between step 3 (pnpm install + git add without removing the file) and the checklist/example (git rm pnpm-lock.yaml before pnpm install) so guidance is uniform.

Clarify step 10's 'SUMMARY.md' reference, since the documented script writes a timestamped report under .tmp/ rather than a SUMMARY.md file, to avoid a missing-key-detail gap.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient executable commands, but it includes some unnecessary explanation (the 'Why Regenerate pnpm-lock.yaml?' section explains lockfile mechanics Claude already knows) and redundancy (the 'Example: Complete rebase flow' repeats the standard workflow).	2 / 3
Actionability	The skill provides abundant concrete, copy-paste-ready bash commands and invokes specific existing scripts (align-pre-initial-versions.cjs, generate-rebase-report.cjs), matching 'fully executable code/commands; specific examples'.	3 / 3
Workflow Clarity	The 10-step rebase process is clearly sequenced with explicit validation checkpoints (git status, sanity-check diffs vs remote, --dry-run push) and a feedback loop of resolve-conflict -> continue, plus a checklist and troubleshooting recovery.	3 / 3
Progressive Disclosure	The two referenced scripts exist in ./scripts/ and are signaled as one-level-deep paths, but the SKILL.md itself is a ~310-line monolithic file with troubleshooting, rationale, and a full example that could be split into separate reference files.	2 / 3
	Total	10 / 12 Passed

Description

57%

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 clearly identifies a specific niche (pnpm-monorepo rebasing) and names relevant trigger terms, but it lacks an explicit 'Use when...' trigger clause and only partially enumerates concrete actions. Adding an explicit usage trigger and a fuller action list would raise the score.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when rebasing a feature branch onto main in the Fusion Framework monorepo or when pnpm-lock.yaml conflicts arise during a rebase.'

List more concrete actions (e.g., regenerate lockfile, resolve Version Packages commits, align pre.json versions, generate a rebase report) to strengthen specificity.

Include common trigger variations users might say, such as 'rebase onto main', 'lockfile conflict', or 'changeset pre-release versions'.

Dimension	Reasoning	Score
Specificity	Names the domain ("rebasing feature branches onto main in the Fusion Framework monorepo") and one concrete action ("handling pnpm-lock.yaml conflicts"), but does not enumerate multiple specific concrete actions, so it falls short of a 3.	2 / 3
Completeness	It states what the skill does but provides no "Use when..." clause or equivalent explicit trigger guidance for when Claude should invoke it; per the guidelines a missing trigger clause caps completeness at 2.	2 / 3
Trigger Term Quality	Includes relevant natural terms like "rebase", "feature branches", "main", "pnpm-lock.yaml", and "monorepo", but lacks common variations and an explicit usage trigger, matching 'some relevant keywords but missing common variations'.	2 / 3
Distinctiveness Conflict Risk	The narrow framing around rebasing in a specific pnpm monorepo with pnpm-lock.yaml conflict handling is a clear niche with distinct triggers unlikely to fire for unrelated skills.	3 / 3
	Total	9 / 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: equinor/fusion-framework
Commit: 54fb2a7

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