# AGENTS.md

## Git Workflow
- After each completed code change, create a git commit automatically.
- Push only when the user explicitly requests it.
- Use small, focused commits.
- Use rich multi-line commit messages so `git log` is the primary step-by-step history for this repo.
- Commit messages should use:
  - a short imperative subject line
  - a blank line
  - concise body sections such as `Request:`, `Changes:`, `Verification:`, and `Next useful context:` when relevant
- Do not wait for the user to ask for a commit.
- Before committing, run a relevant verification command when practical.
- Do not include unrelated dirty files in a commit.

## Context Recovery
- Do not maintain a separate session-notes or handoff-log file.
- Use `git log` as the persistent project history.
- At the start of a new thread or whenever prior context matters, inspect recent commit subjects and commit bodies before making assumptions.
- Prefer checking both the current worktree and recent git history so uncommitted local state and committed project history are both visible.