Problem
This repo's CLAUDE.md, under "Git and PR conventions," states:
Always branch from origin/main — there is no separate upstream remote
But core slopsmith's CLAUDE.md, under "Git Workflow," states:
Upstream remote — set upstream to the canonical Slopsmith repository; origin is your fork
These are two different remote models (fork+upstream vs. direct-to-origin), and anyone working across both slopsmith core and slopsmith-plugin-splitscreen in the same session gets contradictory instructions depending which CLAUDE.md they read last.
Ask
Reconcile the two documents. Likely resolution: confirm which model is actually in effect for this plugin repo specifically (plugin repos may legitimately differ from core's fork-based contribution model if plugin authors push directly), and update whichever CLAUDE.md is stale so the two docs agree — or explicitly note in both that plugin repos and core intentionally use different remote conventions, if that's the real intended state.
Migrated from Maestro-Ltd/slopsmith-plugin-splitscreen#17.
Problem
This repo's CLAUDE.md, under "Git and PR conventions," states:
But core
slopsmith's CLAUDE.md, under "Git Workflow," states:These are two different remote models (fork+upstream vs. direct-to-origin), and anyone working across both
slopsmithcore andslopsmith-plugin-splitscreenin the same session gets contradictory instructions depending which CLAUDE.md they read last.Ask
Reconcile the two documents. Likely resolution: confirm which model is actually in effect for this plugin repo specifically (plugin repos may legitimately differ from core's fork-based contribution model if plugin authors push directly), and update whichever CLAUDE.md is stale so the two docs agree — or explicitly note in both that plugin repos and core intentionally use different remote conventions, if that's the real intended state.
Migrated from Maestro-Ltd/slopsmith-plugin-splitscreen#17.