Guide for rebasing feature branches onto main in the Fusion Framework monorepo, including handling pnpm-lock.yaml conflicts
73
58%
Does it follow best practices?
Impact
97%
1.42xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agents/skills/custom-rebase/SKILL.mdpnpm monorepo rebase workflow script
Double fetch pattern
0%
100%
Rebase onto origin/main
100%
100%
Lockfile removal step
0%
100%
Lockfile regeneration
100%
100%
Stage regenerated lockfile
100%
100%
Continue rebase
100%
100%
Sanity check diff stat
0%
100%
Sanity check file list
0%
100%
Sanity check commit log
0%
100%
Force-with-lease push
100%
100%
No manual lockfile editing
100%
100%
Rebase report generation and human-readable summary
Correct script invocation
90%
90%
--no-fetch flag used
41%
58%
Report read from correct path
30%
100%
Breaking changes section
62%
100%
New dependencies section
87%
100%
Version baselines section
50%
100%
Risk assessment present
100%
100%
Risk emoji indicator
100%
100%
Pre-push checklist
90%
100%
SUMMARY.md created
100%
100%
Version Packages conflict resolution and pre-release alignment
package.json uses --ours
100%
100%
CHANGELOG.md uses --ours
100%
100%
Glob pattern for packages
0%
100%
vue-press package.json handled
100%
100%
Stage after checkout
100%
100%
Continues rebase
100%
100%
Correct alignment script path
0%
100%
Run from repo root
50%
100%
No --ours on source files
100%
62%
No manual version editing
100%
100%
060e3af
Table of Contents
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.