start-session

To check your Git status and CI health before starting a development session, you can use an environment setup tool that verifies repository state, monitors open pull requests, and confirms infrastructure availability to provide an actionable briefing.

The best way to clean up old Git branches and prepare your Docker environment is to run an automated session initialization process that removes merged branches, verifies Docker service availability, and loads context from previous handoff files.

You can recover context from a previous development session by loading handoff files or devlogs, which automatically restore your prior environment state and surface critical backlog tasks for immediate focus.

Yes, you can prioritize backlog items and development tracks automatically by running a session initialization check that evaluates your current development tracks and surfaces the most critical tasks for your immediate focus.

Environment setup works without manually checking Docker service availability because the session initialization process automatically confirms infrastructure status alongside Git state and CI health checks before you begin coding.

You should use automated session management instead of manually checking your repository state because it comprehensively verifies Git status, CI health, and infrastructure while cleaning up merged branches to ensure a clean, up-to-date environment ready for productive work.