update-setup
/update-setup
Inspect or apply upstream claudops changes to a project's copied .claude/ workflow. Use for claudops update checks, selected upstream adoption, or conflicts with local workflow customizations. Installed plugin upgrades use the host's plugin manager.
- Author
- alexandrbasis ↗
- Repository
- claudops ↗
- Licence
- MIT
- Last repository change
- 08.09.2026
Assessment and security
- Files in this package
- 3
- Scripts
- 2
- HTML comments
- 1
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 08.09.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
- 2 scripts in this package. Review them before installing, as Claude may execute them.
- SKILL.md zawiera komentarze HTML (1). Nie widać ich w podglądzie Markdown, a model je czyta.
Scripts: scripts/update_setup.py, tests/test_update_setup.py
What it does and when to use it
Inspect or apply upstream claudops changes to a project's copied .claude/ workflow. Use for claudops update checks, selected upstream adoption, or conflicts with local workflow customizations. Installed plugin upgrades use the host's plugin manager.
Original author description
Inspect or apply upstream claudops changes to a project's copied .claude/ workflow. Use for claudops update checks, selected upstream adoption, or conflicts with local workflow customizations. Installed plugin upgrades use the host's plugin manager.
How it works
- Scope and authority
- Resolve the script and target
- Workflow
- Conflict Handling
- Post-Update Checks
- Edge Cases
SKILL.md preview
---
name: update-setup
description: Inspect or apply upstream claudops changes to a project's copied .claude/ workflow. Use for claudops update checks,
selected upstream adoption, or conflicts with local workflow customizations. Installed plugin upgrades use the host's plugin
manager.
allowed-tools: Read Glob Grep Bash Write Edit AskUserQuestion
compatibility: Portable clients may not enforce Claude Code invocation guards or project setup behavior.
---
<!-- claudops-build: project-config-pointer -->
> If `.claude/skills/update-setup/SKILL.md.disabled` exists, stop before reading a fallback.
> **Project configuration:** If the current project contains `.claude/skills/update-setup/SKILL.md`, read and apply it instead of this bundled default. The project copy is the capability source of truth.
> **Repository context:** Read `../setup/references/task-context.md` when resolving a task, project commands, named agent roles, or legacy `.claude/` resource paths. Use repository evidence and applicable project instructions; a missing local workflow copy does not require setup. Resolve bundled resources from the installed skill, never from the target cwd.
# Update Setup
Sync local `.claude/` workflow files with upstream claudops. The skill is
upstream-driven: local-only user files are ignored unless they are explicitly tracked in
the update manifest.
This workflow is for a legacy copied `.claude/` installation. A managed plugin remains
authoritative; upgrade it through the host plugin manager instead of copying the plugin
into the project. Read `../setup/references/task-context.md` when this update is
attached to a task; a check-only or standalone update does not create a task.
## Scope and authority
- Start with the deterministic script. Do not classify diffs manually.
- A check-only request ends at the report. Before applying updates, refreshing disabled
files or deleting removed upstream files, establish approval for the exact paths and
operations. Reuse approval already granted for that selection. Branch creation, commit,
push and PR creation require their own authorized scope; they are not update prerequisites.
- Never update `.claude/settings.json`, `.claude/settings.local.json`, `CLAUDE.md`,
hook logs, `.gitkeep`, or local-only `*.local.*` files through this skill.
- Use LLM judgment only to explain conflicts and help the user choose a strategy after
the script has produced exact statuses and diffs.
## Resolve the script and target
Resolve `scripts/update_setup.py` relative to this loaded skill, including when it is
inside a plugin. Keep the consuming repository as the working directory. Set these
shell variables to the actual resolved paths for the commands below:
```bash
CLAUDOPS_UPDATE_SCRIPT="/absolute/path/to/loaded/update-setup/scripts/update_setup.py"
CLAUDOPS_TARGET="/absolute/path/to/target-repository"
python3 "$CLAUDOPS_UPDATE_SCRIPT" --help
```
The script's `--local-root` is a global option and belongs before `scan`, `apply`, or
`verify`. Its local state belongs to the target repository; never point it at a managed
plugin cache. An installed plugin upgrade is a separate operation through the host's
plugin manager. Read the installed plugin's identifier before constructing that command.
The script writes adoption state to:
```text
.claude/skills/update-setup/claudops-upstream.lock.json
```
Tracked scope:
- `.claude/**`
Skipped scope:
- `.claude/settings.json`
- `.claude/settings.local.json`
- `.claude/hooks/logs/**`
- `.gitkeep`
- `CLAUDE.md`
- local-only `*.local.*`
## Workflow
### 1. Scan
Create a deterministic report:
```bash
python3 "$CLAUDOPS_UPDATE_SCRIPT" --local-root "$CLAUDOPS_TARGET" scan \
--output .claudops-update-report.json
```
For local testing against an existing upstream clone:
```bash
python3 "$CLAUDOPS_UPDATE_SCRIPT" --local-root "$CLAUDOPS_TARGET" scan \
--upstream-root /tmp/claudops-upstream-sync \
--commit "$(git -C /tmp/claudops-upstream-sync rev-parse HEAD)" \
--output .claudops-update-report.json
```
### 2. Present Report
Render the report:
```bash
python3 "$CLAUDOPS_UPDATE_SCRIPT" --local-root "$CLAUDOPS_TARGET" report \
--report .claudops-update-report.json
```
Explain statuses:
- `new`: upstream file is not present locally.
- `modified`: upstream differs from local and local has no tracked conflict.
- `conflicting`: local changed since the last tracked adoption.
- `disabled`: upstream file exists, but local has `<path>.disabled`.
- `removed`: file was tracked in the manifest but is gone upstream.
- `placeholder_only`: differences are filled `{{PLACEHOLDER}}` values.
- `unchanged`: local matches upstream or the tracked adoption hash.
If only `unchanged` and `placeholder_only` entries exist, report that the setup is up to
date and stop.
### 3. Resolve the selection
Present the exact paths and operations for approval unless that selection is already
authorized. Paths are relative to `.claude/`. Convert the approved selection into JSON:
```json
{
"update": [
"skills/example/SKILL.md"
],
"refresh_disabled": [
"skills/disabled/SKILL.md"
],
"delete": [
"skills/removed/SKILL.md"
]
}
```
Rules:
- `update` may include `new` and `modified` paths.
- `refresh_disabled` may include `disabled` paths and writes `<path>.disabled`.
- `delete` may include only `removed` paths.
- Do not apply `conflicting` paths until the user chooses a conflict strategy.
### 4. Apply
After approval:
```bash
python3 "$CLAUDOPS_UPDATE_SCRIPT" --local-root "$CLAUDOPS_TARGET" apply \
--report .claudops-update-report.json \
--selection /path/to/selection.json
```
The apply step updates selected files and refreshes the target repository's lock manifest.
Use the source clone and local files from the reviewed scan. If either changes before
application, rerun the scan and resolve any changed selection before writing.
When a task is attached, link the scan, exact selection, apply result and verify
read-back from the task directory. Preserve local customizations and disabled markers;
never write the managed plugin cache.
### 5. Verify
Run:
```bash
python3 "$CLAUDOPS_UPDATE_SCRIPT" --local-root "$CLAUDOPS_TARGET" verify
```
When changing this helper or its command contract, run the `tests/test_update_setup.py`
file adjacent to the loaded skill. A report or successful script exit alone does not
prove the selected files were adopted: read back the result counts and destination hashes.
## Conflict Handling
For `conflicting` files:
1. Show the file path and exact diff from `.claudops-update-report.json`.
2. Explain what upstream changed and what local changed.
3. Ask the user to choose one strategy:
- replace local with upstream
- keep local and mark skipped
- manually merge, then update the manifest after verification
Do not silently merge conflicts.
## Post-Update Checks
After applying selected updates:
- Run `verify`.
- If new hook files were added, inspect `.claude/settings.json` and report unwired hooks
as manual follow-up. Do not auto-edit settings.
- If updated files contain `{{PLACEHOLDER}}`, tell the user to run `/setup`.
- Summarize counts: updated, disabled refreshed, deleted, skipped, placeholders, and
manual follow-ups.
## Edge Cases
- Clone failure: report the git error and stop.
- Missing `.claude/`: route an authorized first configuration to `setup`; it can materialize
the bundled templates. A check-only request reports that there is no copied workflow.
- Conflicts: show the affected paths and material changes. Group related conflicts for
review; the file count does not determine their severity.
- Binary files: the script may copy them, but conflict explanation should avoid trying to
summarize binary content.
Files in this package (3)
- SKILL.md 8 KB
- scripts/update_setup.py 14 KB
- tests/test_update_setup.py 7 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · alexandrbasis/claudops | 100 | MIT |
| alexandrbasis/claudops | 100 | MIT |
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 8ba2f30f037a (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100update
Update NanoClawbster from upstream. Fetches latest changes, merges with your customizations and skills, runs migrations. Triggers on \"update\", \"pull upstream\", \"sync with upstream\", \"get latest changes\". - 100claude-codex-upstream-update
Use when researching Claude Code or Codex upstream releases, selecting adaptations, or preparing Harness upgrades. Local-only; not for distribution. - 100update-plugins
Check which Claude Code marketplaces and plugin installs (user, project and local scope, across all project folders) are out of date, recommend what to update, and update what the user confirms. Use when the user asks to update plugins, check for plugin updates, or sync plugin versions across repos. - 100sync-template
Syncs the .claude/ directory from an upstream template repository, showing a diff and applying new or modified files without overwriting local customizations. Use when updating SDD template files or when the user mentions template sync or upstream update. - 100custom-plugin-refresh
Maintenance protocol for hand-authored plugins that have no upstream to diff against: the four freshness risk classes and their cadences, where hard-coded versions hide, the re-research and surgical-edit update protocol, the refresh commit tag, and triage for picking what to… - 100nav-sync-claude
Sync project CLAUDE.md to the installed Navigator version, preserving customizations. Use when user says "sync CLAUDE.md", "update CLAUDE.md", or when detecting outdated Navigator configuration.