finish-task

Name: finish-task
Availability: InStock
Author: josephneumann

Verify implementation, run quality gates, update documentation, and close a beads task.

4|Updated Jan 7, 2026

Search Tags:#automation #code review #pull request #git workflow #beads #task completion

Ready to run

npx skills add https://github.com/josephneumann/claude-corps --skill finish-task-josephneumann

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: finish-task
Source: https://github.com/josephneumann/claude-corps/tree/main/skills/finish-task
Command: npx skills add https://github.com/josephneumann/claude-corps --skill finish-task-josephneumann

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, bd, uv, pnpm, make, and includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of completing a development task by ensuring all necessary verification, documentation, and code management steps are followed before closing it out.

Core Features & Use Cases

Verification: Ensures code quality through tests and UI checks.
Documentation: Prompts for necessary updates to README, CLAUDE.md, etc.
Code Management: Guides through committing, pushing, and creating pull requests.
Task Closure: Automates the final steps of closing a task in the beads system.

Quick Start

Use the finish-task skill to finalize the work for beads task 'feat-user-auth-flow'.

Frequently Asked Questions about finish-task

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I finalize and close a beads task after finishing development?▼

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.

What steps are required to automate pull request creation and task closure in a git workflow?▼

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.

Does finalizing a development task require specific CLI tools installed?▼

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.

Can I use this process to verify code quality before creating a pull request?▼

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.

What is the best way to ensure documentation is updated before closing a beads task?▼

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.

Why does task completion require verifying implementation against acceptance criteria?▼

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.