wrap

Commit changes and write a session memo to .claude/_NEXT_SESSION_MEMO.md.

Updated Feb 12, 2026
One-click install
npx skills add https://github.com/obenland/dotfiles --skill wrap-obenland
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wrap
Source: https://github.com/obenland/dotfiles/tree/main/claude/.claude/skills/wrap
Command: npx skills add https://github.com/obenland/dotfiles --skill wrap-obenland

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ends a coding session by automatically committing changes and generating a session memo that documents what shipped and the current state.

Core Features & Use Cases

  • Check changes and identify what needs to be included in the commit
  • Stage changes and create a clear, conventional commit message
  • Write a session memo to .claude/_NEXT_SESSION_MEMO.md describing shipped work and current status
  • Produce a concise wrap report summarizing what was completed and what remains

Quick Start

Run the wrap command at session end to commit changes and generate the session memo.

Frequently Asked Questions about wrap

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

FAQPage Schema
How do I automatically commit changes and generate a session memo when ending a Git workflow?

You can automatically end a session by committing changes and generating a session memo. This requires a Git repo and writes a conventional commit message alongside a documented summary to .claude/_NEXT_SESSION_MEMO.md.

What is the best way to document shipped work and current status before ending a coding session?

Documenting shipped work involves generating a session memo that describes what shipped and the current state. This process stages changes, creates a conventional commit, and writes a wrap report summarizing what was completed and what remains.

Does generating a session memo require a specific file path in my Git repository?

Generating a session memo requires the target path .claude/_NEXT_SESSION_MEMO.md within your Git repository. It writes the documented session summary describing shipped work and current status directly to this file.

How do I create a clean VCS history with conventional commit messages for a feature or bug fix?

Creating a clean VCS history requires staging changes and generating a clear, conventional commit message. This process identifies what needs to be included in the commit and produces a concise wrap report summarizing the work.

Can I use this workflow to check changes and stage only what needs to be included in the final commit?

Yes, this workflow checks changes and identifies what needs to be included in the commit before staging. It ensures a clean VCS history by staging the relevant changes and creating a conventional commit message for your feature or bug.

Why do I need a session memo if I am already making a Git commit?

A Git commit provides a clean VCS history, while a session memo documents what shipped and the current state for the next session. The memo targets .claude/_NEXT_SESSION_MEMO.md to summarize what was completed and what remains.