dev-reset-workspace

To reset your git workspace to a clean main, this process removes stale branches, uncommitted changes, and lingering background tasks. It enforces phase-by-phase checks and prompts you to confirm destructive actions before proceeding.

The best way to clean up stale branches and uncommitted changes is a phase-driven workflow that stops background agents, switches to main, and prunes merged branches. It safely stashes uncommitted work instead of deleting it.

Resetting a repository workspace does not delete your uncommitted work. The workflow applies safe prompts and safeguards that stash or report uncommitted changes when appropriate, ensuring you do not lose data during the cleanup process.

To prune merged branches and clean up worktrees, run a phase-driven workspace reset workflow that switches to main, removes stale branches, and cleans up lingering worktrees. It verifies a clean state before completion to ensure a fresh starting point.

You should use a workspace reset workflow at the start of new development cycles and PR workflows to ensure a reproducible fresh starting point. It removes lingering background tasks and stale branches that could otherwise affect new work.