brain-save

Original：🇺🇸 English

Translated

Save session context, decisions, progress, and plans to the Claude Brain Logseq graph. Triggers: "save to brain", "save this", "remember this", "store this decision", "log this", "save progress", "before I quit", "wrap up". Don't fire for read operations (use brain-load) or status checks (use brain-status).

1installs

Sourcejame581/logseqbrain

Added on2026-05-18

NPX Install

npx skill4agent add jame581/logseqbrain brain-save

SKILL.md Content

View Translation Comparison →

Brain Save

Persist session context — decisions, progress, plans, implementation details — to the Claude Brain Logseq graph for cross-session and cross-device continuity.

Prerequisites

Resolve the graph path per

skills/_shared/path-resolution.md

.

What to Save

Six categories — see

references/categories.md

for each one's format and rules. The orchestrator decides which apply based on what the session covered:

Session Log Entry (always)
Decisions (when made — see
```
references/decisions.md
```
for conflict + cross-project rules)
Plan Updates (when plans changed — replace, don't append)
Implementation Details (when significant)
Jira Task Context (when tasks were worked on — store pointers, not full plans)
User Preferences & Meta (when newly discovered — update
```
pages/Meta.md
```
)

Save Process

Identify target project(s). Look for project names mentioned, files/repos discussed, or explicit user statements ("we're working on X"). If multiple projects, save to each. If unclear, ask: "This touched [X] and [Y] — save to both?"
Verify project page exists. Glob for
```
pages/Projects___<ProjectName>.md
```
. If missing:
- Tell user: "No project page found for [name]. Want me to create one first?"
- If yes, hand off to
```
brain-init
```
  "Adding a New Project" flow, then continue.
- If no, list available projects and let the user pick.
- Never write session data to a non-existent project page.
Read the current project page selectively using the section-targeted-read pattern in
```
skills/_shared/section-locator.md
```
. Read only the sections you'll touch (Session Log, Decisions, Current Plan, Implementation) — never the whole file. The read serves two purposes: detect duplicates before appending, and provide enough surrounding lines for the Edit
```
old_string
```
to be unique.
Prepare the updates for each applicable category from
```
references/categories.md
```
.
Write the updates using the Edit tool — surgical updates per section, never rewrite the whole page:
- Append to Session Log
- Append to Decisions (with conflict check per
```
references/decisions.md
```
  )
- Replace Current Plan if changed
- Update Implementation if needed
- Update
```
last-updated::
```
  to today's date

Update the journal —
## Sessions
. Append a rich cross-reference to today's

journals/yyyy_MM_dd.md

:

markdown

- ## Sessions
  - [[Projects/ProjectName]]: Brief summary of session

Update
pages/Meta.md
if new user preferences emerged (see
```
references/categories.md
```
category 6).
Update
pages/Index.md
if a project status changed or new cross-project info emerged.

Write a journey-log entry per

skills/_shared/journey-log.md

with activity line:

saved [[Projects/<ProjectName>]]

.

Confirm to the user in plain language what was saved. List each thing written.

Auto-Suggest Save

See

references/auto-suggest.md

. Suggestion only — never auto-save.

Important Notes

Edit tool for surgical updates only. Never rewrite a whole page (sync conflicts).
All content in bullet-point format. See
```
CLAUDE.md
```
for Logseq invariants.
When appending, place new entries at the end of the section, before the next
```
##
```
heading.
If
```
journals/
```
doesn't exist, create it (Bash
```
mkdir -p
```
) before writing the journal entry.