close

name	close
description	Close a work session in this repo — update koder/STATE.md with what changed and the next step, clean up accidental or temporary repo artifacts, and leave a clear handoff. Use when the user says "close session", "wrap up", "end session", "handoff", or invokes "/close".

Close Session Workflow

When the user asks to wrap up or close the current session, run this sequence:

1. Review the session changes

• Check git status --short and git diff --stat
• Separate the work from this session from unrelated user changes
• Do not revert unrelated changes you did not make

2. Update koder/STATE.md

• Update the Updated: date
• Keep the document as a thin Past / Present / Future handoff
• Add only the latest completed milestone and links to durable detail
• Update issue or plan statuses only when work was actually completed or a new blocker was clearly discovered
• Rewrite the Future section so the next agent can resume without reconstructing context
• Put durable change history in CHANGELOG.md, release verification in koder/releases/, and issue-specific detail in koder/issues/ or koder/plans/

3. Clean up repo artifacts

• Remove temporary files, scratch notes, or mistaken tracking docs created during the session
• Keep durable artifacts that are part of the intended result
• If cleanup would discard ambiguous work, ask the user instead of guessing

4. Commit and clean the repo

• Stage all session changes (code, docs, STATE.md updates) and commit with a clear message summarizing the session's work
• Do NOT stage files that look like secrets, credentials, or large binaries — flag them to the user
• After committing, run git status --short to confirm a clean working tree
• If unrelated uncommitted changes remain, leave them alone — do not revert or commit work you did not produce

5. Verify the handoff

• Run the relevant tests or verification commands if code or docs changed
• Give the user a concise summary of what changed, the commit, and any remaining follow-up
• The goal: the next /open should see a clean repo and an accurate koder/STATE.md

Notes

• Do NOT create or close issue docs unless the user explicitly asks
• Do NOT build, install, or publish anything unless the user explicitly asks
• If koder/STATE.md is already accurate, keep the update minimal rather than churning it