save
/save
Save the founder's work as a new version, wrapping git so they never type a git command. Trigger on "save my work", "save this", "save my progress", "commit my work", "checkpoint this", "save a version", or any plain request to record the current state. Records every changed file by name (never a blanket grab-everything) into one saved version with a plain-language message. If the privacy guard blocks the commit (a private name, a dash, an AI-attribution line, or a secret), the reason is surfaced and nothing is saved.
- Author
- ARCASSystems ↗
- Repository
- FounderOS ↗
- Licence
- MIT
- Last repository change
- 24.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 24.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Save the founder's work as a new version, wrapping git so they never type a git command. Trigger on "save my work", "save this", "save my progress", "commit my work", "checkpoint this", "save a version", or any plain request to record the current state. Records every changed file by name (never a blanket grab-everything) into one saved version with a plain-language message. If the privacy guard blocks the commit (a private name, a dash, an AI-attribution line, or a secret), the reason is surfaced and nothing is saved.
Triggers from the description
Original author description
Save the founder's work as a new version, wrapping git so they never type a git command. Trigger on "save my work", "save this", "save my progress", "commit my work", "checkpoint this", "save a version", or any plain request to record the current state. Records every changed file by name (never a blanket grab-everything) into one saved version with a plain-language message. If the privacy guard blocks the commit (a private name, a dash, an AI-attribution line, or a secret), the reason is surfaced and nothing is saved.
How it works
- Pre-flight
- Procedure
- Runtime honesty
- Rules
SKILL.md preview
---
name: save
description: >
Save the founder's work as a new version, wrapping git so they never type a git command. Trigger on "save my work", "save this", "save my progress", "commit my work", "checkpoint this", "save a version", or any plain request to record the current state. Records every changed file by name (never a blanket grab-everything) into one saved version with a plain-language message. If the privacy guard blocks the commit (a private name, a dash, an AI-attribution line, or a secret), the reason is surfaced and nothing is saved.
why: "Version control is the biggest literacy wall in onboarding. Wrapping it in one verb gives a non-technical founder full history and undo without learning git, and keeps the you-own-your-files promise real."
enhance: "Save often. Each save is a point you can undo back to later, so frequent saves make the restore verb far more useful."
allowed-tools: ["Bash", "Read"]
mcp_requirements: []
---
# Save
Runs on: local-exec - runs a local script; on a cloud surface I read the results, I do not run it.
Record the founder's current work as a new version. Wraps git so they never see a git command. Local only. This never pushes anywhere.
## Pre-flight
- If `core/identity.md` does not exist, stop with: `Founder OS not set up here. Run /founder-os:setup first.`
- If `scripts/caveman_git.py` does not exist, stop with: `Version control helper not found. Run /founder-os:update to install it.`
- If git is not installed or the folder has no `.git/` directory (a ZIP install that has not graduated yet), do not error. Say: `Version history is not on yet - your changes are still covered by session snapshots (say "what did you change" to see them). Want the full timeline? Say "own my history" and I will set it up for you.` Then stop, or run the `own-your-history` skill if they say yes.
## Procedure
1. Run `python scripts/caveman_git.py save`. To pass a short plain-language note the founder gave ("save my pricing rework"), use `python scripts/caveman_git.py save --message "<note>"`. Do not invent a note; the script writes an honest default if you pass none.
2. Read the script output and relay it in plain language:
- On success it prints `Saved.` and the list of files that changed. Tell the founder what was saved in one line.
- On a block it prints `Could not save.` and the guard reason. Explain in plain words what tripped the guard (a private name, an AI-attribution line, or what looks like a password or key), name the file and line the guard printed, and say that nothing was saved. Do not bypass the guard. Do not retry with a flag that skips it.
3. Never run `git add -A`, `git add .`, or `git push`. The script stages by path and commits locally; that is the whole job.
## Runtime honesty
This verb runs a local script. On a surface that cannot run a script (a web-only agent), say so plainly: you can show the founder what would be saved, but you cannot perform the save there. They run it in Claude Code, or on any local-runtime agent pointed at the folder.
## Rules
- Local only. Never push.
- Explicit staging only. Never `git add -A` or `git add .`.
- Never bypass the privacy guard. A blocked save means real content needs fixing, not skipping.
- No em dashes or en dashes in anything you write. Hyphens only.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · ARCASSystems/FounderOS | 90 | MIT |
| nigelng/nng-kit | 100 | MIT |
| erayozenn/BigHead-2ndBrain | 100 | MIT |
| agricidaniel/claude-obsidian | 100 | MIT |
| NourEldinShobier/handoff | 100 | MIT |
| arcfjmt/handoff | 100 | MIT |
| ryanonline1234/smart-compact | 100 | MIT |
| xtsoftwarelabs/neatcontext-plugins | 100 | MIT |
| adb-software-solutions/contextbrain-plugins | 82 | MIT |
Database snapshot: 13.11.2026 · package version 607432f74c93 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 1 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90restore
Undo the founder's OS back to an earlier saved version, non-destructively, wrapping git so they never type a git command. Trigger on "undo", "undo to before this morning", "restore to yesterday", "roll back", "go back to last week", "revert my changes", or any plain request to… - 100own-your-history
Turn on full version history for a Founder OS install that does not have it yet - the graduation step for ZIP installs. Trigger on "own my history", "turn on version history", "turn on full history", "install git", "set up version control", or when the save, history, or restore… - 100git-ops
Single front door for everything git and GitHub — saving work, getting the latest, backing up, and putting changes online. Routes plain-language requests to the right operation in the correct order, even when the user does not use git terms. Use whenever the user wants to save,… - 100task-save
This skill should be used when the user asks to "save current task", "save progress", "create task from context", "task-save", "break down tasks", "decompose work", or wants to capture current work state as structured tasks with dependency ordering. Usage: /task-save [--cwd… - 100checkpoint
Save progress checkpoint — git commit WIP and update Linear issue with progress comment. Use when the user says 'checkpoint', 'save progress', 'wip commit', or invokes /checkpoint. - 100context-update
Save a brief mid-session checkpoint to this workspace and update current state only when a priority or open thread changed. Use only when the user explicitly asks to checkpoint or save current progress.