close-session

Save, sync, and push end-of-session work in Weave-managed repositories.

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/AGM1968/weave --skill close-session
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: close-session
Source: https://github.com/AGM1968/weave/tree/main/.claude/skills/close-session
Command: npx skills add https://github.com/AGM1968/weave --skill close-session

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This routine ensures end-of-session work is not lost by automating the save, sync, and push steps required to hand off tasks safely.

Core Features & Use Cases

  • End-of-session safety: files are saved and state is preserved across the weave graph.
  • Graph and Git synchronization: updates are synchronized with the weave storage and the GitHub repository.
  • Controlled handoff: ensures all pending work is captured and pushed before handing off to another session or user.

Quick Start

File remaining work as issues, run quality gates, close completed nodes, then sync and push to GitHub to finalize the session.

Frequently Asked Questions about close-session

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

FAQPage Schema
How do I safely hand off my Git work at the end of a coding session?

To safely hand off Git work at the end of a session, you need to save files, sync state across your task graph, and push updates to GitHub. This prevents data loss by ensuring no work is stranded locally.

What is the best way to sync Weave graph state before pushing to GitHub?

Syncing Weave graph state before pushing involves running a weave sync to update task nodes and preserve graph integrity. This ensures completed nodes are closed and pending issues are filed before the final Git push.

Do I need a Weave-managed repository to automate end-of-session cleanup?

Yes, end-of-session cleanup operates within Weave-managed repositories. The routine relies on the Weave graph to file remaining issues, close completed nodes, and guarantee no data is stranded during the handoff.

Can I skip the push step if my quality gates fail during session handoff?

No, the routine enforces a successful push requirement. It runs quality gates and files remaining work as issues first, ensuring all pending tasks are safely captured and pushed to GitHub before closing the session.

How does automated session handoff prevent stranded data in Git workflows?

Automated session handoff prevents stranded data by combining weave sync with a mandatory Git push. This guarantees all local changes, including newly filed issues and closed task nodes, are finalized in the remote repository.