Skip to main content

Prompt Delivery

Manicode delivers prompt updates to your team through pull requests in a dedicated Git repository. When new or improved prompts are released, a PR appears in your prompt repository for your team to review, test, and merge on your own schedule.

How It Works​

Manicode publishes update
        |
        v
PR opened in your prompt repo
        |
        v
Your team reviews the diff
        |
        v
Merge when ready
  1. Manicode publishes an update. The release pipeline creates a branch in your prompt repository with the latest prompt files.
  2. A pull request is opened. The PR includes a diff of every prompt that changed, so your team sees exactly what is new, modified, or removed. Any older prompt PR that is still open is closed, because the new PR already includes its changes.
  3. Your team reviews. Review the changes like any other code review — read the diffs, test updated prompts against your models, and discuss with your team.
  4. Merge when ready. You control when updates go live. Merge the PR to adopt the new prompts, or close it to skip a release.

What Gets Delivered​

Each prompt update PR contains the full prompt set under prompts/:

prompts/
├── VERSION                          which release you are running
├── index.json                       every prompt's id, name, version, and last review date
└── <group>/<technology>/<version>/
    └── prompt.md                    the finished prompt for that technology version
  • Prompt files — One prompt.md per technology per version, for example prompts/python/django/5.2/prompt.md. Each file is complete on its own: a framework's prompt already includes the rules for the language and runtime it builds on, so you use one file per technology. Groups are language ecosystems (python, js, jvm, dotnet, go, php, ruby, rust, swift, dart, beam, native) plus infra, cloud, policy, spec, and shell for technologies without one host language.
  • index.json — A list of every prompt in the release. Use it to look up a prompt's path, or to check when it was last reviewed.
  • A VERSION file — Metadata recording which release you are running and where it came from.
  • A changelog — The PR description lists the prompts added, updated, and removed in this release.

A prompt's id is its path without the file name, for example python/django/5.2. Each supported version of a technology is a separate prompt, so Django 5.2 and Django 6.0 each have their own file.

Here is an index.json entry:

"python/django/5.2": {
  "uuid": "c0827183-bb14-4354-8856-76a103e16ef8",
  "name": "Django",
  "version": "5.2",
  "last_reviewed": "2026-09-29",
  "path": "python/django/5.2/prompt.md"
}

The uuid stays the same for a given prompt across releases, so you can use it to join with your own records.

Versioning​

Prompt versions use a date-based format: YYYY.MM.DD-HHMM (e.g., 2026.10.07-1430). This makes it straightforward to compare versions and determine when a release was created.

The VERSION file included in every release contains:

version: 2026.10.07-1430
source_sha: 0559d73b9d821f8abc9da967623fe7cf2ec2eafc
context_sha: aab803f1d43c5090e86fa7cef452b6683531e04b
aegis_commit: 71093f23bfbee22378fb69c39d8c1b8473bc1216
released_at: 2026-10-07T14:30:00Z
FieldDescription
versionDate-based version identifier
source_sha, context_sha, aegis_commitThe Manicode source commits that produced this release. Include them when you report an issue with a prompt.
released_atUTC timestamp of when the release was created

Update Frequency​

Prompt updates are released as improvements are ready. There is no fixed cadence. Your team controls adoption timing through the PR merge workflow.

Next Steps​