checkpoint

Create a checkpoint by staging only the relevant changed files, committing with a descriptive message, and updating a TODO.md file that lists completed and remaining tasks. This preserves a clean history and clear record of what comes next.

Use docker compose exec to run commands inside the running container, such as ruff check and pytest against your app and shared packages directories. This ensures the checks run against the same environment as production.

git add -A stages everything, including .env files, credentials, node_modules, and unrelated changes from other tasks. Staging specific files keeps commits focused and prevents accidentally leaking secrets or mixing unrelated work.

A TODO.md should list completed tasks as checked items, remaining tasks as unchecked items, and a section for blockers or open questions discovered during the current wave. This gives anyone resuming the work immediate context.

Create a checkpoint after completing a wave in a multi-wave implementation or whenever you need to save progress and document remaining work. Regular commits suit isolated changes, while checkpoints combine committing with progress tracking and verification.