finalize

Installation
SKILL.md

FINALIZE — ready to publish, and provably so

Prepare the release and hand it over. Do not publish, merge, or tag anything until the user confirms in writing. Use the ready tools as-is — do not rewrite them, and never claim one ran when it did not.

Rules

  • No publish without explicit human confirmation. No auto-merge, no auto-publish, no auto-tag.
  • No claim without evidence. Every item in the release report points to a command, an output, or a file.
  • Use ready tools as-is. Record each tool with its version, or "not run" with the reason.
  • A check that did not run is never reported as passed.

Steps, in order

1. Prerequisites

Confirm orcinus-verify gave PASS and security-review gave PASS (or explicit exceptions) on the change. If either is FAIL or INCOMPLETE, stop and fix that first. Finalize does not override verification or security.

2. Docs and handoff

Installs
8
GitHub Stars
1
First Seen
Nov 6, 2026