Prompts as reviewed source files

Keep prompts as versioned .prompt or YAML files that go through the same PR review as the rest of your code.

The problem

When prompts are inline literals, a change is buried in an unrelated diff and no reviewer really approves the prompt itself. Typed params drift, constraints are scattered, and the thing that actually drives the model is the least reviewed part of the change.

With promptel

A promptel prompt is a self-contained file: typed params, body, technique, and constraints in named blocks. It shows up in a PR as a legible diff a reviewer can approve, and the YAML surface makes it easy to validate against a schema in CI.

How it flows

01
file
Keep each prompt as a .prompt (or YAML) file in the repo.
02
PR
Prompt edits appear as ordinary, block-structured diffs.
03
validate
Convert to YAML and run schema validation in CI with the CLI.
04
execute
The reviewed file is what executePrompt runs — no drift from an inline copy.

What you get

✓Prompt changes get real review
✓Typed params and constraints stay explicit
✓The reviewed file is the executed file

Try it on a prompt

Run npm install promptel and follow the quickstart.