full-finish

Orchestrate a governed post-task release pipeline with audits, validation, and versioned outputs.

8|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/Gold-b/claude-code-governance --skill full-finish
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: full-finish
Source: https://github.com/Gold-b/claude-code-governance/tree/main/bundle/skills/full-finish
Command: npx skills add https://github.com/Gold-b/claude-code-governance --skill full-finish

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes the risky final stage of software delivery by turning task completion into a governed release pipeline. It helps prevent stale commits, missed QA checks, incomplete documentation, versioning mistakes, and broken handoffs between sessions.

Core Features & Use Cases

  • Multi-phase release orchestration: Runs a strict sequence covering pre-close checks, retrospective detection, node-role validation, change analysis, QA/security review, documentation, version bumping, release creation, and client update follow-through.
  • Parallel specialist coordination: Dispatches QA, Security, Integration, Project Management, Documentation, and DevOps agents with explicit responsibilities and quality gates.
  • Governed release safety: Detects parallel-session drift, tagged-head retrospective scenarios, blocked releases, missing docs updates, and version mismatch risks before publishing.
  • Use case: After a complex backend, frontend, and infrastructure change, use this Skill to audit the work, update project memory and handoff docs, bump the patch version, build the installer, publish the release, and present a final release report.

Quick Start

Ask the AI to run the full-finish skill on the source repository to audit the completed work, prepare documentation and handoff, bump the version, and guide the release pipeline to completion.

Frequently Asked Questions about full-finish

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

FAQPage Schema
How do I automate a software release pipeline with QA and security checks?

A governed post-task release pipeline automates software release by orchestrating strict phase ordering for QA audits, security reviews, and version bumping. It validates release readiness by dispatching parallel specialist agents to audit changes before publishing versioned outputs.

What is a session handoff in a release pipeline and when do I need it?

A session handoff documents the current repository state and updates project memory to transfer context between work sessions. You need it after complex changes to prevent stale commits and broken handoffs by ensuring the next session understands completed release pipeline phases.

How do I prevent versioning mistakes and missed QA checks before a GitHub release?

To prevent versioning mistakes and missed QA checks before a GitHub release, enforce strict phase ordering with node-role validation and version synchronization. A governed pipeline detects version mismatch risks and blocked releases, verifying documentation and installers before publishing.

Does this release pipeline handle parallel-session drift and tagged-head retrospective scenarios?

Yes, the release pipeline handles parallel-session drift by detecting conflicting repository changes, and manages tagged-head retrospective scenarios by validating node roles before proceeding. This governed approach catches blocked releases and version mismatches before publishing.

What's the best way to coordinate DevOps and documentation updates for a software release?

The best way to coordinate DevOps and documentation updates is through parallel specialist agent execution within a governed release pipeline. This dispatches DevOps and Documentation agents with explicit responsibilities and quality gates to verify installer builds and update docs simultaneously.