save

Name: save
Availability: InStock
Author: endlessblink

Save in-progress work and push updates to a remote repository.

Updated Nov 29, 2025

Search Tags:#git #workflow #backup #remote #version-control #in-progress #save-progress

Ready to run

npx skills add https://github.com/endlessblink/flow-state --skill save-endlessblink

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: save
Source: https://github.com/endlessblink/flow-state/tree/main/.claude/skills/save
Command: npx skills add https://github.com/endlessblink/flow-state --skill save-endlessblink

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Save in-progress work and push updates to a remote repository, enabling continuity across devices without prematurely marking tasks as DONE.

Core Features & Use Cases

Preserve in-progress state across devices by saving work-in-progress and pushing updates instead of marking tasks DONE.
Optional MASTER_PLAN updates to document progress notes when requested.
Deterministic staging/commit workflow that excludes sensitive paths (e.g., .env*, backups/, node_modules/, and lockfiles) to accelerate session-end saves.

Quick Start

Execute a save to record your in-progress work and push updates to the remote repository.

Frequently Asked Questions about save

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

FAQPage Schema

How do I backup in-progress work to a remote git repository without marking tasks as done?▼

To backup in-progress work to a remote git repository without marking tasks done, stage changes while excluding sensitive paths and create a WIP commit before pushing updates. This preserves your current state across devices.

How does a WIP commit workflow handle sensitive files like .env and lockfiles?▼

A WIP commit workflow handles sensitive files by deterministically excluding paths like .env, backups/, node_modules/, and lockfiles during staging. This ensures only safe project files are committed and pushed to the remote repository.

Can I update MASTER_PLAN.md when saving git progress across machines?▼

Yes, you can update MASTER_PLAN.md when saving git progress across machines. The workflow optionally documents progress notes within the file before staging changes and creating the work-in-progress commit.

What is the best way to save git progress when ending a session on one machine and switching to another?▼

The best way to save git progress when ending a session and switching machines is to gather task context, stage changes excluding sensitive paths, create a WIP commit, and push updates to your remote repository for continuity.

Why exclude lockfiles and node_modules when pushing work-in-progress updates?▼

Excluding lockfiles and node_modules when pushing work-in-progress updates accelerates session-end saves by preventing unnecessary file bloat in the remote repository. This deterministic staging focuses only on essential source changes.