end_of_task

Finalize approved development tasks by committing changes, pushing branches, and archiving artifacts.

2|1|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/FourthWiz/claude_dev_workflow --skill end-of-task
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: end_of_task
Source: https://github.com/FourthWiz/claude_dev_workflow/tree/main/dev-workflow/skills/end_of_task
Command: npx skills add https://github.com/FourthWiz/claude_dev_workflow --skill end-of-task

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of closing out a reviewed development task by enforcing final quality checks, managing git push operations, aggregating session cost data, capturing lessons learned, and archiving task artifacts so nothing is forgotten and releases are clean.

Core Features & Use Cases

  • Pre-flight validation: Verifies an APPROVED review exists, runs tests, checks working tree cleanliness, branch sync status, and scans diffs for secrets.
  • Git ceremony: Commits remaining changes with conventional messages if requested, pushes the feature branch to origin, and reports push outcomes without creating pull requests.
  • Operational wrap-up: Aggregates cost data from the task ledger, prompts and records lessons learned, updates session state, and archives the task folder into the finalized artifacts area.
  • Use Case: When a developer has an approved review and passing tests, run this Skill to perform the final commit/push, collect cost and session data, archive planning artifacts, and produce a concise final report.

Quick Start

Run end_of_task to finalize the current approved task, push the branch to origin, capture lessons learned, aggregate costs, and archive the task artifacts.

Frequently Asked Questions about end_of_task

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

FAQPage Schema
How do I finalize a git branch after an approved code review?

To finalize a git branch after an approved code review, you need to commit remaining changes, run pre-flight checks, push the feature branch to origin, and archive planning artifacts. This ensures a clean, audited finalization step before creating a pull request.

What is the best way to archive task artifacts and capture lessons learned in git?

The best way to archive task artifacts and capture lessons learned is to use an automated workflow that moves planning folders into a finalized artifacts area while prompting for session insights. This prevents forgotten files and keeps releases clean.

How do I aggregate development costs and session data before pushing a feature branch?

You aggregate development costs and session data by parsing a task cost ledger with timeout-handled lookups and updating session state. This occurs during the finalization process alongside running tests and pushing the feature branch.

Does the end_of_task workflow create pull requests automatically?

No, the end_of_task workflow does not create pull requests automatically. It performs pre-flight validation, pushes the feature branch to origin, and reports push outcomes, leaving the actual pull request creation as a separate manual step.

When should I run a task finalization workflow in my local repository?

You should run a task finalization workflow in your local repository when a development task has an APPROVED review and passing tests. It provides a safe step to commit changes, scan diffs for secrets, push branches, and archive artifacts.

Can I use conventional commit messages when finalizing my git workflow?

Yes, you can use conventional commit messages when finalizing your git workflow. The finalization process commits remaining changes with conventional messages if requested before pushing the feature branch to origin.