gtsi-context-save

Captures git state, active tasks, decisions, and next steps into a per-author context file.

Updated May 21, 2026
One-click install
npx skills add https://github.com/gestaosian/gtsi-claude-skills --skill gtsi-context-save-gestaosian
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gtsi-context-save
Source: https://github.com/gestaosian/gtsi-claude-skills/tree/main/plugins/gtsi-ops-plugin/skills/gtsi-context-save
Command: npx skills add https://github.com/gestaosian/gtsi-claude-skills --skill gtsi-context-save-gestaosian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When pausing work for the day, switching machines, or approaching a risky operation, developers lose track of branch state, pending tasks, and decisions made during a session. This Skill preserves that working context in a structured Markdown file so it can be restored later. ## Core Features & Use Cases - Git State Capture: Records current branch, modified, staged, and untracked files plus the last three commits. - Task and Decision Logging: Collects active tasks via TaskList and summarizes key decisions, next steps, and blockers from the conversation. - Per-Author Storage: Detects the author from git config, slugifies the name, and writes a timestamped file under .gtsi/context/<author>/ which is git-ignored. - Use Case: Before leaving for the day, ask to save context; the Skill shows a summary for confirmation, then writes a file that gtsi-context-restore can reload on another machine. ## Quick Start Ask the assistant to save the current work context before pausing, and confirm the summary it presents so it writes the snapshot file under .gtsi/context/.

Frequently Asked Questions about gtsi-context-save

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

FAQPage Schema
How do I save my current work context in Claude Code?▼

Ask the assistant to save the context, for example before pausing or switching machines. It collects git status, recent commits, active tasks, decisions, and blockers, shows you a summary, and writes a timestamped Markdown file after your confirmation.

What information does a context snapshot capture?▼

A snapshot captures the current branch, modified, staged, and untracked files, the last three commits, all non-completed tasks, key conversation decisions, planned next steps, and external blockers such as pending tickets or dependencies.

Where are saved context files stored and are they committed to git?▼

Context files are stored under .gtsi/context/<author-slug>/ with a timestamped filename. The .gtsi/context/ directory is listed in .gitignore, so snapshots remain local, personal, and unversioned.

What happens if git user.name is not configured when saving context?▼

The Skill falls back to the USER environment variable and then to 'unknown' for the author slug. It warns you and suggests running git config user.name 'Your Name' so future snapshots are filed under your identity.

Can saving context overwrite a previous snapshot or leak credentials?▼

No. Filenames include a timestamp to guarantee uniqueness, and the Skill never overwrites an existing file without warning. It also explicitly avoids capturing credentials, tokens, or passwords pasted into the conversation.