wrap-up

Execute an end-of-session checklist for shipping, memory updates, and self-improvement.

61|9|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/jonathanmalkin/jules --skill wrap-up-jonathanmalkin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wrap-up
Source: https://github.com/jonathanmalkin/jules/tree/main/.claude/skills/wrap-up
Command: npx skills add https://github.com/jonathanmalkin/jules --skill wrap-up-jonathanmalkin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures that every work session is properly concluded by handling essential end-of-session tasks, preventing data loss and maintaining project integrity.

Core Features & Use Cases

  • Session Retrospective: Automatically runs a deep retrospective to identify patterns and potential script candidates.
  • Report Generation: Creates a comprehensive session report detailing accomplishments, decisions, and next steps.
  • Terrain Update: Updates Terrain.md with session outcomes, ensuring project state is always current.
  • Code Commit: Stages and commits all session artifacts with a descriptive message.
  • Use Case: After a coding session, running /wrap-up will automatically generate a report of what was built, commit the code, and update the project's task list.

Quick Start

Use the wrap-up skill to finalize the current session and commit all changes.

Frequently Asked Questions about wrap-up

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

FAQPage Schema
How do I automate end-of-session code commits and documentation updates?

Automating end-of-session code commits and documentation updates requires running a checklist that generates a session report, updates project terrain files, and stages artifacts for commit. This process prevents data loss and maintains project integrity.

What is a session retrospective and how does it improve my coding workflow?

A session retrospective analyzes recent coding activities to identify behavioral patterns and potential script candidates. Automating this retrospective process helps capture session outcomes and informs continuous self-improvement.

How do I generate a session report and update project terrain documentation?

Generating a session report and updating terrain documentation involves executing an end-of-session checklist that records accomplishments and decisions. It automatically writes these outcomes to Terrain.md to keep project state current.

Do I need to run a determinism scan before finalizing a code session?

Yes, a determinism scan for script candidates is required before finalizing a code session. This scan identifies deterministic workflows suitable for automation before the retrospective and commit stages are executed.

What's the best way to prevent data loss when concluding a coding session?

The best way to prevent data loss when concluding a coding session is to execute an automated wrap-up checklist. This stages and commits all session artifacts with a descriptive message while updating project memory.