wrap

Automate end-of-session cleanup and learning capture for Claude Code sessions.

282|23|Updated Jan 3, 2026
One-click install
npx skills add https://github.com/team-attention/stanford-cs146s-kr --skill wrap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wrap
Source: https://github.com/team-attention/stanford-cs146s-kr/tree/main/.claude/skills/wrap
Command: npx skills add https://github.com/team-attention/stanford-cs146s-kr --skill wrap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the end-of-session cleanup and documentation generation for Claude Code sessions, saving time for engineers during project wrap-ups.

Core Features & Use Cases

  • Automated session cleanup: Automatically organize notes, unfinished tasks, and learning reflections at session end.
  • CLAUDE.md update proposals: Suggest structured CLAUDE.md improvements based on session findings.
  • Workflow automation: Detect repetitive patterns and surface automation opportunities for future sessions.

Quick Start

Use the wrap skill to tidy up and summarize learning at the end of a Claude Code session. The primary command is /wrap, with optional flags.

Frequently Asked Questions about wrap

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

FAQPage Schema
How do I automate Claude Code session cleanup and learning capture?

You can automate session cleanup by running the /wrap command at the end of a Claude Code session to organize notes, detect repetitive automation opportunities, and generate learning summaries.

How do I propose updates to CLAUDE.md after a coding session?

To propose CLAUDE.md updates, run the /wrap command and it will automatically analyze session findings to suggest structured improvements for your project documentation.

Can I run a session wrap-up without committing changes to the repository?

Yes, you can perform a non-commit run by using specific optional flags with the /wrap command to analyze and organize session learnings without altering repository state.

What is the best way to detect repetitive workflow patterns for automation?

The best way to detect repetitive patterns is to trigger a wrap-up analysis using the /wrap command, which surfaces workflow automation opportunities based on your session activity.

Does session wrap-up support quick updates for fast documentation generation?

Yes, session wrap-up supports quick updates through optional flags on the /wrap command, allowing you to rapidly tidy up notes and generate learning reflections.