Plugin
The cl-dev plugin, an agentic set of skills you run from your coding agent, one page per skill.
CodeLantern has two halves: the platform (your account, integrations, and
access) and the cl-dev plugin, the agentic side you run from inside your coding
agent. The plugin is a set of skills, each a slash command you invoke as
/cl-dev:<name>. For example, /cl-dev:spec starts a new spec, and
/cl-dev:implement builds a planned feature. Install it
once, then run the skills as you work.
This section has a page for every skill. Each page covers the same three things:
- What it does: the outcome you get.
- When to use it: the moment in your work where it fits.
- How to invoke it: the exact command to run.
New to CodeLantern?
The Core Concepts section explains the workflow, the knowledge base, and how it all fits together.
How these pages are ordered
The pages follow the CodeLantern workflow, from spec at the
start through review-code at the end. That's the same order you'll run them on a
typical piece of work. The utility skills that support that workflow (like grill,
handoff, and the knowledge-base skills) come after.
You don't have to run them in that order, and you won't always run every one. Smaller changes can skip straight from claiming an issue to planning it; larger or riskier work benefits from the design and review steps in between. Each skill's page tells you when it's worth reaching for.
The toolbox, grouped by phase
The 22 skills fall into four groups.
Plan
spec: Interview a request into a clear issue with acceptance criteria that describe the outcome rather than the implementation.claim-issue: Set up the work surface: branch, placeholder plan, draft PR.design-solution: For bigger or vaguer work, converge on the approach before you plan it.create-impl-plan: Turn the settled design into the phased plan the agent executes.approve-plan: The gate where you sign off before any code is written.reduce-complexity: Simplify a design or plan before you build.review-design: Pressure-test the approach for gaps and risk.grill: Hard questions on the plan before it's locked.
Build
implement: Execute the plan phase by phase: tests first, quality gates, a commit per checkpoint.consolidate: Distill what the work taught into the knowledge base.finalize: Assemble the PR by authoring the summary, building the body, and marking it ready.review-code: Systematic review of the diff before it merges: correctness, security, tests, criteria.
Inform
discover: Scan the codebase to map conventions, components, and project facts.extract: The agent interviews you for the decisions and know-how behind the code.define: Sharpen a term into the glossary, one word at a time.adr: Record a decision that's hard to reverse, surprising, or a real trade-off.
Setup & helpers
init: Onboard a repo with config, knowledge-base scaffold, labels, and workflows (once, at the start).set-context: Resume a work item; pulls branch, plan, and artifacts back into context.size: Score an issue's complexity, XS–XL, on the board.backlog: Triage and prioritize what's open.handoff: Hand a skill to the cloud agent from an issue or PR comment.doctor: Health-check your CodeLantern setup.