finalize

Verifies, vets, and prepares a draft pull request for squash merge with attestation.

Updated Nov 17, 2025
One-click install
npx skills add https://github.com/vzakharov/vovazakharov.com --skill finalize-vzakharov
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finalize
Source: https://github.com/vzakharov/vovazakharov.com/tree/main/.claude/skills/finalize
Command: npx skills add https://github.com/vzakharov/vovazakharov.com --skill finalize-vzakharov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Landing a branch safely requires many easy-to-forget steps: running the vet suite, merging the base branch, cleaning working artifacts, reconciling the squash message, and recording what was actually verified. This Skill automates that entire land-prep sequence so nothing ships unverified or leaves transient files on the trunk. ## Core Features & Use Cases - Full land-prep pipeline: ensures a draft PR exists, runs quality passes and ./scripts/vet.sh, merges origin/<base>, sweeps working-artifact directories (docs/issue/, docs/pr/, docs/plans/, docs/remove-before-merging/), marks the PR ready, and reconciles the squash message. - Attestation record: posts or edits a sticky finalize-attestation PR comment documenting exactly what was verified, against which base SHA, including honest no vet no-op attestations for docs-only diffs. - Guarded auto-merge: /finalize and merge squash-merges only when the run was uneventful, with an explicit stand-down checklist covering conflicts, red CI, unanswered review feedback, and base movement. - Use Case: After finishing a feature branch, run /finalize to vet the diff, merge the latest base, clean up plan and PR-export artifacts, post the verification attestation, and hand the operator a ready-to-merge PR. ## Quick Start Ask the assistant to run /finalize on the current branch to vet, clean up, and prepare the pull request for review.

Frequently Asked Questions about finalize

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

FAQPage Schema
How do I prepare a GitHub pull request for merge?

Run /finalize on the branch: it ensures a draft PR exists, runs the vet suite, merges the base branch, removes working-artifact directories, marks the PR ready, reconciles the squash message, and posts an attestation comment recording what was verified.

How do I squash-merge a PR with the GitHub CLI?

Use gh pr merge <n> --squash --subject <title> --body-file <file>. This Skill only does that under the 'and merge' flag, and only when the run was uneventful — no conflicts, no red CI, no unanswered review feedback, and no base movement.

What does the finalize attestation comment contain?

It records the verified commit SHA, the base branch SHA, the vet result, CI status, and any dispatched CI-only buckets. In 'no vet' docs-only mode it states that verification was a deliberate no-op and why, so a missing record is never ambiguous.

When should I use the no vet mode?

Use it only for diffs with nothing to verify — markdown, top-level docs, or read-only reference data. It skips the vet run and bucket dispatch but still posts the attestation; if any vet check would have had something to say, the mode was misapplied.

Why does finalize refuse to merge even with the and merge flag?

It stands down when the run required judgment: authored fixes to pass vet, merge conflicts, red CI runs, substantive squash-message rewrites, base-branch movement, or unanswered PR feedback. Standing down is reported with the condition, the step, and what would clear it.