session-close

End coding sessions with committed, pushed, and documented handoffs.

40|3|Updated Feb 8, 2018

Search Tags:#automation #workflow #handoff #git-push #session-cleanup

Ready to run

npx skills add https://github.com/jm96441n/dotfiles --skill session-close

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: session-close
Source: https://github.com/jm96441n/dotfiles/tree/main/.config/opencode/skill/session-close
Command: npx skills add https://github.com/jm96441n/dotfiles --skill session-close

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This protocol enforces a disciplined end-of-work session to ensure all changes are committed, pushed, and documented for a clean handoff.

Core Features & Use Cases

Enforces a mandatory push to remote before closing a session, preventing orphaned work.
Creates a clear handoff context by updating issues and providing status checks for the next session.
Coordinates deterministic steps (fetch, rebase, push) using the jj/bd toolchain to guarantee traceable history.

Quick Start

Follow the mandatory workflow to ensure all changes are committed, pushed, and ready for handoff.

Frequently Asked Questions about session-close

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

FAQPage Schema

How do I automate git push and handoff when ending a coding session?▼

Automating git push and handoff requires a deterministic workflow that fetches, rebases, and pushes changes before closing a session. This ensures all code, tasks, and notes are versioned and handed off cleanly without orphaned work.

What is a session cleanup workflow for personal projects and team handoffs?▼

A session cleanup workflow enforces a disciplined end-of-work routine where changes are committed, pushed to remote, and documented. It provides clear handoff context by updating issues and running status checks for the next session.

How do I prevent orphaned work when closing a coding session?▼

To prevent orphaned work when closing a coding session, enforce a mandatory push to remote before completion. This guarantees all local changes are versioned, traceable, and accessible to the next developer or future session.

Does this session handoff workflow work with jj and bd tools?▼

Yes, this session handoff workflow coordinates deterministic steps using the jj and bd toolchain. It applies fetch, rebase, and push operations with these tools to guarantee a traceable version history before final verification.

What's the best way to ensure an auditable hand-off for a team coding session?▼

An auditable hand-off requires enforcing a mandatory workflow with fetch, rebase, and push steps followed by a final verification. This creates traceable history and updates task context, ensuring the next session receives a clean, documented state.

When do I need to run a final verification before completing a session close?▼

A final verification before completing a session close is needed after applying fetch, rebase, and push steps. It confirms that all changes are successfully committed, pushed to remote, and ready for a clean handoff.