agentleFS
Sign inStart free
egregore-labsegregore-labs/egregore/.claude/skills/pull/SKILL.md

pull

Skill293 starsChanged 9 days agoMITView on GitHub

Use for /pull when you need to sync the current branch and shared memory. Activity and dashboard are read-only and never sync repositories.

13 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 10 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    Not this: only want to see recent activity → /activity (read-only).

    line 14
  2. Distinctive:

    If memory is already up to date:

    line 53

“Common” is measured: kept by at least 6 in 10 of the 10 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

Pull latest for current repo and shared memory.

Note: /activity and /dashboard are read-only. Use /pull for explicit synchronization.

When to invoke

User says: "/pull", "pull latest", "sync my branch", "get the latest changes", "update memory", or needs to sync without also viewing activity. Not this: only want to see recent activity → /activity (read-only).

Execution boundary

This is a deterministic sync-transport operation. Run it inline; do not spend a Loom/model-routing call or delegate it to another agent.

What to do

Run:

bash bin/pull.sh

The command resolves the base with bash bin/base-branch.sh, fetches it, and rebases a task branch onto origin/<base>. It fast-forwards the base branch itself, merges when a rebase conflicts, and leaves a conflict for you with the tree restored if both attempts fail. When the memory link is missing, it links the memory checkout beside the main checkout, then syncs memory through the Runtime.

Show its report to the user as is. Exit 1 means something needs a hand; the report says what. Managed repositories are not synced by this command.

Output

Show what arrived — don't leave the user wondering if things synced:

Pulling...
  configured base ↓ 3 commits → synced
  dev/oz/...      ✓ rebased onto configured base
  memory         ↓ 2 commits — 4 files updated
                   handoffs/2026-02/12-renckorzay-giza-docs.md (new)
                   handoffs/index.md
                   artifacts/giza-architecture.md (new)
                   artifacts/giza-api-spec.md (new)

If memory is already up to date:

  memory         ✓ up to date

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