agentleFS
rlajousrlajous/claude-code-commands/skills/update/SKILL.md

update

Skill30 starsChanged 3 months agoMITView on GitHub

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.

61 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use end, create and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • torarnvSkill

    end

    Wrap up a work session. Updates memory files, logs decisions and lessons, appends to the session log.

    Also in 3 projects that use this

  • MicrosoftSkill

    create

    Also in 4 projects that use this

  • bitwize-music-studioSkill

    tutorial

    Provides interactive guided album creation for new users. Use when the user is new to the plugin or asks for a walkthrough of the album creation process.

    Also in 3 projects that use this

  • MicrosoftSkill

    note

    Use this skill to record progress, partial findings, hypotheses, and page-anchored evidence while investigating a long document. Call Note aggressively — any time you read a page and confirm, narrow, or update your understanding of the user's question. Triggers include "jot that down", "save this finding", "note that page 7 says X", or (more often) implicit internal signals — you just learned something and want it recoverable later. Notes persist in the session and Review can select among them. Never paraphrase notes back from memory; write them as you go.

    Also in 4 projects that use this

  • kv0906Skill

    inbox

    Quick capture mode (with content) or batch processing mode (no content). GTD-style routing of inbox items to proper folders. Use "/inbox thought to capture" or "/inbox" to process.

    Also in 4 projects that use this

  • jholhewresSkill

    backup

    Backup and restore — files, databases, and system backups

    Also in 3 projects that use this

  • +2 more from microsoft

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 1 is distinctive, and 5 are very specific to this project.

  • 0

    Common

    Most of the 59 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Follow runtime compatibility.

    line 12
  2. Very specific:

    Never substitute an empty package variable or silently fall back to /scripts.

    line 35
  3. Very specific:

    Use the synchronizer bundled with setup, resolved relative to this skill as {SKILL_DIR}/../setup/scripts/sync-project.mjs, to calculate and …

    line 42
  4. Distinctive:

    Use atomic per-file replacement where practical.

    line 73
  5. Very specific:

    If .git-workflow/config.yaml is absent and .claude/config.yaml exists, offer the same non-destructive copy used by $setup.

    line 77
  6. Very specific:

    After a successful non-dry-run update, the synchronizer rewrites .git-workflow/version.json with version 2.5.2, the resolved source, …

    line 79

“Common” is measured: kept by at least 6 in 10 of the 59 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Update Git Workflow

Follow runtime compatibility. 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.

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:

SourceTargetWhen
skills/*/.claude/skills/*/Manual Claude installation
agents/*.md.claude/agents/*.mdManual Claude installation
references/*.md.claude/references/*.mdManual Claude installation
.codex/agents/*.toml.codex/agents/*.tomlCodex 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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.