agentleFS
Sign inStart free
NickMoignardNickMoignard/agent-workspace-template/.agents/skills/update-workspace/SKILL.md

update-workspace

Skill0 starsChanged 2 months agoMITView on GitHub

Refresh the agent workspace so nothing goes stale — pull referenced projects, sync agent skills, and update project dependencies. Use when the user asks to update, refresh, or unstale the workspace/projects/deps/skills.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. hunterbohm/solo-staff★ 0same name

    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 repository7 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    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:

    Run make update-projects. This fast-forwards each linked project's clone to the latest commit on its default branch.

    line 29
  2. Very specific:

    Run make update-agent-deps to bring dependencies current inside each project.

    line 34
  3. Very specific:

    Run make update-agent-skills to refresh external skills (via npx skills update).

    line 36
  4. Very specific:

    Commit any workspace-level changes (e.g.

    line 39
  5. Very specific:

    Never hand-edit the .code-workspace folder list.

    line 45
  6. Distinctive:

    If something won't fast-forward, stop and inspect rather than forcing it.

    line 47

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Keep the workspace up to date

Referenced projects, external skills, and dependencies all drift over time. This skill brings everything current.

Full refresh

From the workspace root:

make update            # = update-projects + update-agent-deps + update-agent-skills

Or run the pieces individually:

GoalCommandWhat it does
Projects stalemake update-projectsgit pull --ff-only in each linked project's clone, then re-syncs the VS Code workspace folders.
Skills stalemake update-agent-skillsRuns npx skills update to refresh external skills tracked in skills-lock.json.
Dependencies stalemake update-agent-depsDetects the package manager per project and updates deps.

Procedure

  1. Run make update-projects. This fast-forwards each linked project's clone to the latest commit on its default branch. Nothing to commit in the workspace — it pins no project commits. If a project needs a new project added or linked, use make add-project URL=<git-url> (or make sync-projects after editing projects.yaml).
  2. Run make update-agent-deps to bring dependencies current inside each project. Inspect and commit lockfile changes inside each project's own repo.
  3. Run make update-agent-skills to refresh external skills (via npx skills update). Add new ones with npx skills@latest add <owner/repo> -a universal, then commit .agents/skills/ + skills-lock.json.
  4. Commit any workspace-level changes (e.g. projects.yaml) with a clear message.

Rules

  • Dependency and code changes belong to the project's own repo — commit them there. The workspace tracks only its own config (projects.yaml, skills).
  • Never hand-edit the .code-workspace folder list; update-projects and sync-projects regenerate it via make sync-workspace.
  • If something won't fast-forward, stop and inspect rather than forcing it.

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