Version-control system prompts, model configs, and output schemas. Track changes, run terminal evals, and catch regressions before production. 100% offline via CLI or synced to the cloud.
open source • local sqlite • zero key custody
Manage, version, diff, and evaluate atomic prompt bundles.
| Prompt Name | Description | Version | Test Suite | Visibility | Actions |
|---|---|---|---|---|---|
| security-audit-v2 | Automated vulnerability scanning and CWE classification for Node & Python apps. | v3 | 12/12 (100%) | Private | Open StudioEdit BundleView DiffRun Evals |
| customer-support-agent | Tone-calibrated customer response generator with strict refund guardrails. | v5 | 23/24 (96%) | Public | Open StudioEdit BundleView DiffRun Evals |
| code-reviewer-pro | Strict TypeScript and Rust code review agent with security audit rules. | v4 | 18/18 (100%) | Private | Open StudioEdit BundleView DiffRun Evals |
Hardcoded strings cause silent regressions, broken output schemas, and zero rollback history. Git for Prompts gives AI teams commit logs, visual diffs, and regression test suites.
Prompt edits pushed straight to code without isolated evals, schema checks, or rollback points.
Immutable snapshots bundling your prompt template, model config, and structured output schema in local SQLite.
From initial draft to automated evals and team sync.
Initialize a local SQLite repository directly inside your project folder.
Run local evaluations with your environment API keys against real test cases.
Sync approved versions to the team dashboard or deploy over the REST API.
Run test cases against dual AI models (Groq & OpenRouter). Validate variable interpolations and strict Zod JSON output schemas.
Input: SQL Injection payload • Score: 100%
Zod validation: Object schema verified
Interpolated "{{codeSnippet}}" successfully
Version control prompt templates, model parameters, and structured outputs without cloud lock-in.
Every save creates a new immutable version with full audit history. Roll back instantly or diff changes side-by-side.
The CLI runs completely offline in your terminal using local SQLite. Zero external servers required.
Keep system prompts, templates, model parameters, tools, and structured response schemas versioned together.
Push prompt versions to the web dashboard and serve them to your apps using SHA-256 hashed API keys.
Run evaluations, inspect diffs, and push approved prompt versions directly from your terminal. Pure TypeScript shared between the CLI and web dashboard.
Explore CLI Docs →$ gitforprompts diff prompt-v1 prompt-v2
--- prompt-v1 (2026-08-06)
+++ prompt-v2 (2026-08-07)
- systemPrompt: "You are a helper."
+ systemPrompt: "You are a strict code reviewer."
+ tools: ["run_static_analysis", "lint_check"]
“Treat prompts like production code: version them, diff them, and test them in your terminal before they hit production.”
Prompts govern production application behavior, but teams still manage them as raw strings scattered across codebases. Git for Prompts brings the discipline of code versioning to AI prompts: immutable commits, visual diffs, automated regression tests, and zero-lockin local storage.
Developers should never be blocked by network connectivity or cloud outages. The CLI operates on a local SQLite database directly inside your project (.gitforprompts/). Create prompts, commit snapshots, and run evals completely offline.
When syncing prompt versions across teams, cloud mutations use database transaction locks to guarantee version numbers never collide or overwrite existing history.
Your LLM API keys belong to you. Local evaluations run using your workstation environment variables. Cloud API credentials are stored solely as non-reversible SHA-256 hashes for authenticated delivery.
Engineered for human developers and autonomous coding agents. Features full support for the Model Context Protocol (MCP), structured schemas, and standard llms.txt endpoints.
Built in public. We welcome contributions from developers, researchers, and AI engineers.
Everything you need to know about Git for Prompts.
No. Local evaluations run in your terminal using your local environment variables. On the cloud platform, API credentials are stored as non-reversible SHA-256 hashes.
Run `$ npx gitforprompts init` inside any repository. Immutable history, offline SQLite, zero setup.
Get Started Free →