complete

Validate PLAN completion, update documentation, and merge branches to develop.

69|7|Updated Jan 19, 2026
One-click install
npx skills add https://github.com/TaylorHuston/local-life-manager --skill complete
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: complete
Source: https://github.com/TaylorHuston/local-life-manager/tree/main/.claude/skills/complete
Command: npx skills add https://github.com/TaylorHuston/local-life-manager --skill complete

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the finalization of completed work by ensuring validation, documentation updates, code reviews, and automated merges to develop in a repeatable, auditable process.

Core Features & Use Cases

  • End-to-end finalization: Validate PLAN completion, synchronize documentation, and create a final commit.
  • Mandatory reviews and audits: Enforce code reviews and security audits before merging.
  • GitFlow-aware merging: Automatically merge feature branches into develop and clean up branches.
  • Documentation and config updates: Update SPEC references and CHANGELOG entries to reflect the changes.

Quick Start

To finalize an active task, run /complete careerbrain 002. To finalize the current issue: /complete careerbrain.

Frequently Asked Questions about complete

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

FAQPage Schema
How do I automate Git merge and task finalization for completed work?

Automate code finalization by validating PLAN.md completion, updating SPEC and CHANGELOG files, enforcing mandatory code reviews, and executing a GitFlow merge to develop. This ensures repeatable, auditable merges for finished software tasks.

What is GitFlow-based merging and when is it needed for feature branches?

GitFlow-based merging integrates completed feature branches into the develop branch after validation. It is needed when finalizing software work to ensure documentation updates, mandatory reviews, and security audits pass before merging and cleaning up branches.

How do I enforce mandatory code reviews and security audits before a Git merge?

Enforce mandatory reviews and security audits before merging by automating the task finalization process. The workflow checks that code reviews and security audits pass, updates CHANGELOG entries, and creates a final commit before performing the branch merge.

Does the automated merge workflow require a PLAN.md file to run?

Yes, the automated merge workflow requires a PLAN.md file. It enforces PLAN.md completion to validate that all planned tasks are finished, synchronizes documentation like SPEC references, and creates a final commit before merging the feature branch.

What's the best way to update CHANGELOG and SPEC documentation during a merge?

The best way to update documentation during a merge is to automate it within the task finalization workflow. The process updates SPEC references and adds CHANGELOG entries to reflect changes, creates a final commit, and then merges the branch to develop.

Can I clean up feature branches automatically after merging to develop?

Yes, you can clean up feature branches automatically. The finalization workflow performs a GitFlow-aware merge into develop and handles branch cleanup as part of the end-to-end process after validations and documentation updates are complete.