Amm save branch

Skill frankenmason/amm-skills/amm-save-branch

Selective curated long-term memory skill bundle for agentmemory MCP. Works with Claude Code, Codex, Cursor, Gemini CLI, Copilot, Antigravity.

Install

npx -y skills add frankenmason/amm-skills --skill amm-save-branch

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Persist a mid-session branch point (topic shift) to long-term memory, marking where the agent pivoted from one scope to another so the prior scope can be resumed later. Trigger when the user steers to a new task while prior work is incomplete, or when the agent self-detects a scope change worth bookmarking.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.8 KB, 570 tokens by cl100k_base, as published. Nobody here has run it

AMM — Save Branch Point

Purpose

A session rarely stays on one topic. When it pivots, the prior scope is easy to forget. A branch-point entry lets amm-recall resurface the prior scope when the user loops back ("what were we doing before X?").

When to Trigger

User message starts a new topic while a prior topic had open items.
Agent self-detects: the current turn's scope ≠ the scope of the previous 3+ turns.
Keywords: "actually, instead...", "pivot", "let's switch to", "before I forget", "hold on".

Apply Conditions

Both the old scope and the new scope can be named in ≤10 words each.
The old scope has at least one unresolved item (otherwise no reason to bookmark it).

Execute

memory_save({
  content:  "Branch point (#{{SESSION_ID}}): <old_scope> → <new_scope>.
             Pending in old scope: <comma- or line-separated items>.
             Return trigger: <condition for coming back>",
  type:     "workflow",
  concepts: "branch_point, <old_topic>, <new_topic>, {{SESSION_ID}}",
  files:    "<comma-separated absolute paths or empty>"
})

Warnings

Do NOT save for small focus shifts within the same scope (fixing a typo mid-implementation is not a branch).
Do NOT save if the old scope has zero pending items — there is nothing to resume.
If the new scope is long-lived, also save an amm-save-pending for the old scope's key items (branch points are for navigation, pendings are for tracking).

Example

User: "hold on, let's look at the build failure first — we can come back to the refactor after."

memory_save({
  content:  "Branch point (#beta-2): refactor user-service.ts → fix CI build failure.
             Pending in old scope: extract auth middleware, add tests for edge cases.
             Return trigger: CI green on main.",
  type:     "workflow",
  concepts: "branch_point, refactor, build_failure, beta-2",
  files:    "/workspace/src/user-service.ts, /workspace/.github/workflows/ci.yml"
})

amm — umbrella (Bootstrap, references, license)
amm-save-pending — when the pending list is worth individual tracking
amm-recall — find branch points to resume

Change Log

1.0.0 — Initial release.