Menu
Protocol for properly ending a coding session - ensures all work is committed, pushed, and handed off correctly.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
| name | session-close |
| description | Protocol for properly ending a coding session - ensures all work is committed, pushed, and handed off correctly. |
| license | MIT |
| compatibility | opencode |
| metadata | {"category":"workflow","tools":"jj, bd"} |
Use this skill when ending a work session. This ensures all work is properly saved, pushed, and documented for the next session.
When ending a work session, you MUST complete ALL steps below. Work is NOT complete until jj git push succeeds.
MANDATORY WORKFLOW:
jj git fetch
jj rebase -d main
bd sync
jj bookmark set <bookmark-name>
jj git push -b <bookmark-name>
jj status # Verify push succeeded
jj git push succeedsBefore saying "done" or "complete", run this checklist:
[ ] 1. jj status (check what changed)
[ ] 2. jj describe -m "..." (describe current commit)
[ ] 3. bd sync (sync beads changes)
[ ] 4. jj bookmark set <name> (set bookmark on current commit)
[ ] 5. jj git push -b <name> (push to remote)
NEVER skip this. Work is not done until pushed.
Work with Atlassian products (Jira and Confluence) using the Atlassian CLI. Use when the user needs to create, view, edit, search, or manage Jira work items, projects, boards, sprints, filters, or Confluence spaces. Also use for authentication, user management, or automation of Atlassian workflows.
Guide for writing ast-grep rules to perform structural code search and analysis. Use when users need to search codebases using Abstract Syntax Tree (AST) patterns, find specific code structures, or perform complex code queries that go beyond simple text search.
Write Gremlin graph traversal queries for Neptune using the gremlin-go driver patterns in this codebase
Prefer Jujutsu (jj) over git for version control. Use squash workflow pattern where commits are described first, then changes are made in a scratch child commit and squashed into the parent.