session-wrap

Capture session decisions and generate handoff documents from Git state.

2|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/hamzaPixl/pixl-ai --skill session-wrap-hamzapixl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-wrap
Source: https://github.com/hamzaPixl/pixl-ai/tree/main/packages/crew/skills/session-wrap
Command: npx skills add https://github.com/hamzaPixl/pixl-ai --skill session-wrap-hamzapixl

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

End-of-session wrap-up that captures key decisions and handoff artifacts to ensure decisions are not lost during transfer and work can resume with full context, improving continuity and reducing rework.

Core Features & Use Cases

  • Capture and append decisions to .claude/memory/decisions.jsonl for durable traceability.
  • Generate a portable handoff document at .context/session-handoff-{date}.md to share with teammates.
  • Integrate with Git and task state to summarize current work, status, and important files for onboarding or transfer.

Quick Start

Initiate the end-of-session wrap-up to automatically save decisions and generate a handoff document.

Frequently Asked Questions about session-wrap

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

FAQPage Schema
How do I automate session handoff and preserve decisions for my team?

Automating session handoff preserves decisions by reading Git state and task context, appending records to a decisions.jsonl file, and generating a transfer-ready handoff document for your team.

What is a session wrap-up workflow in software engineering?

A session wrap-up workflow captures key decisions and handoff artifacts at the end of a work period, ensuring context is not lost during transfer and work can resume without rework.

How do I generate a handoff document from Git context for a project transfer?

Generating a handoff document from Git context involves reading current repository state and task status, then outputting a portable markdown file summarizing work for onboarding teammates.

Does this decision-tracking workflow work without specific dependencies?

Yes, this decision-tracking workflow operates without external dependencies, requiring only a Git repository to read state and generate the handoff markdown file.

Where are session decisions stored for durable traceability?

Session decisions are stored by appending them to a memory file named decisions.jsonl, providing durable traceability across multiple work sessions and team transfers.