← Use cases · CI

CI-native teams that already trust lockfiles

Shops that live by uv, pnpm, or cargo lockfiles want the same guarantee for prompts — no new SaaS, no runtime dependency.

The problem

A team with disciplined dependency lockfiles still has an unlocked surface: its prompts. Evals pass against one version while production runs another, and the gap only surfaces as a quality regression no one can explain.

With blogus

blogus adds prompts.lock to the same lockfile-and-verify discipline the team already uses for dependencies. verify is offline and secret-free, so it drops straight into an existing CI step with no new infrastructure.

How it flows

01
check
Pre-commit hook flags any inline prompt that isn’t versioned yet.
02
verify
CI step recomputes hashes and fails on drift — no keys, no network.
03
lock
Prompt updates land with a refreshed lock, reviewed like a dependency bump.
04
release
The lock’s commit field ties each shipped prompt to an exact ref.

What you get

✓Prompts get the same lock guarantee as dependencies
✓Zero new services or runtime calls
✓Quality regressions from silent prompt edits caught before merge

Try it on your repo

Run uvx blogus scan today, or follow the quickstart.