Merges upstream template changes into branded forks while preserving branding via brand.json.
npx skills add https://github.com/pward17/site-template --skill upstream
Please help me install this Agent Skill. Skill: upstream Source: https://github.com/pward17/site-template/tree/main/.claude/skills/upstream Command: npx skills add https://github.com/pward17/site-template --skill upstream
Syncs upstream template changes into your branded fork while preserving branding and minimizing manual merge work.
Run the /upstream sync command to fetch the latest upstream changes and merge them into your fork while preserving branded files.
High-intent search queries and answers about installing and using this skill.
To merge upstream changes without losing branding, you need a conflict-aware workflow that protects branded files. This Skill performs a no-commit merge, automatically restores files listed in brand.json, and regenerates lockfiles to ensure your custom branding survives the template upgrade.
The best way to sync a template repo fork with upstream git changes is to use a branded-file protection mechanism. This tool fetches upstream updates, applies a no-commit merge to preview changes, and automatically restores branding defined in your configuration file.
The brand.json file protects files during a git merge by defining branding-sensitive paths. After the upstream merge is applied without committing, the tool reads this configuration to automatically restore your branded files, preventing upstream template changes from overwriting your customizations.
Yes, you can preview upstream changes before committing them to your fork. The tool performs a no-commit merge, allowing you to review the applied template updates and verify that branding-sensitive files are correctly restored before finalizing the sync.
You do not need to manually resolve conflicts for branding-sensitive files when upgrading a branded fork. The tool minimizes manual merge work by using brand.json to automatically restore your custom files and regenerating lockfiles as part of the upgrade workflow.
Your lockfiles are modified after syncing upstream template changes because the upgrade workflow automatically regenerates them. This ensures your dependency tree remains consistent with the newly merged upstream code while keeping your branded files protected.
outfitter-devSync agent-browser fork with upstream and generate integration documentation.
idvorkinSync local git repositories with upstream or origin main branches.
AvatarGanymedeDelete local git branches and worktrees deleted on the remote.
erguotou520Synchronize a NanoClaw fork with upstream changes while preserving local modifications.
