Build
finalize
Finalize a pull request: author the summary, assemble the body, and mark it ready for review.
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.
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 → mergeRun 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:finalizeIt 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.
Build
Related skills
Other skills in the same phase of the workflow.
| consolidate | Update your knowledge base with what the finished work taught. |
| implement | Build the code from an approved plan, phase by phase, running quality checks and committing as it goes. |
| review-code | Get a systematic review of a pull request's diff before you merge. |