issue-finish

To finish an issue, the workflow verifies the issue status is Done, commits and pushes remaining real work while correctly handling the pipeline eval index, removes issue artifacts, and creates a local cleanup commit without pushing it.

The issue completion guardrails hard-stop the process if the issue status is not Done, preventing the accidental closure of incomplete work and ensuring only fully validated issues are finalized.

Git handling uses a two-phase approach: it commits and pushes remaining real work first, then creates a separate local cleanup commit for artifact removal that is intentionally not pushed to the remote repository.

You can use it for worktree workflows named worktree-issue-N, standalone branches after issue implementation, and automated pipelines that generate intermediate tasks, determining the correct issue number from the branch or argument.

Pipeline-eval-index requires special handling during explicit staging to avoid committing it as standalone work, ensuring only actual remaining issue work is committed and pushed before artifact cleanup begins.

The best way is to run an issue completion workflow that defensively deletes leftover temp files, removes issue research or plan artifacts, and creates a local cleanup commit to keep the workspace tidy.