Menu
Reflect code changes back into the lens files.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Append a new lens to lens.yml and generate its initial content.
Make the codebase match the lenses via Claude Code plan mode.
Show the current Lens status for this directory.
Sync Lens artifacts in the current directory.
Initialize a Lens setup in the current directory. With no description argument, surveys the repo (like Claude's /init) to propose a template and draft the intent; with a description argument, passes through to the CLI verbatim.
Advance refs/lens/synced or refs/lens/applied to HEAD.
| name | pull |
| description | Reflect code changes back into the lens files. |
| allowed-tools | Bash(lens:*) |
Before running the CLI, verify:
lens binary is on PATH. If command -v lens returns non-zero, tell the user: "lens CLI not found. Install with npm i -g lens-engine."lens.yml exists (use Bash tool to test -f lens.yml). If not, tell the user: "No lens.yml found. Run /lens:init first."Then run (passing arguments through verbatim):
lens pull $ARGUMENTS
lens pull invokes the configured runner (an LLM session) and can take a minute or more on larger repos. Stream the CLI's stdout/stderr to the user. If it exits non-zero, surface the error clearly.