wrap

Record session learnings into CLAUDE.md and docs while reconciling TODO.md.

Updated Mar 15, 2020

Search Tags:#knowledge base #Claude Code #project documentation #Git commits #session wrap-up #TODO reconciliation

Ready to run

npx skills add https://github.com/GameDevFox/neko --skill wrap-gamedevfox

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: wrap
Source: https://github.com/GameDevFox/neko/tree/main/claude/skills/wrap
Command: npx skills add https://github.com/GameDevFox/neko --skill wrap-gamedevfox

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents valuable session learnings from being lost by turning a completed coding session into updated project memory and an accurate TODO tracker.

Core Features & Use Cases

Docs memory updates: Updates CLAUDE.md and docs/*.md using the session reflection checklist to keep future sessions aligned with what was learned.
TODO reconciliation: Removes previously completed checklist items and marks newly completed items based on what was actually finished this session.
Reviewable, approval-gated commit: Stages only the intended session changes and produces a clear before/after summary for user approval before committing.

Quick Start

Run /wrap to update CLAUDE.md, docs/*.md, and TODO.md, then review the proposed diff and approve the commit.

Frequently Asked Questions about wrap

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

FAQPage Schema

How do I update project documentation and TODOs after a Claude Code session?▼

To update project documentation after a Claude Code session, you can run a session wrap-up workflow that records learnings into CLAUDE.md and docs/*.md files while reconciling TODO.md based on completed tasks.

Can I automatically stage and commit Git changes when wrapping up session learnings?▼

You can stage and commit Git changes during session wrap-up, but the workflow requires explicit user confirmation. It produces a before/after summary for approval and must not commit any changes without your direct consent.

What is the best way to keep CLAUDE.md and TODO.md consistent across coding iterations?▼

The best way to keep CLAUDE.md and TODO.md consistent is applying a three-phase end-of-session cleanup workflow that updates docs memory, reconciles completed checklist items, and stages changes for approval-gated commits.

How does TODO reconciliation work when finalizing a coding session?▼

TODO reconciliation works by removing previously completed checklist items and marking newly completed items based on what was actually finished during the coding session, ensuring your task tracker stays accurate.

Do I need any external dependencies to update docs memory and track Git commits?▼

No external dependencies are required to update docs memory and track Git commits. The session wrap-up workflow operates directly on your project's CLAUDE.md, docs/*.md, and TODO.md files using standard Git staging.

Why should I use an approval-gated commit process for session wrap-up?▼

An approval-gated commit process prevents unintended changes from entering your repository by generating a clear before/after summary of doc updates and TODO reconciliation, requiring explicit confirmation before any Git commit occurs.