Reviewing Prompt PRs

When Manicode publishes a prompt update, a pull request is created in your prompt repository. This page explains how to review and merge these PRs.

Anatomy of a Prompt PR

Each prompt update PR follows a consistent structure:

• Title: Update prompts to YYYY.MM.DD-HHMM — the version being delivered
• Branch: prompts/YYYY.MM.DD-HHMM — a dedicated branch for this release
• Description: The release version and source commits, followed by the prompts added, updated, and removed, listed by id (for example python/django/5.2)
• Changed files: Updated prompt.md files, index.json, and the VERSION metadata file

When a new PR opens, any older prompt PR that is still open is closed with a link to the new one. Each PR carries the full prompt set, so you only ever need to review the latest one.

Moving to the Prompts 2.0 Layout

If your repository still has the older layout (folders such as code security prompts/), your next PR moves it to the current one. That PR removes every old file and adds one prompt.md per technology version under prompts/<group>/<technology>/<version>/. Its description starts with a note saying so.

Before you merge it:

1. Find every place that points at an old prompt path: IDE config files (.github/copilot-instructions.md, CLAUDE.md, .cursor/rules/), CI steps, and scripts.
2. Look up the replacement in prompts/index.json. Search by technology name, then pick the version that matches what your team runs. For example, a Django 5.2 project uses prompts/python/django/5.2/prompt.md.
3. Update those references in the same change you merge, or right after, so nothing reads a path that no longer exists.

The version-specific prompts already include the rules for the language and runtime each framework builds on, so a Django project needs only the Django prompt, not a separate Python one.

Review Workflow

1. Read the Diff

Start with the PR description, which lists every prompt that changed. Then read the diff:

• Added prompts — New technologies, or new versions of technologies already covered
• Updated prompts — Changes to existing prompt content (security rules, coding patterns, version-specific guidance)
• Removed prompts — Prompts for versions or technologies that are no longer supported

2. Assess Relevance

Focus on the prompts for the technology versions your team uses. If your team runs Django 5.2 and React 19, review python/django/5.2 and js/react/19 closely. Changes to technologies or versions you do not use can be reviewed with less scrutiny.

3. Test Against Your Models

Before merging, check out the PR branch and test updated prompts with your LLM setup:

# Fetch and check out the PR branch
git fetch origin
git checkout prompts/2026.10.07-1430

# Test a prompt with your preferred model
cat prompts/python/django/5.2/prompt.md
# Copy and paste into your LLM interface, or use via API

Test with your standard verification prompts:

• Ask the LLM to generate code with known security implications (login, file upload, database query)
• Verify security controls are present in the output
• Compare with output from your current prompt version

4. Merge or Skip

• Merge the PR to adopt the new prompts. Your main branch will reflect the latest release.
• Close without merging if you want to skip this release. Future releases will include the skipped changes plus any new updates.

Review Criteria

When reviewing prompt changes, check for:

Criterion	What to Look For
Security rules	Are new security rules appropriate for your application?
Version match	Are you using the prompt for the exact version you run (e.g., Rails 7.2 vs. Rails 8.0)? Each version has its own file.
Model compatibility	If you pin a specific model version, test that the prompt works with your pinned model
Removed content	If security rules or prompts were removed, understand why before merging
Scope changes	If a prompt's scope expanded (e.g., added new vulnerability categories), verify the additions are accurate

Tips

• You do not need to merge every release. If a release only touches prompts for technologies you do not use, it is fine to skip it.
• PRs accumulate. If you skip several releases and then merge a later one, you get all the changes at once since the PR always contains the full prompt set.
• Use GitHub's file filter to narrow the diff to the groups or technologies you use, for example prompts/python/.
• Automate testing by adding a CI step that runs your standard verification prompts against the PR branch before merging. See Integration: GitHub Actions for examples.