save skill
Saves work-in-progress by staging changes, committing with a WIP prefix, and pushing to a remote repository while keeping the task status as IN PROGRESS.
- GitHub stars
- 26
- Files
- 1
- Last commit
- Feb 26, 2026
- License
- MIT
- Allowed tools
- —
What does the save skill do?
save saves work-in-progress by staging changes, committing with a WIP prefix, and pushing to a remote repository while keeping the task status as IN PROGRESS.
Summary generated from the skill's SKILL.md.
About the save skill
Developers who need to pause their coding sessions without marking tasks as finished can use this skill to secure their current state. It automates the process of staging modified files, creating a commit with a WIP prefix, and pushing changes to a remote repository. This is specifically designed for scenarios like switching machines, ending a work session, or backing up work before a computer restart.
When an agent receives a command like /save or end session, it first runs git status and git diff --stat to show the user what has changed. It then uses AskUserQuestion to determine the task ID and whether to update the MASTER_PLAN.md file with a timestamped progress note. The workflow carefully excludes sensitive files like .env or dependency folders such as node_modules and .venv to ensure security. Unlike the /done command, this process skips running tests to prioritize speed and maintains the task status as IN PROGRESS.
What an agent can do with it
- 1Switching between different computersAn agent can save all current changes and push them to a remote repository so you can continue working on another machine.
- 2Ending a work sessionYou can use this to back up your current progress at the end of the day without marking the task as complete.
- 3Updating project documentationThe agent can add a timestamped progress note to your MASTER_PLAN.md file to track what was accomplished.
Written from the skill's SKILL.md. Every use case is checked against a quote from it.
How to install the save skill
Each command copies the skill folder into the client's skills directory. Restart the client or start a new session to load it.Install the save skill in Plugin
/plugin marketplace add endlessblink/master-plan /plugin install master-plan@master-plan
Install the save skill in Claude Code
~/.claude/skills/save/SKILL.md
$ npx degit endlessblink/master-plan/skills/save ~/.claude/skills/saveInstall the save skill in Claude Code (project)
.claude/skills/save/SKILL.md
$ npx degit endlessblink/master-plan/skills/save .claude/skills/saveInstall the save skill in Codex
~/.agents/skills/save/SKILL.md
$ npx degit endlessblink/master-plan/skills/save ~/.agents/skills/saveInstall the save skill in Gemini CLI
~/.gemini/skills/save/SKILL.md
$ npx degit endlessblink/master-plan/skills/save ~/.gemini/skills/saveInstall the save skill in Claude.ai
npx degit endlessblink/master-plan/skills/save save && zip -r save.zip save # claude.ai → Customize → Skills → + → Create skill → Upload a skill → save.zip
SKILL.md
View on GitHubSave Progress
Save work-in-progress and push to remote repository. Unlike /master-plan:done, this keeps the task status as IN PROGRESS — perfect for:
- Switching machines
- End of session but task not complete
- Before restarting your computer
- Backing up current work
Triggers
/master-plan:save- Main command- "save progress", "switch machine", "end session", "backup work"
Workflow
Step 1: Show Current State
Run these commands to show what changed:
git status
git diff --stat
Display a summary of modified files to the user.
Step 2: Get Task Information
Use AskUserQuestion to gather:
-
Task ID (header: "Task")
- Options: "Tracked task (enter ID)", "No task (just commit)"
-
Update MASTER_PLAN? (header: "Docs")
- Options: "No (just commit)", "Yes (add progress note)"
Then ask in plain text: "What's a brief summary of the progress? (1-2 sentences)"
IMPORTANT: Wait for user to provide the summary before proceeding.
Step 3: Update MASTER_PLAN.md (if requested)
If the user wants to add progress notes:
- Find the task's
###section in MASTER_PLAN.md - Add a progress note with timestamp
Format:
**Progress (YYYY-MM-DD):** [summary of what was done]
Keep status as IN PROGRESS — do NOT change to DONE.
Step 4: Stage Files
Stage all changed files EXCEPT:
.env*files (secrets)node_modules/,__pycache__/,target/,.venv/- Backup directories
- OS files (
.DS_Store,Thumbs.db)
Prefer staging specific files by name over git add -A.
Step 5: Commit
Create a WIP commit:
With task ID:
git commit -m "$(cat <<'EOF'
wip(TASK-XXX): progress summary
Co-Authored-By: Claude <noreply@anthropic.com>
EOF
)"
Without task ID:
git commit -m "$(cat <<'EOF'
wip: progress summary
Co-Authored-By: Claude <noreply@anthropic.com>
EOF
)"
Step 6: Push to Remote
git push
Step 7: Output Summary
## Progress Saved
- **Task**: TASK-XXX (or "No task")
- **Summary**: [what was done]
- **Commit**: [short hash]
- **Status**: Still IN PROGRESS
Ready to continue on another machine:
1. `git pull`
2. Continue working on TASK-XXX
Difference from /done
| Aspect | /master-plan:done |
/master-plan:save |
|---|---|---|
| Task Status | ✅ DONE | 🔄 IN PROGRESS (unchanged) |
| Commit prefix | feat(TASK-XXX): |
wip(TASK-XXX): |
| Tests required | Yes | No (skip for speed) |
| MASTER_PLAN update | Mark complete | Add progress note only |
| Use case | Task finished | Session end, machine switch |
Important Rules
- Do NOT mark task as DONE — The whole point is to save progress without claiming completion
- Do NOT run tests — Speed is the priority for session-end saves
- Always push — The goal is to make work available on another machine
- Ask before MASTER_PLAN changes — Some users may just want to commit/push
Files in this skill
1save skill questions
How do I install the save skill in Claude Code?
Run npx degit endlessblink/master-plan/skills/save ~/.claude/skills/save. Claude Code loads skills from ~/.claude/skills (all projects) or .claude/skills (one project) and uses a skill when its description matches the task.
Which clients can use the save skill?
Any client that reads the Agent Skills format: Claude Code, Codex, Gemini CLI and claude.ai (upload as a ZIP). Scripts in the skill run only where the client allows code execution.
How is saving progress different from marking a task as done?
Saving progress keeps the task status as IN PROGRESS and uses a 'wip' commit prefix, whereas marking as done changes the status to DONE and uses a 'feat' prefix.
When should I use the save skill?
You should use it when switching machines, ending a session without completing the task, restarting your computer, or simply backing up your current work.
Does this skill run tests before committing?
No, tests are skipped to prioritize speed during session-end saves.