ag-saude-sessao

To run a development session health check, execute a read-only diagnostic that scans for concurrent processes, config corruption, and orphaned stashes without modifying state. This proactively detects stability risks and prevents data loss before you continue working.

A development session diagnostic checks for concurrent Claude instances, config integrity issues, orphaned stashes, abandoned worktrees, environment variable corruption, and disk or memory pressure. It reports these findings read-only to safeguard your ongoing work.

Yes, you can diagnose concurrent processes and abandoned worktrees using a read-only health check that reports status without modifying any state. It safely identifies environmental issues like resource pressure and config corruption while keeping your data intact.

You should run a session health check at startup or when the environment behaves unexpectedly. Performing these read-only diagnostics proactively detects concurrent processes, environment variable corruption, and resource pressure to prevent failed work.

Your development environment may seem broken due to config corruption, orphaned stashes, or disk and memory pressure. You can diagnose these issues by running a read-only session health check that identifies concurrent processes and reports status without modifying state.

The best way to detect orphaned stashes and environment variable corruption is to run a read-only session health diagnostic. It proactively identifies these stability risks alongside abandoned worktrees and concurrent processes to prevent data loss.