session-wrapup

name	session-wrapup
description	Handles end-of-session housekeeping: committing code, pushing to remote, deploying, and summarizing progress. Prevents forgotten commits and undocumented progress. [GENERATED BY MOTIF — review and customize]

Session Wrapup

Handles end-of-session housekeeping: committing code, pushing to remote, deploying, and summarizing progress. Prevents forgotten commits and undocumented progress.

When to Use

• User says 'commit and push' or 'let's wrap up'
• User says 'deploy' at the end of a session
• Session appears to be ending (user says goodbye or thanks)
• Don't skip when: even small changes were made -- always commit

Instructions

1. Run git status to see what changed
2. Stage relevant files (ask if unsure which to include)
3. Commit with a descriptive message summarizing the session's work
4. Push to remote
5. If deployment is requested, follow project-specific deploy process
6. Summarize what was accomplished in 3-5 bullet points
7. Note any loose ends or TODOs for next session

Best Practices

• Write commit messages that describe the 'why', not just the 'what'
• Avoid: Don't bundle unrelated changes in one commit
• Always push after committing
• Avoid: Avoid committing secrets or .env files

Common Pitfalls

Problem	Solution
Forgetting to push after commit	Always push immediately after commit succeeds
Commit message is vague ('various changes')	Summarize the session's main accomplishment in the message

Key Constraints

• Never commit without a descriptive message
• Always push to remote after committing
• Never commit files containing secrets