Setup & helpers
init
Initialize a repository so CodeLantern workflows can run against it.
What it does
/cl-dev:init prepares a repository for CodeLantern workflows. It's a one-time setup you run in a repo the first time you want to use cl-dev there.
Once it finishes, the repository knows how to work with CodeLantern: which project your work lives in and the local scaffolding the skills expect. From that point on, the rest of the workflow (/cl-dev:spec, /cl-dev:claim-issue, and everything after) can run against the repo.
When to use it
Run /cl-dev:init the first time you bring CodeLantern to a repository, before any other skill. It comes before the workflow proper begins:
init → spec → claim-issue → create-impl-plan → implement → review → mergeYou only need it once per repository. If a repo is already set up (for example, a teammate ran it earlier), you don't run init again. Use /cl-dev:set-context to load the state of existing work and pick up where things left off.
How to invoke it
From your coding agent, in the root of the repository you want to set up:
/cl-dev:initBefore you run it, make sure:
- The cl-dev plugin is installed in your coding agent. If it isn't, follow Install first.
- A CodeLantern platform account is connected to the repository through the CodeLantern GitHub App, and the repository is configured for a project manager (GitHub or Linear). See Integrations and Repositories. If you don't have an account yet, contact CodeLantern to get set up.
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. |
| set-context | Load the state of an in-progress work item so you can pick up where you left off. |
| size | Assess an issue's complexity on an XS–XL scale and record it on the issue. |