pure-dev

Plugin pure-dev from marketplace legend-engine in finos/legend-engine. Commands read from the repo's manifest — today.

Skills (15)

• pure-backend-start

  Starts (or confirms) the standalone legend-engine backend - engine Server + H2 + local metadata server on fixed ports 9095/9092 - so a Pure LSP started with -Dlegend.test.* routes execute()/go() through real plan-generation instead of the interpreted engine. Starts only the backend, not the LSP. Use

• pure-chain-update

  Procedure for git-syncing and rebuilding a local legend-pure + legend-engine checkout, in dependency order, with pinned dependency versions resynced. Run by hand, one project at a time, fixing problems as they surface. Use for 'update my project chain', 'pull latest and rebuild <project>', 'sync leg

• pure-code-style

  Reformats a .pure file (or a block of Pure code) to a consistent house style: 2-space indentation with no column-aligned hanging indents, tight colons in type annotations, spaced pipes on if/match/lambda branches, one-parameter-per-line for long function signatures, and no stray blank lines or trail

• pure-lsp-check

  Compiles/checks a single .pure file against the already-running Legend Pure LSP bridge and reports diagnostics (errors/warnings) in under a second, as a fast alternative to a full `mvn test`/`mvn compile` cycle while iterating on Pure source in legend-pure. Use whenever the user is editing .pure fil

• pure-lsp-classpath

  Computes and caches the engine-scale Pure classpath (via Maven dependency:build-classpath) for any pure-bearing project registered in config/projects.json - legend-pure, legend-engine, or a project you've layered on top via PURE_DEV_EXTRA_PROJECTS_JSON - and resolves that project's dependency-ordere

• pure-lsp-connect

  Attaches the pure-lsp HTTP bridge to an LSP daemon that is ALREADY running (e.g. started from IntelliJ, or left over from a prior session) - never spawns a new daemon JVM. Defaults to socket port 9100. Use for 'connect to the existing/already-running LSP', 'attach the bridge to the LSP on port X', o

• pure-lsp-execute-parallel

  Runs 2 to 30 Pure functions or tests concurrently on the warm LSP daemon via `pure-lsp execute-parallel`, or every test in a package or .pure file with --package/--source. Use whenever more than one function or test is to be run, including several tests on one PCT adapter, and never a shell loop of

• pure-lsp-execute

  Runs exactly ONE existing Pure function by path (signature, mangled id or bare path) through the running Legend Pure LSP bridge, without a go() wrapper, and returns its typed value in returnValue. Also runs every test in a package or .pure file serially with --package/--source. For 2 or more functio

• pure-lsp-go

  Executes Pure code through the running Legend Pure LSP bridge as a fast REPL-style dev loop — compiles everything currently loaded and runs a function literally named go():Any[*], instead of writing a full PCT/JUnit test just to try something out. Returns BOTH the function's return value (typed, in

• pure-lsp-launch-engine

  Launches the Pure LSP bridge scoped to legend-engine with defaults baked in - the go-to entrypoint for 'just start the LSP for legend-engine'. Brings the backend engine Server up by default so execute()/go() use real plan-generation; --no-backend opts out. Use when the user wants to start/launch/boo

• pure-lsp-set-option

  Sets or unsets a Pure runtime option (the flags behind isOptionSet('...')) live in the running LSP, no restart. Covers ForceInterpreted, ExecPlan, PlanLocal, FullInteractiveExec, ExecDebug and ShowLocalPlan, and is the single source of truth for what each does and which combination to set for interp

• pure-lsp-sql-e2e

  Runs cases from the legend-engine SQL e2e parity corpus (TestPostgresParity, ~2300 SQL cases compared against a real Postgres) through the warm interpreted Pure LSP with `pure-sql-e2e`, so edits to fromPure.pure and other SQL-translation Pure sources are testable in seconds instead of a 15-25 min Ma

• pure-lsp-status

  Checks whether the Legend Pure LSP dev-loop bridge is running and its current state — initializing/ready/failed, live compiler progress text, symbol/repository counts. Use whenever the user asks if the Pure LSP or pure-lsp bridge is up/running/ready, what it's currently doing, why it seems stuck, or

• pure-lsp-sync-hook

  Explains and manages the PostToolUse hook that auto-syncs .pure file edits/creates/deletes to the running Pure LSP session's overlay, so the Agent's on-disk changes and the LSP's in-memory model stay in a matching state without manual /check or /delete calls - mirroring the file-change events a real

• trim-comments

  Reviews every comment and Javadoc added by the current branch (vs. its target/default branch) and trims them to intent-only: delete anything that narrates what the code does or rationalises why it was written, keep only the genuine surprise a reader would otherwise 'fix'. Use when asked to 'trim com

Hooks (1)

• PostToolUse

  ${CLAUDE_PLUGIN_ROOT}/hooks/pure-dev-sync-hook-launcher

Similar plugins