close-session

Save session progress, clean temporary files, and generate session records.

2|1|Updated Dec 30, 2025
One-click install
npx skills add https://github.com/abdullahbeam/nexus-design-abdullah --skill close-session-abdullahbeam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: close-session
Source: https://github.com/abdullahbeam/nexus-design-abdullah/tree/main/00-system/skills/system/close-session
Command: npx skills add https://github.com/abdullahbeam/nexus-design-abdullah --skill close-session-abdullahbeam

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Without this skill, all progress on your tasks, updated project status, saved decisions, and session context are permanently lost when you close your Claude Code chat, forcing you to re-explain your work and rebuild everything from scratch in your next session.

Core Features & Use Cases

  • Automatic Progress Saving: Marks completed tasks, updates project status, and recalculates progress for all active Nexus projects at the end of every session.
  • Workspace Cleanup: Scans for and helps you manage temporary draft files in your root workspace folder to keep your environment organized.
  • Session Record Keeping: Generates dated session reports with work completed, decisions made, and next steps to provide full context for future sessions.
  • Navigation Map Updates: Automatically regenerates project and skill navigation maps to reflect your latest workspace state. Use Case: If you spent a 2-hour session finalizing wireframes for your product launch project, this skill will mark all related tasks as complete, save your design decisions to memory, clean up any draft wireframe files you no longer need, and create a session report so you can jump straight into user testing in your next chat.

Quick Start

Just say "done", "finish", or "wrap up" at the end of your Claude Code session to automatically trigger the close-session skill and save all your work.

Frequently Asked Questions about close-session

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

FAQPage Schema
How do I save session progress and prevent context loss when closing a workspace?

Saving session progress requires triggering the close-session workflow by saying "done" or "wrap up". It automatically marks completed tasks, updates project status, and generates a dated session report to preserve context continuity before the workspace closes.

What is automatic workspace cleanup and how does it manage temporary files?

Automatic workspace cleanup scans your root folder for temporary draft files and helps manage them to keep your environment organized. This process triggers at the end of a session to remove unnecessary drafts generated during project workflows.

How do I keep project context continuity across different chat sessions?

You maintain cross-session context continuity by generating dated session reports that document work completed, decisions made, and next steps. This record allows future sessions to immediately recover prior project status without re-explaining work.

Does session management automatically update project navigation maps?

Yes, session management automatically regenerates project and skill navigation maps to reflect your latest workspace state. This ensures your project workflow tracking remains accurate and up-to-date when you save work state at the end of a session.

When do I need to trigger progress tracking before closing my workspace?

You need to trigger progress tracking at the end of any skill or project workflow before closing your workspace. Simply say "finish" or "wrap up" to automatically apply task updates, save memory persistence, and clean temporary files.

What are the limitations of relying on manual memory persistence for project workflows?

Relying on manual memory persistence risks permanent loss of task updates, saved decisions, and session context when closing the workspace. Without an automated close-session trigger, you must manually re-explain your work and rebuild progress from scratch.