agentleFS
Sign inStart free
pushprove-maxpushprove-max/Commandeck/skills/update/SKILL.md

update

Skill3 starsChanged 6 days agoApache-2.0View on GitHub

Finish a commandeck plugin update for this project. Use when the owner runs /commandeck:update or says "update commandeck", after `claude plugin update commandeck`.

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

3 rules. 0 are common, 1 is distinctive, and 2 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.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask "Relay": Rebase it (recommended) | Leave as is

    line 23
  2. Very specific:

    Only Rebase runs bash ${CLAUDE_PLUGIN_ROOT}/scripts/relay-sync.sh --rebase.

    line 25
  3. Very specific:

    If update shows a Main prompt cache:, Builder and worker prompt cache: or Chief of Staff prompt cache: line under Needs you, ask that …

    line 29

“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

/commandeck:update

Claude Code moves an updated plugin to a new folder; Codex's hooks, the permission rule and the two background jobs still name the old one until this runs. In each project that is set up:

bash ${CLAUDE_PLUGIN_ROOT}/scripts/update.sh

It prints the version and its changelog, re-points everything, and runs the doctor. Show the owner the changelog and any line that is not ok.

Then run bash ${CLAUDE_PLUGIN_ROOT}/scripts/relay-sync.sh. If it prints relay: <n> commits behind main, say so, that the relay pane may be running and sees the change, and ask:

Ask "Relay": Rebase it (recommended) | Leave as is

Only Rebase runs bash ${CLAUDE_PLUGIN_ROOT}/scripts/relay-sync.sh --rebase. It refuses and changes nothing when the relay worktree has uncommitted changes or the rebase conflicts: show its line. relay: current or relay: none: say nothing.

If update shows a Main prompt cache:, Builder and worker prompt cache: or Chief of Staff prompt cache: line under Needs you, ask that question from ${CLAUDE_PLUGIN_ROOT}/skills/setup/SKILL.md word for word, then run bash ${CLAUDE_PLUGIN_ROOT}/scripts/setup.sh with only that question's flag: --main-cache-ttl, --worker-cache-ttl or --relay-cache-ttl. Never run setup.sh without the answer.

  • It exits 1 with "back as it was" when the doctor fails: the files are restored; tell the owner the doctor's FAIL lines.
  • It refuses a config version it does not know and changes nothing. There is no migration: the owner uninstalls with the old version, then sets up again.
  • Going back a version: install the earlier version with Claude Code's plugin command, then run this same script from that version's folder.

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.

Check your setup, free