skills.rest
leomleao
leomleaoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

save-context

Append session entries to [TICKET_ID]_context.md in the ticket output folder.

Updated Aug 23, 2026
Search Tags:#automation#markdown#ticket#session#handover#save-context
One-click install
npx skills add https://github.com/leomleao/tct-cowork-plugin --skill save-context-leomleao
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: save-context
Source: https://github.com/leomleao/tct-cowork-plugin/tree/main/plugins/assistant/skills/save-context
Command: npx skills add https://github.com/leomleao/tct-cowork-plugin --skill save-context-leomleao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Write a session handover file to [TICKET_ID]_context.md in the ticket's output folder at the end of every command. This file is the handover record — a future AI session should be able to open it and understand exactly where things stand.

Core Features & Use Cases

  • Writes or appends a standardized session entry to the ticket's [TICKET_ID]_context.md file, ensuring continuity across commands and sessions.
  • Stores the context in the correct per-ticket folder [OUTPUT_ROOT]\[CLIENT_PREFIX]\[TICKET_ID] - [CHANGE_TITLE] with the filename [TICKET_ID]_context.md.
  • Handles daily session sequencing (e.g., Session YYYY-MM-DD, Session YYYY-MM-DD (2), etc.) to preserve a complete history.

Quick Start

Run save-context after each command to append the session entry to the ticket's context file.

Frequently Asked Questions about save-context

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

FAQPage Schema
How do I persist session context across multiple ticket work commands?▼

You can persist session context by appending a standardized Markdown entry to a [TICKET_ID]_context.md file after each command, allowing future AI sessions to understand exactly where the ticket work stands.

What is a session handover file and when do I need it for automation workflows?▼

A session handover file is a persistent Markdown record that preserves the state of sequential ticket work. You need it for per-ticket automation workflows where context must be handed off across multiple AI sessions.

How do I automatically save Markdown session logs in specific ticket directories?▼

To save Markdown session logs in specific ticket directories, configure the output path as [OUTPUT_ROOT]\[CLIENT_PREFIX]\[TICKET_ID] - [CHANGE_TITLE], and the system will create the folder if necessary before writing the file.

Can I maintain a chronological history of daily sessions in a Markdown handover file?▼

Yes, you can maintain a chronological history by appending new entries with daily session sequencing, such as Session YYYY-MM-DD and Session YYYY-MM-DD (2), to preserve a complete record of all ticket work.

What is the best way to automate context handover for per-ticket AI sessions?▼

The best way to automate context handover is to append a persistent [TICKET_ID]_context.md file using a fixed Markdown structure, which captures the exact state of the work after every executed command.

Related Skills

Explore More Content & Communication Skills→
denis-pingindenis-pingin

fixme-tickets-md

Manage session-scoped bug tickets as markdown files with YAML frontmatter.

Community
Advanced
semicolon-devteamsemicolon-devteam

summarize-meeting

Summarize STT transcripts and meeting notes into discussion and decision summaries.

Official
Advanced
adriaanmostert1976-labadriaanmostert1976-lab

prompt-master-codehandover

Convert Cowork builds into Markdown handover prompts for Claude Code.

Community
Advanced
desirecoredesirecore
2

markdown

Create, edit, and organize Markdown documents for reports and notes.

Official
Basic