session-wrapup
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]
Best use case
session-wrapup is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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]
Teams using session-wrapup should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/session-wrapup/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How session-wrapup Compares
| Feature / Agent | session-wrapup | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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]
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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