strata:save
/strata:save
Zapisuje notatkę z zakończonej pracy w bazie wiedzy, od razu albo jako szkic do przeglądu, zanim ginie kontekst.
- Autor
- gideondk ↗
- Repozytorium
- strata ↗
- Licencja
- MPL-2.0
- Ostatnia zmiana repozytorium
- 08.06.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 08.06.2026, bez odwołań do wycofanych modeli i API.
MPL-2.0, otwarta.
Co robi i kiedy
Zapisuje notatkę z zakończonej pracy w bazie wiedzy, od razu albo jako szkic do przeglądu, zanim ginie kontekst.
Wyzwalacze z opisu
Oryginalny opis (EN)
Capture a session note. Two modes, direct (write immediately) and draft (build a draft from git session state, present for review, save on accept). Invoke autonomously at the end of substantive work (decisions made, files touched, context risks being lost). Pass `--draft` (or invoke when the user says "draft a save", "nudge me with a save", "what would you save") for the interactive review flow. Default is direct write. Skip if purely exploratory or <5 turns.
Jak działa
- Two modes
- What to write (in a save body)
- --kind values
- Observe (autonomous grounded capture)
- Keep it quiet
- Safety
Podgląd SKILL.md
---
name: strata:save
description: Capture a session note. Two modes, direct (write immediately) and draft (build a draft from git session state, present for review, save on accept). Invoke autonomously at the end of substantive work (decisions made, files touched, context risks being lost). Pass `--draft` (or invoke when the user says "draft a save", "nudge me with a save", "what would you save") for the interactive review flow. Default is direct write. Skip if purely exploratory or <5 turns.
---
# strata:save
Persist what just happened so the next session can pick up where this one
Left off. Lands in `<vault>/<repo>/pr-context/<branch-slug>/<timestamp>--<initials>--<topic>.md`.
## Two modes
### Direct (default)
User says "save this as <topic>" or you decide to save autonomously.
1. Compose the note body in your reply.
2. Write:
```bash
"${CLAUDE_PLUGIN_ROOT}/bin/strata" save \
--topic "<topic>" --kind session <<'STRATA_NOTE'
<note body>
STRATA_NOTE
```
### Draft (interactive review)
User says "draft a save", "what would you save", or you're at the Stop-hook
nudge and want help. Build a draft from real git state, then ask before
writing.
1. Snapshot the session:
```bash
"${CLAUDE_PLUGIN_ROOT}/bin/run-python.sh" -c \
"import sys; sys.path.insert(0, '${CLAUDE_PLUGIN_ROOT}/scripts'); \
import session_state; \
print(session_state.draft_note_body(session_state.snapshot()))"
```
The draft has four sections: `What was done` (from commits), `In progress`
(from uncommitted), `Decided` (placeholder), `Left open` (placeholder).
2. Present the draft. Offer:
- **Accept** — save with the suggested topic
- **Edit** — apply changes (or fill Decided/Left open from conversation),
re-confirm
- **Skip** — abandon
3. On accept, pipe the final body through `strata save` with the topic
from the draft.
### Apply-draft (one-keystroke acceptance of a Stop-hook offer)
When the Stop hook stashes a pre-filled draft (it does this when the
session crossed a signal threshold: 3+ commits, or 1+ commit with 3+
uncommitted files, or 8+ uncommitted files), the user can save it as-is
with no further prompting:
```bash
"${CLAUDE_PLUGIN_ROOT}/bin/strata" save \
--apply-draft
```
The script reads `${PLUGIN_DATA}/pending-draft.json`, writes it to the
current branch's `pr-context/` folder, and clears the stash. Drafts older
than 24h are silently dropped (treat as no-op).
If the user wants to edit the draft first, snapshot it, present it, then
apply with the edited body (drop the stash via `import draft_store;
draft_store.clear_draft()` after, or let it expire naturally).
The stash only fires from the Stop hook when there's enough signal; the
user never sees a draft offer for trivial sessions.
## What to write (in a save body)
- **What was done** — 2-5 bullets.
- **Decisions made** — anything affecting future code, especially divergence
from CLAUDE.md or established patterns.
- **Open questions / blockers** — things deliberately left unresolved.
- **Files touched** — relative paths, no diffs.
No large diffs, no command transcripts, no build output. Prose for humans
and me-on-Monday.
## --kind values
- `session` (default) — general working note
- `review` — feedback received on this branch
- `investigation` — bug hunt or spike notes
- `handoff` — explicit "next person, do X" note
- `decision-draft` — early thinking that may graduate to an ADR
## Observe (autonomous grounded capture)
For a low-stakes, grounded breadcrumb you don't want to interrupt the user for,
use `--observe` (the single autonomous-write entry point). It writes a
`status: auto` observation, quarantined from recall until a human reviews it in
the dashboard. Grounding is required (`--source-file` and/or `--commit`):
```bash
echo "Commit bumped the retry budget 3→5; see the client." | \
"${CLAUDE_PLUGIN_ROOT}/bin/strata" save \
--observe --topic "retry budget bumped" \
--source-file "src/http/client.py" --commit "$(git rev-parse --short HEAD)"
```
Never for decisions / contested questions / domain definitions — those stay
human-ratified.
## Keep it quiet
Capture is plumbing, not the conversation. Don't narrate each step ("let me
write the session note, now the index…") — run the command and let its one-line
receipt (`✓ Strata: saved …`) be the confirmation. One short sentence of context
before the call is plenty; no play-by-play, and don't paste the script's path or
raw output back to the user.
## Safety
`strata save` runs a **warn-only** secret/PII pre-step before every write — it
advises on stderr if it spots credentials/identifiers but **never blocks** the
save. `/strata:lint` remains the explicit blocking scan; the pre-push git hook
is the final backstop. Still: don't paste identifiers, NHS numbers, postcodes,
or credentials — the vault is shared.
Wersje
W bazie nie ma innych skilli o nazwie strata:save.
Migawka bazy z 13.11.2026 · wersja paczki 31dc540372a9 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 90strata:procedure
Zapisuje procedurę, instrukcję, listę kontrolną lub sposób pracy zespołu jako notatkę w bazie wiedzy. - 95strata.handoff
Zamyka sesję: spisuje stan pracy, oczekujące punkty i blokery, żeby kolejna sesja mogła bezpiecznie wrócić do zadania. - 100using-strata
Przy starcie sesji kieruje pracę do właściwego skilla strata i wypisuje kontekst projektu: domenę, profil i kolejny krok. - 96context-management-context-save
Prawdopodobnie zapisuje kontekst sesji do późniejszego użycia, na podstawie nazwy skilla. - 90strata:correct
Poprawia, wycofuje lub uczy się z notatki w bazie wiedzy, gdy użytkownik wskaże błąd albo stwierdzi, że coś już nie obowiązuje. - 96context-management-context-save
Prawdopodobnie zapisuje bieżący kontekst pracy agenta, aby można go było przywrócić w późniejszej sesji.