Leave yourself an easy restart.
The last useful action in a session is often a short handoff to your future self. Record the working state while it is still clear. A session can end with a finished change or a named blocker; either deserves an accurate record.
- 01
Record the current state
Note the project path, branch, relevant changed files, and any work that was already present. Say which part of the task is complete. Do not describe a proposed edit as implemented or a suggested command as executed. Leave private credentials and unrelated conversation out of the note.
- 02
Attach the verification evidence
List the checks that ran and what they established. Include failures and checks you could not run. If a check happened before the final edit, flag that mismatch. The next session should not have to guess whether the current code was the version that passed.
- 03
Choose one next action
Name the smallest useful continuation: inspect a remaining error, review the diff, or start the next behavior slice. Explain any decision that needs input from someone else. On resuming, compare the note with the actual checkout before acting on it.
A useful finish
The next session can locate the work, understand its verification status, and begin one concrete action.
A session closeout
Summarize this session: objective, repository state, completed changes, checks actually run, unavailable verification, and one next action. Distinguish pre-existing work and new changes. Flag any evidence collected before the final edit. Keep the note concise.