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.
  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:

  • Prompt files — The full set of Manicode prompts, organized by category (Code Security, Validation, Compliance, Threat Modeling, AI Coding Requirements, Workforce)
  • A VERSION file — Metadata including the version identifier, source reference, and release timestamp
  • A changelog — Summary of what changed in this release (new prompts, updated prompts, removed prompts)

Versioning​

Prompt versions use a date-based format: YYYY.MM.DD-HHMM (e.g., 2026.02.23-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.02.23-1430
source_sha: abc123def456
released_at: 2026-02-23T14:30:00Z
FieldDescription
versionDate-based version identifier
source_shaThe source commit that produced this release
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​