session-wrap

Capture local git changes and session activity into a timestamped per-project handoff file.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/JYHTHEGREAT/jyh-system --skill session-wrap-jyhthegreat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-wrap
Source: https://github.com/JYHTHEGREAT/jyh-system/tree/main/skills/session-wrap
Command: npx skills add https://github.com/JYHTHEGREAT/jyh-system --skill session-wrap-jyhthegreat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

session-wrap automates the tedious and error-prone process of summarizing development work at the end of a session, ensuring per-project handoff records, deduplicated lesson capture, and consistent memory updates instead of manual notes or ad-hoc text files.

Core Features & Use Cases

  • Per-project handoff files: Generates a timestamped handoff file in a project-scoped path to avoid cross-project overwrites.
  • Git-aware collection: Collects recent commits, diff stats, changed filenames, and uncommitted status when run inside a git repository.
  • Structured summary and lessons: Produces a concise session summary, next-actions list, document-sync hints, and extracts up to five lessons classified by type (error, insight, preference, gotcha, workflow).
  • Memory management: Appends lessons to project MEMORY.md and lessons.jsonl with ID sequencing, duplicate detection, archiving, and optional categorization via a local script.
  • Operational controls: Supports --dry-run to preview output and --confirm to require explicit user approval before writing files; resilient to non-git directories and various failure modes.
  • Use case: Run at the end of a feature branch to produce a handoff for reviewers, record lessons for the project memory, and mark plan phases as complete.

Quick Start

Run session-wrap in your project directory to generate a per-project handoff and append new lessons to MEMORY.md.

Frequently Asked Questions about session-wrap

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

FAQPage Schema
How do I automate git session handoffs and capture lessons at the end of a dev branch?

To automate git session handoffs, run a session wrap tool to collect recent commits, uncommitted status, and next tasks into a timestamped file. It appends extracted lessons to project memory files with deduplication and ID sequencing.

What is the best way to summarize local git changes for a project handoff?

Summarizing local git changes for a project handoff involves collecting diff stats, changed filenames, and active plan state into a concise summary. This process ensures per-project records avoid cross-project overwrites and capture next-actions.

Can I generate session handoff files in non-git directories?

Yes, you can generate session handoff files in non-git directories. The session wrap process handles non-git environments gracefully by skipping git-specific collection while still producing a timestamped handoff and updating memory files.

How do I prevent duplicate lessons when appending to MEMORY.md?

To prevent duplicate lessons in MEMORY.md, the session wrap process uses built-in duplicate detection and ID sequencing. It appends new entries to lessons.jsonl and archives existing ones to maintain a clean project memory.

Does the session wrap process support previewing output before writing files?

Yes, the session wrap process supports previewing output before writing files using a dry-run flag. It also offers a confirm flag to require explicit user approval before modifying handoff files, MEMORY.md, or lessons.jsonl.

What types of lessons can be extracted during a development session wrap up?

During a development session wrap up, you can extract up to five classified lesson types: error, insight, preference, gotcha, and workflow. These lessons are structured to document specific development challenges and process improvements.