upgrade

Merge upstream claudesidian changes while preserving user customizations.

2.6k|194|Updated Sep 12, 2025
One-click install
npx skills add https://github.com/heyitsnoah/claudesidian --skill upgrade-heyitsnoah
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: upgrade
Source: https://github.com/heyitsnoah/claudesidian/tree/main/.agents/skills/upgrade
Command: npx skills add https://github.com/heyitsnoah/claudesidian --skill upgrade-heyitsnoah

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates upgrading claudesidian by integrating upstream changes while preserving user customizations, reducing manual drift and configuration drift.

Core Features & Use Cases

  • Version checks and upstream synchronization: compares local version with upstream and determines updates.
  • Backup and safety net: creates a backup snapshot before applying upgrades.
  • Upstream fetch and diff: fetches latest code from upstream and generates diffs.
  • Guided application: interactive, AI-assisted resolution of conflicts and updates.
  • Symlink hygiene: verifies and repairs symlinks for skills after updates.

Quick Start

Run the upgrade workflow to fetch upstream, review diffs, and apply updates to your local claudesidian.

Frequently Asked Questions about upgrade

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

FAQPage Schema
How do I upgrade claudesidian without losing my custom configurations?

To upgrade claudesidian safely, this Skill automates merging upstream changes while preserving your local customizations. It fetches the latest code, generates a diff, and uses AI-assisted conflict resolution to prevent configuration drift.

What is the safest way to pull upstream changes and merge local customizations?

The safest way to pull upstream changes is creating a backup snapshot before applying updates. This Skill compares your local version with upstream, fetches the latest features, and guides you through an interactive merge to protect your customizations.

Can I migrate from a legacy claudesidian layout to the latest version?

Yes, you can migrate from legacy layouts across different environments. The upgrade workflow applies version checks from package.json, fetches upstream updates, and repairs symlinks to ensure a smooth transition to the latest layout.

How does AI-assisted merge resolution handle version check conflicts?

AI-assisted merge resolution handles version check conflicts by comparing local and upstream package.json versions, generating a detailed diff, and interactively guiding you through applying updates while preserving your customizations.

Do I need to manually fix symlinks for skills after an upstream update?

No, you do not need to manually fix symlinks. The upgrade process includes symlink hygiene that automatically verifies and repairs symlinks for skills after updates are applied, ensuring your environment remains functional.