savepointlisted

# Savepoint Use this skill to preserve or load coding-session state without relying on prior chat context. Default behavior: ```text /savepoint -> create or refresh `.savepoint/SAVEPOINT.md` /savepoint save -> same as default /savepoint load -> verify an existing savepoint and report whether continuation is safe /savepoint text -> response-only copy-paste handoff; no file recovery guarantee ``` Native slash-command support depends on the client. If slash prompts are not passed through, use `$savepoint` natural language requests. ## Rules - Stay in savepoint scope. Do not edit application code. - Do not run `/new`, `/status`, PTY/session rotation, threshold policy, or background process control. - Do not read references, `scripts/*.py`, or `evals/*.json` during normal use. - Prefer current files, Git state, and durable state files over chat memory. - Do not paste transcripts, full diffs, long logs, shell history, PRDs, ADRs, issues, or commits. - Reference existing artifacts by path, URL, branch, or commit. - Redact API keys, tokens, cookies, credentials, private keys, passwords, `.env` values, and PII as `<redacted>`; do not place raw secrets in semantic input files. - File savepoints must end with exactly one `SAVEPOINT_V1` marker block. - Keep top-level `SAVEPOINT.md` compact. Use generated `details/*.md` only when needed for recovery. ## Create / Save 1. Treat provided focus text, if any, only as next-session focus. 2. Capture repo/Git state and write