skills.rest
Shmurdoc
ShmurdocCOMMUNITY
Explore all skills by this author →
GitHub

context-save

Capture git state, decisions, and pending tasks for session resumption.

Updated May 27, 2026
Search Tags:#development workflow#checkpoint#session resume#git state#session persistence#work progress#context save
One-click install
npx skills add https://github.com/Shmurdoc/EasyRide-v1 --skill context-save-shmurdoc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: context-save
Source: https://github.com/Shmurdoc/EasyRide-v1/tree/main/.opencode/skills/gstack-context-save
Command: npx skills add https://github.com/Shmurdoc/EasyRide-v1 --skill context-save-shmurdoc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the common problem of losing track of coding progress, key decisions, and pending work when pausing or switching development sessions, eliminating the need to re-trace steps or re-discover context when returning to a task.

Core Features & Use Cases

  • Full Git State Capture: Records current branch, uncommitted changes, and repository status to preserve exact code state at save time.
  • Decision & Work Logging: Saves key choices made during the session and pending remaining tasks to maintain work continuity.
  • Seamless Session Resume: Pairs with the /context-restore skill to let you pick up exactly where you left off in any future session.
  • Use Case: If you are mid-debug a production issue and need to pause for a meeting or end your workday, run this skill to save all context so you can resume the debug flow immediately without re-running tests or re-reading prior notes.

Quick Start

Use the context-save skill to save your current work progress, git state, and pending tasks so you can resume your session later without losing any context.

Frequently Asked Questions about context-save

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

FAQPage Schema
How do I save my coding session context before switching tasks?▼

To save coding session context, capture the full git state, key decisions, and remaining work items. This prevents losing track of coding progress and eliminates re-tracing steps when you return to the task.

How do I resume a development workflow after pausing mid-task?▼

Resuming a development workflow requires restoring previously saved session context. Pairing the saved git state and pending tasks with a complementary restore skill lets you pick up exactly where you left off instantly.

What is the best way to track uncommitted git changes when ending a workday?▼

Tracking uncommitted git changes when ending a workday involves recording the current branch, repository status, and uncommitted modifications. This preserves the exact code state at save time for future continuity.

Can I save work progress and pending tasks without committing to git?▼

Saving work progress without committing to git is possible by logging key choices and pending tasks separately. The skill records repository status and decisions, maintaining work continuity without requiring a git commit.

Does git state capture work for mid-debug production issue workflows?▼

Git state capture works effectively for mid-debug production issue workflows. Saving context during a debug flow prevents losing prior progress, allowing you to resume immediately without re-running tests or re-reading notes.

Related Skills

Explore More Software Engineering Skills→
TakSungTakSung

catchup

Track Git repository changes and summarize status, commits, and diffs.

Official
Basic
mi179mi179
1

context-save

Capture git state, decisions, and remaining work into a repeatable checkpoint.

Community
Advanced
kk20300113-pngkk20300113-png

context-save

Save git state, session decisions, and pending work items to a local store.

Community
Advanced
JeremiahEllingtonJeremiahEllington

checkpoint

Capture git state, decisions, and remaining work into resumable checkpoints.

Community
Advanced