log-session

name	log-session
description	Write or update a dev/log entry documenting this working session — the human↔agent collaboration record. Use when the user says "log this session", runs $log-session, or before any commit that changes code (the pre-commit hook requires a staged dev/log entry).

Log this working session

Write a session-log entry for the current working session.

1. Read dev/log/TEMPLATE.md and fill every section per its own instructions.
2. Create dev/log/<today's date, YYYY-MM-DD>-<short-kebab-case-topic>.md. If an entry for today and this topic already exists, update it instead of creating a duplicate.
3. Four points of emphasis:
   • Use direct, concise, factual prose. Record decisions and results without discursive narration, rhetorical framing, or repeated summaries.
   • Never include credentials or secrets. Redact private personal paths, home directories, usernames and contact details, internal hostnames and IP addresses, cluster accounts and allocation/job IDs, and private repository or workspace names. Use neutral placeholders; information the human explicitly approves as public may remain.
   • Quote the user's key prompts lightly copy-edited and privacy-redacted in blockquotes, including mid-session redirections. Do not preserve private literals for quote fidelity.
   • Be candid and specific in "Human interventions" — that section drives rule improvements.
4. If a lesson generalizes, propose a concrete diff to AGENTS.md or the matching .claude/rules/ file, but do not apply it without the user's approval.
5. Show the entry to the user for review before finishing.
6. If a commit is coming next, stage the entry (and any approved rule changes) so it ships in the same commit as the code — the pre-commit hook requires this.