session-close

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.

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.

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.

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.

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.

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.