Pin a prompt version to production from the terminal

A label such as production or staging points at one version of one prompt. Moving it never changes the version history; it only changes which version the label resolves to. Labels live on the server, so they need an account and editor access to the project.

ple tag "code review" 3 production     # label v3 (moves it if it was elsewhere)
ple tag "code review" --list           # labels and recent moves
ple tag "code review" --remove staging
ple get "code review" --label production

ple get --label prints the labelled version raw to stdout, with {{variables}} filled from --var, so it pipes into a script or an agent. The MCP server takes the same label argument on get_prompt.

Each move records who did it, when, and from which version to which. The web version list shows the badge and a label history. If production suddenly behaves differently, you can see whether the label moved before you look anywhere else.

There is no runtime SDK. For a private prompt the simplest path is to resolve the label when you build, so the deployed app holds no token:

ple get "code review" --label production > prompt.txt

Public prompts can also be read without authentication at /api/public/prompts/versions/{id}?label=production.

Templates can keep or drop text depending on a variable, with {{#if}}, {{else}} and {{#unless}}. A variable counts as set when it has a value that is not empty, false or 0. Nothing is executed, and nesting stops at five levels.

Review this diff.{{#if strict}} Flag every style nit.{{/if}}

ple get "pr review" --var strict=1 --var diff="$(git diff)"

Both ship in promptlike@0.9.0 (CLI) and promptlike-mcp@0.5.0. Free keeps up to 10 versions of each prompt and a rollback adds a new version instead of deleting the ones after it; see prompt version control. Full command reference: CLI docs. Comparing tools? PromptLikeEngineer vs PromptLayer.