finalize

Build

What it does

/cl-dev:finalize gets a pull request ready for review. It authors the summary of the work, assembles the PR body, and flips the pull request out of draft so reviewers can pick it up. When it finishes, you have a clean, review-ready PR with a description that reflects what actually changed. Its knowledge base section links to captured updates and lists suggestions that were surfaced but not captured, with the recorded outcome or reason where available.

When to use it

Reach for it once the change is built and you've captured what it taught your knowledge base. This is the step that turns a draft PR into one that's ready for a reviewer:

… implement → consolidate → finalize → review-code → merge

Run it after /cl-dev:consolidate, when the implementation is complete and you want to open the PR for review. It's the handoff point between building the change and reviewing it: once finalize has marked the PR ready, the next step is /cl-dev:review-code on the diff.

How to invoke it

In your coding agent, in the repository you're working in, run:

/cl-dev:finalize

It works against the pull request tied to your current work, so make sure the change is implemented and consolidated first. finalize describes and submits what's already there; it doesn't write new code. If you're returning to work in progress, run /cl-dev:set-context first to bring the current state back into your session.