Pulling Updates from Skills Repository

Sync local skills repository with upstream changes while preserving local modifications.

8|1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/gujiachun-rainbow/RainClaw --skill pulling-updates-from-skills-repository-gujiachun-rainbow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Pulling Updates from Skills Repository
Source: https://github.com/gujiachun-rainbow/RainClaw/tree/main/.trae/skills/pulling-updates-from-skills-repository
Command: npx skills add https://github.com/gujiachun-rainbow/RainClaw --skill pulling-updates-from-skills-repository-gujiachun-rainbow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill syncs your local skills repository with upstream changes while preserving your personal modifications.

Core Features & Use Cases

  • Deterministic update workflow: stash changes, fetch tracking remote, merge upstream changes, and verify skill integrity.
  • Conflict handling: guides how to resolve merge conflicts and re-validate after update.
  • Operational safety: preserves local commits and branches during updates.

Quick Start

Start the updating process at session start or when you want to pull the latest upstream changes.

Frequently Asked Questions about Pulling Updates from Skills Repository

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I pull upstream changes from a git repository without losing local modifications?

To pull upstream changes safely, stash local modifications, fetch the tracking remote, merge upstream updates, and verify skill integrity to ensure local commits and branches remain preserved.

What is the safest git workflow to sync a local skills repository with upstream?

The safest git workflow to sync a local skills repository involves stashing changes, fetching the tracking remote, merging upstream changes, and running verification steps to maintain conflict-free environments.

How do I resolve merge conflicts after fetching upstream changes in my local repository?

Resolve merge conflicts after fetching upstream changes by following guided conflict resolution steps, then re-validate and verify skill integrity to ensure the local repository remains up-to-date and conflict-free.

Can I preserve local commits and branches when updating my local repository with upstream changes?

Yes, you can preserve local commits and branches during updates. The workflow applies operational safety by stashing changes before fetching and merging upstream updates, keeping local modifications intact.

When should I sync my local skills repository with upstream changes?

You should sync your local skills repository with upstream changes at startup or when manually updating to the latest versions to keep skills up-to-date and conflict-free across environments.

What happens if my local skills repository has uncommitted changes before an upstream merge?

If your local skills repository has uncommitted changes, the workflow stashes them before fetching and merging upstream changes, ensuring local modifications are safely preserved and restored after the update.