ds-save

Preamble

"../lib/env.sh" "save"
_ROOT=$(git rev-parse --show-toplevel 2>/dev/null || echo "NOT_A_GIT_REPO")
_CHANGED=$(git diff --name-only 2>/dev/null | wc -l | tr -d ' ')
_NEW=$(git ls-files --others --exclude-standard 2>/dev/null | wc -l | tr -d ' ')
echo "ROOT: $_ROOT"
echo "CHANGED_FILES: $_CHANGED"
echo "NEW_FILES: $_NEW"

What this skill does

Save where you are right now. Like hitting Save in a game — you can always come back to this exact moment.

Step 1 — Check git is set up

If GIT_ROOT is . or ROOT is NOT_A_GIT_REPO:

"This project doesn't have saving turned on yet — which means if something breaks, there's no way to get back to where you are now. I can set it up in a few seconds. Want me to?"

If yes, run:

git init
git add -A

Tell the user: "Done — saving is now turned on. I'll create your first snapshot in a moment."

Then continue.

If no:

"OK, I won't set it up right now. Just know that without saving enabled, there's no undo if something goes wrong. You can always run /ds-save again later to set it up." Stop here.

Step 2 — First-time explanation (if no git history)

If LAST_COMMIT is no history yet, explain once:

"Quick note: I use something called 'git' to save your progress — think of it as a time machine for your project. Every time you save, I create a snapshot you can jump back to at any point. You'll never permanently break anything as long as you save regularly."

Step 3 — Summarize what changed

Look at the changed files:

git diff --name-only
git ls-files --others --exclude-standard
git diff --stat

Translate what changed into one plain English sentence. Follow the jargon rules in lib/plain-language.md. Examples:

• "Added the pricing page and updated the navigation to include a link to it"
• "Changed the button color to match your brand and fixed the header layout on mobile"
• "Updated the contact form and added a success message when it submits"
• "Added three new product cards to the homepage"
• "Fixed the typo in the footer and updated the copyright year"