update-setup

Scan upstream .claude changes and prepare an adoption plan.

12|2|Updated Nov 20, 2025

Search Tags:#automation #workflow #update #version-control #upstream #claudops

Ready to run

npx skills add https://github.com/alexandrbasis/claudops --skill update-setup

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: update-setup
Source: https://github.com/alexandrbasis/claudops/tree/main/.claude/skills/update-setup
Command: npx skills add https://github.com/alexandrbasis/claudops --skill update-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Sync local Claudops workflows with upstream updates while preserving local customizations and enforcing safety checks.

Core Features & Use Cases

deterministic scan/report of upstream changes to .claude/.
explicit approvals before applying updates, with safeguards for disabled/removed files.
manifest-driven, scope-limited updates across the local workspace.

Quick Start

Run the update-setup command to scan for upstream changes and prepare an adoption plan.

Frequently Asked Questions about update-setup

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

FAQPage Schema

How do I sync local Claudops workflows with upstream updates?▼

You can sync local Claudops workflows with upstream updates by running the update-setup command, which scans for changes, generates a report, and prepares an adoption plan for your local .claude folder.

How does the deterministic scan and report engine work for .claude folder updates?▼

The deterministic scan and report engine tracks adoption state in a manifest, identifies upstream changes to your .claude folder, and enforces hard rules to preserve local customizations before applying any updates.

Can I preserve local customizations when applying upstream updates to my .claude folder?▼

Yes, you can preserve local customizations because the update process requires explicit approvals before applying changes and includes built-in safeguards for disabled or removed files.

What is the best way to manage version control for local Claudops workflows across a team?▼

The best way to manage version control for team Claudops workflows is using a manifest-driven, scope-limited update engine that enforces hard rules and requires explicit approvals before applying upstream changes.

When do I need explicit approvals for upstream workflow updates?▼

You need explicit approvals for upstream workflow updates whenever you are maintaining a local .claude folder and want to enforce safety checks, ensuring that disabled or removed files are protected during the synchronization process.