finish-task

To finalize a beads task, you must verify the implementation against acceptance criteria, run quality gates including tests and UI checks, update documentation, commit and push changes, create a pull request, and perform a final sync to close the task.

Automating pull request creation and task closure requires verifying code through tests, updating necessary documentation, committing and pushing changes via git, creating a pull request, and syncing the final status to mark the task as closed in the beads system.

Finalizing a development task requires specific CLI tools installed, including gh for pull request creation, bd for beads task management, uv and pnpm for running quality gates, and make for executing scripts.

Yes, you can verify code quality before creating a pull request by running quality gates that include automated tests and UI checks, ensuring the implementation meets acceptance criteria before committing and pushing changes.

The best way to ensure documentation is updated before closing a beads task is to follow the guided prompts that check for necessary updates to README, CLAUDE.md, and other files during the finalization process.

Task completion requires verifying implementation against acceptance criteria to ensure all code is pushed, reviewed, and meets quality standards before the task is marked as closed in the beads system.