tower-upgrade

Integrates approved workspace features and patterns into Tower's installation template and setup scripts.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/juliuschun/tower --skill tower-upgrade
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tower-upgrade
Source: https://github.com/juliuschun/tower/tree/main/claude-skills/skills/tower-upgrade
Command: npx skills add https://github.com/juliuschun/tower --skill tower-upgrade

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of integrating new features, structures, and patterns developed in a user's workspace into the Tower installation template and setup scripts, ensuring consistency and propagating best practices across new installations without breaking existing setups.

Core Features & Use Cases

  • Template Synchronization: Safely incorporates changes from a live workspace into the Tower installation template (~/claude-desk/templates/workspace/) and setup.sh.
  • Diff-Based Analysis: Compares the current workspace with the template to identify and categorize differences (structure, config, services, knowledge, infra).
  • Safety-First Application: Prioritizes not breaking existing installations, categorizing changes by additive, optional, merge, or breaking, and allowing user approval before applying.
  • Use Case: After developing a new standardized project structure or a helpful AI assistant configuration in your workspace, use this skill to seamlessly update the Tower template so all future Tower installations automatically include these improvements.

Quick Start

Run /tower-upgrade scan to see what changes can be applied to the Tower template.

Frequently Asked Questions about tower-upgrade

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

FAQPage Schema
How do I sync workspace changes to my installation template?

Template synchronization compares your live workspace with the installation template to identify differences, categorizing changes as additive, optional, merge, or breaking before safely applying approved updates.

What is the safest way to update setup scripts without breaking existing installations?

Updating setup scripts safely involves categorizing changes by impact—additive, optional, merge, or breaking—and requiring user approval before applying them, ensuring existing configurations remain undisrupted.

How does diff-based analysis work for configuration synchronization?

Diff-based analysis works by comparing the current workspace against the installation template, identifying and categorizing differences across structure, config, services, knowledge, and infrastructure for targeted updates.

Can I propagate new project structures to future deployments automatically?

Yes, you can propagate new project structures by integrating workspace innovations into the Tower template, ensuring all future installations automatically include the latest standardized improvements.

What categories of changes are identified when syncing a workspace to a template?

When syncing a workspace to a template, changes are categorized as additive, optional, merge, or breaking, spanning structure, config, services, knowledge, and infrastructure differences.

When should I not use automated template synchronization?

You should avoid automated template synchronization when changes are categorized as breaking, as applying them without manual review can disrupt existing installations and override active configurations.