session-close

To automate git commit and push at the end of a coding session, you can run an end-of-session ritual that inventories file modifications, stages changes, commits them, and pushes code to a remote repository.

The best way to save session learnings and update memory logs is to synthesize changes into a concise summary and integrate key decisions into persistent memory threads for future continuity.

Yes, session-close requires Git for version control and custom 'bd sync' commands for bead synchronization to properly save and sync your work.

You can inventory file modifications by executing an end-of-session workflow that automatically tracks, displays, and stages all modified files before committing and pushing code changes.

Yes, you can use session management workflows to prepare for the next session by prompting for a concise summary of learnings, changes, and outlining what needs to be done next.

The session-close workflow needs persistent memory threads to integrate session summaries and key decisions, ensuring context continuity and preventing data loss across future coding sessions.