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
- orgiggly/claude-plugintheir own version, first seen Nov 8, 2026
- ljchang/mechatheir own version, first seen Nov 8, 2026
- onetapstudiogames/1f3d9-citylifetheir own version, first seen Nov 8, 2026
- patrickjaja/claude-desktop-extratheir own version, first seen Nov 6, 2026
- egregore-labs/egregoretheir own version, first seen Nov 6, 2026
- buildomator/buildomatortheir own version, first seen Nov 4, 2026
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.
torarnvSkillend
Wrap up a work session. Updates memory files, logs decisions and lessons, appends to the session log.
Also in 3 projects that use this
MicrosoftSkillcreate
Also in 4 projects that use this
bitwize-music-studioSkilltutorial
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
MicrosoftSkillnote
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
kv0906Skillinbox
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
jholhewresSkillbackup
Backup and restore — files, databases, and system backups
Also in 3 projects that use this
- +2 more from microsoft
Other versions61 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 61
- anthropics/knowledge-work-plugins★ 35ksame name
- Q00/ouroboros★ 6.3ksame name
- vellum-ai/vellum-assistant★ 1.5ksame name
- patrickjaja/claude-desktop-extra★ 734same name
- me2resh/apexyard★ 542same name
- daloopa/investing★ 488same name
- TokenRollAI/cc-plugin★ 483same name
- egregore-labs/egregore★ 293same name
- k1p1l0/claude-telegram-supercharged★ 144same name
- kv0906/pm-kit★ 138same name
51 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository23 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- change-briefSkill
- clean-goneSkill
- close-customer-loopSkill
- commitSkill
- finishSkill
- notificationsSkill
- plan-qaSkill
- plan-tddSkill
- release-notesSkill
- releaseSkill
- review-requestSkill
- reviewSkill
- review-watchSkill
- rfcSkill
- setupSkill
- standupSkill
- start-qaSkill
- startSkill
- statusSkill
- syncSkill
- tddSkill
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
- Very specific: line 12
Follow runtime compatibility.
- Very specific: line 35
Never substitute an empty package variable or silently fall back to /scripts.
- Very specific: line 42
Use the synchronizer bundled with setup, resolved relative to this skill as {SKILL_DIR}/../setup/scripts/sync-project.mjs, to calculate and …
- Distinctive: line 73
Use atomic per-file replacement where practical.
- Very specific: line 77
If .git-workflow/config.yaml is absent and .claude/config.yaml exists, offer the same non-destructive copy used by $setup.
- Very specific: line 79
After a successful non-dry-run update, the synchronizer rewrites .git-workflow/version.json with version 2.5.2, the resolved source, …
“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.
Files
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:
--source{PACKAGE_ROOT}, derived from the absolute physical directory containing this loadedSKILL.mdas{SKILL_DIR}/../.., when it contains.codex-plugin/plugin.jsonPLUGIN_ROOT, thenCLAUDE_PLUGIN_ROOT, as compatibility fallbacks only when the host cannot expose the loaded skill path; verify the manifest before accepting either valuesourcerecorded 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-runSynchronize 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. --prunemay 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-runperforms 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.
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
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.

