Stops you from blowing away your work when you pull main into a feature branch. Instead of silently picking one side, it fetches, spots conflicts, then shows you every unmerged file grouped by impact: structural and API changes first, styling last. You get a recommendation table with reasons before any conflict markers get touched. The hard rule is no edits until you confirm the plan. Especially useful on multi-contributor projects where main moves fast and you need to see what changed in shared shells, route modules, or hooks before deciding whether to keep your version, theirs, or combine both. Treats merge conflicts like code review, not obstacles to automate away.
npx skills add https://github.com/cognitedata/builder-skills --skill pull-changes-resolve-conflicts