agentleFS
Sign inStart free
BrandedTamarasu-glitchBrandedTamarasu-glitch/ForgeFlow/.agents/skills/update-forgeflow/SKILL.md

update-forgeflow

Skill1 starsChanged 45 days agoMITView on GitHub

Update the local Forgeflow repo or Codex port from the source repository.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    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:

    Use this skill when the user wants to sync this local Forgeflow copy with the upstream repository.

    line 6
  2. Distinctive:

    Check the local git remote and current branch state.

    line 11
  3. Distinctive:

    If the user wants to proceed and approvals allow it, pull or re-clone as appropriate.

    line 14
  4. Very specific:

    If the user asks about the Claude installer path instead of repo sync, inspect commands/update-forgeflow.md and the install manifest before …

    line 16
  5. Distinctive:

    Never overwrite local custom Codex assets without clear user intent.

    line 19
  6. Distinctive:

    Use non-destructive git operations.

    line 20

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

Use this skill when the user wants to sync this local Forgeflow copy with the upstream repository.

For consumer Claude installs, /update-forgeflow is the no-clone installer. It syncs agents, commands, hooks, templates, project rules, patterns, and runtime helpers into ~/.claude/, with helper scripts under ~/.claude/forgeflow/scripts/forgeflow/.

Workflow:

  1. Check the local git remote and current branch state.
  2. Fetch remote changes.
  3. Show the incoming diff or commit range.
  4. If the user wants to proceed and approvals allow it, pull or re-clone as appropriate.
  5. Preserve project-local Codex additions unless the user explicitly asks to overwrite them.
  6. If the user asks about the Claude installer path instead of repo sync, inspect commands/update-forgeflow.md and the install manifest before changing behavior.

Rules:

  • Never overwrite local custom Codex assets without clear user intent.
  • Use non-destructive git operations.

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