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
• Changed files: Updated prompt markdown files and the VERSION metadata file

Review Workflow

1. Read the Diff

The PR diff shows exactly which prompts changed. Look for:

• New prompts — Files added for frameworks or categories not previously covered
• Updated prompts — Changes to existing prompt content (security rules, coding patterns, model-specific tuning)
• Removed prompts — Prompts that have been deprecated or consolidated into other prompts

2. Assess Relevance

Focus on prompts relevant to your team's stack. If your team uses Django and React, prioritize reviewing changes to those prompts. Changes to frameworks 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.02.23-1430

# Test a prompt with your preferred model
cat "code security prompts/Backend Frameworks/Python/01 Secure Django Developer (Opus 4.6).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 the framework version you use?
Framework compatibility	Do prompt references match your framework version (e.g., Rails 7 vs. Rails 8)?
Model compatibility	If you pin a specific model version, test that the prompt works with your pinned model
Removed content	If security rules 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 frameworks 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 specific frameworks or categories during review.
• 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.