nextsession

name	nextsession
description	Use when starting or resuming a work session on the biasbuster project, to load current project state and re-establish the coding rules and session workflow before doing any work.
disable-model-invocation	true
allowed-tools	Read, Edit, Bash(git add:*), Bash(git commit:*), Bash(git push:*), Bash(git status:*), Bash(git diff:*), Bash(git switch:*), Bash(gh issue:*), Bash(gh pr:*), Bash(uv run pytest:*), Bash(uv run python:*), Bash(sqlite3:*)

Read HANDOVER.md and follow the instructions. Ask me if you have any questions.

Our general coding rules live in CLAUDE.md — read and honour them, especially the "STOP AND CHECK" list and the Python Coding Standards. On top of those, follow this session workflow:

1. All tests must pass before committing, unless I explicitly give permission otherwise. Run the suite with uv run pytest.
2. Before you start working, make sure HANDOVER.md and ROADMAP.md represent the current state of progress and are up to date. If not, update them before you start.
3. Avoid technical debt — if you find an error, fix it when possible; otherwise lodge it as an issue on GitHub.
4. When you are done, update HANDOVER.md and ROADMAP.md to reflect the current state of development and progress. Prune both to stay concise and under 500 lines if possible: focus on what still needs doing, and summarise briefly what has already been done. If you are not sure how to do this, ask me.
5. When the task is complete, stage the files you changed explicitly (never git add -A / git add . — personal skills and scratch files may be lying around untracked), commit, push, and open a PR to the main branch. Link the PR to the relevant GitHub issue if applicable, and include a clear description of the changes made and any relevant context for reviewers. If you are not sure how to do this, ask me.