agentleFS
xeevaxeeva/Genesis/.claude/skills/update/SKILL.md

update

Skill17 starsChanged 8 months agoMITView on GitHub

Pull the latest Genesis updates from the remote repository. Use when the user says "update", "pull updates", "upgrade genesis", "check for updates", or "sync".

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

5 rules. 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 59 edited versions we read keep these.

  • 3

    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. Very specific:

    Check for and apply updates from the Genesis repository.

    line 9
  2. Distinctive:

    If there are uncommitted changes, warn the user and ask whether to proceed (updates may conflict) or abort.

    line 19
  3. Very specific:

    If the count is 0, report "Genesis is already up to date." and exit.

    line 30
  4. Distinctive:

    Confirm with the user: Ask whether to apply the updates.

    line 38
  5. Distinctive:

    If the pull fails due to conflicts, explain the situation and suggest git stash or manual resolution.

    line 60

“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 Genesis

Check for and apply updates from the Genesis repository.

Steps

  1. Verify location: Confirm you are operating in the Genesis directory (~/claude/genesis/). If not, inform the user and exit.
  2. Check for local changes:
git -C ~/claude/genesis/ status --porcelain

If there are uncommitted changes, warn the user and ask whether to proceed (updates may conflict) or abort.

  1. Fetch updates:
git -C ~/claude/genesis/ fetch origin main
  1. Compare versions:
git -C ~/claude/genesis/ rev-list HEAD..origin/main --count

If the count is 0, report "Genesis is already up to date." and exit.

  1. Show what changed:
git -C ~/claude/genesis/ log HEAD..origin/main --oneline --no-decorate

Present the list of incoming changes to the user. Highlight notable updates (new agents, skills, templates, or stack support).

  1. Confirm with the user: Ask whether to apply the updates. Use AskUserQuestion.
  2. Apply updates:
git -C ~/claude/genesis/ pull origin main
  1. Report results: Summarise what was updated. If new skills or agents were added, mention them. If templates changed, note that future generated projects will use the updated templates.

What is Preserved

The following user-specific files are gitignored and will never be overwritten by updates:

  • personalisation.md -- your locale, output style, and profile preferences
  • environment.md -- your platform, shell, and path configuration
  • .claude/settings.local.json -- local Claude Code permission overrides

The .example versions of these files (shipped with Genesis) may be updated to reflect new configuration options. After updating, check if the examples have new fields you might want to add to your own files.

Notes

  • This skill only updates Genesis itself, not projects previously generated by Genesis.
  • Previously generated projects are independent and unaffected by Genesis updates.
  • If the pull fails due to conflicts, explain the situation and suggest git stash or manual resolution.

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.