arc-finish

To close git branches and issues truthfully at session end, verify remaining tasks and evidence before finalizing. Arc finish enforces a guardrail workflow requiring verification steps, ensuring issues close only when work is truly complete and reflecting outstanding tasks when deferred.

The best way to verify issue completion before pushing is applying an explicit verification step that checks goals and implementation evidence. Arc finish requires arc-verify before allowing final closeout claims, preventing premature issue closure and maintaining truthful branch state.

Sequential decision-making for git branch handoffs works by asking one question at a time to choose the next action. Arc finish guides you through native, single-question prompts to decide whether to close, defer, commit, push, or hand off work across related branches.

Yes, you can defer arc-tracked issues during a session handoff. Arc finish supports explicit per-step decisions, allowing you to maintain truthful issue state by deferring outstanding work rather than forcing premature closure when goals are not fully met.

You should not close an issue at the end of a development session if verification shows remaining tasks or incomplete goals. Arc finish enforces guardrails to prevent premature closeouts, requiring evidence-based confirmation before issues and branches are marked complete.

No, arc-finish has no external dependencies to manage branch state. It operates independently to guide verification of remaining tasks and maintain truthful issue and branch states through sequential, one-question-at-a-time prompts during session ends and handoffs.