lpm-cli

Solid

Operate lpm-managed projects through the `lpm` CLI: start or stop projects and services, inspect logs and agent status, wait for readiness, run actions, and duplicate projects into standalone copies or create linked Git worktrees. Use when the user asks to operate or inspect lpm runtime state. `LPM_PROJECT_NAME` selects the default project after the skill triggers; it is not a trigger by itself. For editing YAML configuration, use `lpm-config`.

Code & Development 191 stars 13 forks Updated today MIT

Install

View on GitHub

Quality Score: 91/100

Stars 20%
76
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

`lpm` is a command-line companion to the lpm desktop app. Verify it is available with `lpm --version`; if it is missing, install it from the lpm app's Settings. ### Key facts - The project name is inferred from `LPM_PROJECT_NAME` or the current directory — omit it inside lpm terminals. - Default output is compact text (cheapest); add `--json` only when you need to parse the result. - Exit codes: `0` ok, `2` usage / not found / app not running, `1` failure / timeout. - `config get`, `config apply`, and control commands need the lpm app running; other inspection commands do not. ### Commands - `lpm list` — all projects, running state, agent counts. - `lpm project [name] [--full]` — one project in full (`--full` adds env maps, action details, terminal history). - `lpm config resolve [--cwd PATH] [--json]` — match a directory to its deepest project root without using `LPM_PROJECT_NAME`. - `lpm config validate <file> [--json]` — validate syntax, fields, layer rules, and effective merged configuration. - `lpm config get --layer project|repo|global|template [--project NAME | --template NAME] [--create] [--json]` — read a config layer with the revision required for a safe write. - `lpm config apply --layer project|repo|global|template [--project NAME | --template NAME] [--create] --if-revision HASH (--stdin | --file PATH) [--json]` — validate a candidate and atomically apply it through the running app. Never edit a live config file directly. - `lpm logs [service] [-n 30] [-p proj...

Details

Author
gug007
Repository
gug007/lpm
Created
3 months ago
Last Updated
today
Language
TypeScript
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Data & Documents Solid

lpm-config

Create and edit lpm YAML configs for projects, duplicates, worktree metadata, services, actions, terminals, profiles, SSH projects, and shared config layers. Use when the user explicitly asks to configure lpm, add an lpm service/action/button/terminal, edit `.lpm.yml`, or manage lpm templates or global config. For creating or removing linked Git worktrees and operating running projects, use `lpm-cli`.

191 Updated today
gug007
Code & Development Solid

lpm

Shortcut that loads the two lpm skills — `lpm-cli` (control projects: start/stop services, logs, agent status, duplicate into standalone copies or create Git worktrees) and `lpm-config` (create/edit project YAML configs). Use when the user types /lpm or asks about lpm without a clearly scoped task; when the task clearly fits one skill, invoke `lpm-cli` or `lpm-config` directly instead.

191 Updated today
gug007
Code & Development Solid

lpm-memory

Shared project memory for AI coding agents: save or recall work-session logs in `~/.lpm/memory/<project>/<session>.md` so another agent CLI (Claude Code, Codex, Gemini) or a future session can continue the work by session name. Invoke with a session id (e.g. `/lpm-memory auth-refactor`) to continue that session. Use when the user asks to remember or save the session or progress, hand off work, record what was done, or recall/continue/resume/join a named work session. This is per-project memory shared between agent CLIs — distinct from any CLI's own built-in memory.

191 Updated today
gug007