Skip to content
Skills Library
Programming · Automation

update

/update

Update Git Workflow skills and Claude/Codex project agents from a source checkout or installed plugin, with dry-run, pruning, customization detection, and legacy migration support. Use when the user asks to update, refresh, or synchronize Git Workflow.

Licence
MIT
Last repository change
01.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 01.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Update Git Workflow skills and Claude/Codex project agents from a source checkout or installed plugin, with dry-run, pruning, customization detection, and legacy migration support. Use when the user asks to update, refresh, or synchronize Git Workflow.

Arguments

/update [--host <claude|codex|both>] [--dry-run] [--prune] [--force] [--source <path-or-git-url>]
Original author description

Update Git Workflow skills and Claude/Codex project agents from a source checkout or installed plugin, with dry-run, pruning, customization detection, and legacy migration support. Use when the user asks to update, refresh, or synchronize Git Workflow.

How it works

  1. 1. Parse options
  2. 2. Resolve project and source
  3. 3. Build the synchronization set
  4. 4. Protect customizations
  5. 5. Migrate and record state
  6. Output
Original SKILL.md headings · 76 lines, 641 words
SKILL.md preview
---
name: update
description: Update Git Workflow skills and Claude/Codex project agents from a source checkout or installed plugin, with dry-run, pruning, customization detection, and legacy migration support. Use when the user asks to update, refresh, or synchronize Git Workflow.
argument-hint: "[--host <claude|codex|both>] [--dry-run] [--prune] [--force] [--source <path-or-git-url>]"
disable-model-invocation: false
allowed-tools: Read, Bash, Write, Glob, Grep, AskUserQuestion
user-invocable: true
---

# Update Git Workflow

Follow [runtime compatibility](../../references/runtime-compatibility.md). Claude Code users invoke this as `/update`; Codex users invoke it as `$update`.

## 1. Parse options

- `--dry-run`: calculate and display changes without writing.
- `--prune`: include previously managed files that no longer exist in the source as removal candidates.
- `--force`: overwrite customized managed files after still showing their diffs.
- `--host <claude|codex|both>`: synchronize only the selected host assets; otherwise infer installed hosts and ask if ambiguous.
- `--source <path-or-git-url>`: use an explicit Git Workflow checkout, plugin directory, or Git URL.

Unknown options are errors. Destructive pruning is never implied by `--force` alone.

## 2. Resolve project and source

Resolve the project root from Git, then accept either `.git-workflow/`, `.claude/`, or `.codex/` as evidence of an existing installation. Resolve the source in this order:

1. `--source`
2. `{PACKAGE_ROOT}`, derived from the absolute physical directory containing this loaded
   `SKILL.md` as `{SKILL_DIR}/../..`, when it contains `.codex-plugin/plugin.json`
3. `PLUGIN_ROOT`, then `CLAUDE_PLUGIN_ROOT`, as compatibility fallbacks only when the host cannot
   expose the loaded skill path; verify the manifest before accepting either value
4. `source` recorded in `.git-workflow/version.json`

Never substitute an empty package variable or silently fall back to `/scripts`. If no complete
source resolves, stop before writing and report every candidate checked.

For an explicit Git URL, clone it shallowly into a newly created temporary directory, validate it, and remove the temporary clone on success or failure. Do not perform a default network clone when an installed package root or ledger source is available. Validate that the source contains `skills/`, `agents/`, `.codex/agents/`, and a valid `.codex-plugin/plugin.json`. Stop without writing if it is incomplete.

## 3. Build the synchronization set

Use the synchronizer bundled with `setup`, resolved relative to this skill as
`{SKILL_DIR}/../setup/scripts/sync-project.mjs`, to calculate and apply this set. Always run it
first with `--dry-run`; after the user reviews changes, rerun without `--dry-run`. Add `--force`
only when changed files were approved, and add `--confirm-prune` only after separate confirmation
of listed prune candidates.

```bash
node "{SKILL_DIR}/../setup/scripts/sync-project.mjs" --source <source> --target <project> --host <codex|claude|both> --dry-run
```

Synchronize only components relevant to the installation:

| Source | Target | When |
|---|---|---|
| `skills/*/` | `.claude/skills/*/` | Manual Claude installation |
| `agents/*.md` | `.claude/agents/*.md` | Manual Claude installation |
| `references/*.md` | `.claude/references/*.md` | Manual Claude installation |
| `.codex/agents/*.toml` | `.codex/agents/*.toml` | Codex project agents |

Codex plugin skills are updated by the plugin manager and must not be copied into `.codex/skills/` by this workflow.

For every target, classify it as missing (`+`), changed (`~`), identical (`=`), or orphaned (`?`). Show a unified diff for changed text files.

## 4. Protect customizations

- Without `--force`, ask once before overwriting the listed changed files. A rejection preserves all changed files while still allowing missing files to install.
- With `--force`, overwrite changed managed files only after showing the summary.
- `--prune` may remove only paths recorded as managed in the version ledger. Never remove an untracked local skill or agent merely because the source lacks the same name.
- Show prune candidates and require explicit confirmation even with `--force`.
- `--dry-run` performs no writes, removals, directory creation, or ledger updates.

Use atomic per-file replacement where practical. A failure must not truncate the previous target.

## 5. Migrate and record state

If `.git-workflow/config.yaml` is absent and `.claude/config.yaml` exists, offer the same non-destructive copy used by `$setup`; do not make migration a prerequisite for updating agents.

After a successful non-dry-run update, the synchronizer rewrites `.git-workflow/version.json` with version `2.5.2`, the resolved source, timestamp, hosts, and the exact relative paths managed by this run. Preserve the user's workflow configuration, local hook opt-in, PR context, status report, and reviewed-SHA ledger.

## Output

Report installed, updated, unchanged, preserved, pruned, and failed files separately. If any item fails, return a non-success summary with the exact recovery command. Otherwise suggest `/status` for Claude Code or `$status` for Codex.

Versions

RepositoryScoreLicence
This page · rlajous/claude-code-commands100MIT
nimbalyst/nimbalyst100MIT
nimbalyst/nimbalyst100MIT
nimbalyst/nimbalyst100MIT
jl-cmd-projects/claude-dev-env100MIT
abatyuk/okf100MIT
tony/skills100MIT
crisandrews/clawcode100MIT
nextwork-projects/ai-video-editor-cooked100MIT

Database snapshot: 13.11.2026 · package version 891e5a1e0e04 (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

  • 100setup
    Configure Git Workflow for Claude Code or Codex, migrate legacy configuration, install Codex project agents, and optionally configure issue-tracker MCP servers. Use when the user asks to set up, install, configure, or migrate Git Workflow.
  • 90skill-update
    Use when the user wants to check whether installed agent skills are outdated or update them - "update my skills", "are my skills up to date", "스킬 업데이트", "스킬 최신화" - for skills installed with npx skills, as git clones, or as Claude Code plugins, across Claude Code, Codex, Cursor,…
  • 100update-installed-skills
    Use when syncing or updating previously installed skills to their latest version. Always dry-run updates before applying, and check for breaking changes.
  • 100update-project-skills
    Brings an installed plugin marketplace (claude-skills by default) up to date and reports what is different afterwards. Refreshes the marketplace, updates each plugin installed from it and prints the skills that were added, changed or removed, with a reminder to restart Claude…
  • 100port-to-codex
    Ports a project's Claude Code setup (CLAUDE.md, skills, agents, MCP, hooks) to Codex: AGENTS.md becomes the shared instruction file with CLAUDE.md as a symlink to it, and Codex's .agents/skills/ and .codex/ are generated from .claude/ and .mcp.json with rulesync. Use when the…
  • 95aos-update
    Update the installed AOS: check for a new version, preview, run the update and verify. Use when asked to update, upgrade or check for a new AOS release.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.