Setup & helpers
set-context
Load the state of an in-progress work item so you can pick up where you left off.
What it does
/cl-dev:set-context loads the state of an in-progress work item into your session so you
can resume it. It pulls together the moving parts of the work (the issue, its plan, where
the branch stands, and the pull request) so your coding agent knows what you're working on
and how far along it is, without you re-explaining any of it.
When to use it
Reach for it whenever you're returning to work that's already underway and want your agent up to speed before you continue:
- Starting a fresh session on an issue you claimed earlier.
- Coming back after a break, or handing the work between machines.
- Picking up something a teammate or the cloud agent moved forward while you were away.
It's the natural first step of any resumed session, and it pairs with the build steps that
follow. For example, run it before /cl-dev:implement to bring the
current state back into play. If you're setting up a repository for the very first time,
run /cl-dev:init instead; set-context is for work that already exists.
How to invoke it
In your coding agent, run:
/cl-dev:set-contextIt loads the work item tied to the branch you're on, so check out the right branch first. If you want to point it at a specific issue instead, name that issue when you run it.
Setup & helpers
Related skills
Other skills in the same phase of the workflow.
| backlog | Review and prioritize your open issues before you commit to the next piece of work. |
| doctor | Run a health check of your CodeLantern setup and get told exactly what to fix. |
| handoff | Delegate a workflow step to the CodeLantern cloud agent to run on its own. |
| init | Initialize a repository so CodeLantern workflows can run against it. |
| size | Assess an issue's complexity on an XS–XL scale and record it on the issue. |