skills.rest
JuChLi
JuChLiCOMMUNITY
Explore all skills by this author →
GitHub

save

Save project progress with Git status to a .claude/progress.md file.

Updated Feb 15, 2026
Search Tags:#git#workflow#commit#save#archive#progress
One-click install
npx skills add https://github.com/JuChLi/claude-dotfiles --skill save-juchli
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: save
Source: https://github.com/JuChLi/claude-dotfiles/tree/main/skills/save
Command: npx skills add https://github.com/JuChLi/claude-dotfiles --skill save-juchli

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill allows you to save your current project's progress, including code changes, commit history, and a summary of your work, to a file for later retrieval.

Core Features & Use Cases

  • Save Current State: Captures Git status, recent commits, and staged changes.
  • Progress Archiving: Automatically archives previous progress to a history file.
  • Git Integration: Commits and pushes changes to a remote repository.
  • Use Case: Before taking a break or switching tasks, use /save to create a snapshot of your work. Later, you can use /load to resume exactly where you left off.

Quick Start

Use the save skill to store your current project's progress.

Frequently Asked Questions about save

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I save my Git workflow progress to disk before switching tasks?▼

To save Git workflow progress, this skill captures Git status, recent commits, and staged changes into a `.claude/progress.md` file, automatically archives the previous snapshot to `.claude/progress-history.md`, and pushes everything to your remote repository.

What is the best way to archive project progress and commit changes to Git?▼

The best way to archive project progress is using an automated script that writes current Git status to `.claude/progress.md`, moves old progress to `.claude/progress-history.md`, commits changes with a chore message, and pushes to the remote repository.

Does saving project progress require a specific Git repository setup?▼

Saving project progress requires an existing Git repository with a configured remote. The skill automatically ensures `.claude/` files are ignored by Git before committing and pushing changes to the remote repository.

How does progress archiving work when saving project state to disk?▼

Progress archiving works by automatically moving the existing `.claude/progress.md` file to `.claude/progress-history.md` before generating a new progress snapshot, ensuring previous Git commit history and staged changes are preserved.

Can I resume work after saving Git status and staged changes to disk?▼

You can resume work after saving Git status and staged changes to disk by retrieving the generated `.claude/progress.md` file later to review your previous work summary and exact repository state.

Why does saving project progress automatically push commits to a remote repository?▼

Saving project progress automatically pushes commits to a remote repository to ensure your work snapshot and code changes are safely backed up remotely, preventing any loss of progress between tasks.

Related Skills

Explore More Software Engineering Skills→
chrisliu298chrisliu298
1

push

Stage all changes, commit with repository conventions, and push to the remote.

Community
Intermediate
aslaiiaslaii

gsd-resume-work

Restore project state and route to the next command from checkpoints.

Community
Advanced
borkwebborkweb
7

commit-writer

Generate conventional git commit messages from staged diffs and repository history.

Community
Intermediate
biwakonbubiwakonbu

git-commit

Stage changes and generate descriptive Git commit messages automatically.

Community
Basic