Wrap up a coding session by committing, pushing, creating PRs, syncing docs, and saving open items to memory. Use at the end of a work session.
Ensure all work from the current session is committed, pushed, documented, and open items are persisted.
Gather information about all repositories touched in this session:
git status
git diff --stat
git diff --cached --stat
git log --oneline -10
git branch --show-current
If not inside a git repo, ask the user which repo(s) to wrap up.
For each set of uncommitted changes:
feat:, fix:, refactor:, chore:).env files or secrets — warn if detectedIf there are no uncommitted changes, skip to Step 3.
git rev-list --left-right --count origin/$(git branch --show-current)...HEAD 2>/dev/null
git push -u origin $(git branch --show-current)
gh pr list --head $(git branch --show-current) --json number,title,url
main/master:
gh pr createCheck if documentation matches the current code state:
README.md, CHANGELOG.md, docs/ directorydocs: update [what] to reflect [change]If no documentation exists or docs are already in sync, skip to Step 6.
Identify work that is still in progress or needs follow-up:
Present a concise wrap-up to the user:
Session Wrap-Up:
- Commits: [count] new commits
- Pushed: [branch] -> origin
- PR: [URL or "none needed"]
- Docs: [updated / already in sync / none found]
- Open items: [count, brief list]
When you notice something that would improve this skill: