custom-rebase

Rebases Fusion Framework feature branches onto main and handles monorepo conflict traps. USE FOR: rebase this branch, refresh branch from main, fix pnpm-lock.yaml conflicts, resolve Version Packages conflicts, generate a rebase risk report. DO NOT USE FOR: dependency PR review, branch cleanup unrelated to rebase, or destructive reset without explicit approval.

1.50x

Quality

92%

Does it follow best practices?

Impact

95%

1.50x

Average score across 2 eval scenarios

Securityby

Passed

No findings from the security scan

Quality

Content

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

A high-quality skill body: executable commands throughout, explicit safety gates and validation checkpoints for a destructive workflow, and lean repo-specific knowledge. The one improvement area is showing the changeset file format in step 4.

Suggestions

In step 4, include a short example of the consolidated .changeset/*.md file (frontmatter with patch bumps and message body) so the created changeset is copy-paste ready like the rest of the workflow.

Trim redundant parentheticals in step 4, e.g. "(removed/unused upstream)" alongside the later "a pre.json field Changesets v3 no longer reads", which repeats the same deprecation rationale twice.

Dimension	Reasoning	Score
Conciseness	Lean sections of commands and tables with no explanation of concepts Claude already knows; the dense prose in step 4 (Changesets v3 pre.json behavior, deprecated baseline script) is version-specific knowledge Claude cannot infer, so every token earns its place.	5 / 5
Actionability	Copy-paste bash blocks at every step and a conflict-to-exact-command table (e.g. `git checkout --ours "packages//package.json"`) make the workflow mostly executable; the minor gap is that the consolidated `.changeset/.md` file to create in step 4 is described but its format is never shown.	4 / 5
Workflow Clarity	A six-step sequence with explicit gates (dirty-tree stop, branch confirmation), pre-push validation (`git diff --stat origin/$BRANCH...HEAD`, `git push --force-with-lease --dry-run`), a troubleshooting feedback table, and an Expected Output checklist — full validation for a destructive force-push operation.	5 / 5
Progressive Disclosure	Well-organized sections with no monolithic wall of text; the single bundle reference (scripts/generate-rebase-report.cjs) exists in the bundle, is well-signaled with its invocation path, and its generated report is read one level deep from .tmp/skills/custom-rebase/.	5 / 5
	Total	19 / 20 Passed

Description

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

A strong description: third-person, specific, with explicit positive triggers and negative boundaries. The only weakness is slightly incomplete synonym coverage for natural trigger phrases.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Rebases Fusion Framework feature branches onto main and handles monorepo conflict traps", "fix pnpm-lock.yaml conflicts", "resolve Version Packages conflicts", "generate a rebase risk report" — with comprehensive coverage of the rebase domain and no vague filler.	5 / 5
Completeness	Explicitly answers both "what" (rebase feature branches onto main, resolve monorepo conflict traps) and "when" via the "USE FOR:" clause with concrete trigger phrases, and adds a negative "DO NOT USE FOR" boundary.	5 / 5
Trigger Term Quality	Natural phrases users would say ("rebase this branch", "refresh branch from main", "generate a rebase risk report") plus the concrete lockfile filename, but common synonyms like "sync/update my branch from main" are missing, so coverage is short of comprehensive.	4 / 5
Distinctiveness Conflict Risk	Clear niche (Fusion Framework rebases with named conflict patterns like pnpm-lock.yaml and Version Packages) plus an explicit exclusion list, giving minimal overlap risk with other skills.	5 / 5
	Total	19 / 20 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
Path: .agents/skills/custom-rebase/SKILL.md
Commit: e026972

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