consolidate

What it does

/cl-dev:consolidate captures what a completed change taught your team and folds it back into your project's knowledge base. Once the code is built, it reviews the work and updates the shared reference the rest of your workflow reads from, so the next spec, plan, or review starts from what you just learned instead of rediscovering it. Lessons that would otherwise live only in one person's head become part of the project's durable memory.

When to use it

Reach for /cl-dev:consolidate after the implementation is done and before you open the pull request for review. It's the knowledge step of the workflow, right after implement and before finalize:

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

Use it when:

• You've just finished building a feature or fix and the change surfaced something worth remembering: a convention you settled on, a gotcha you hit, or a pattern others will reuse.
• You want the knowledge base to reflect the work before the PR goes out, so reviewers and future work benefit from it.

How to invoke it

From within your coding agent, in the repository you're working in:

/cl-dev:consolidate

It works against the change you've just implemented in your current session, so run it while that work is still in context. If you're returning to finished work later, run set-context first to bring its state back into your session.

Once you've consolidated what the work taught, move on to finalize to assemble the pull request and open it for review.