Turn a git diff and commit list into a PR body—without inventing uncommitted work, and with a secrets warning.

Top picks

Protocol

1. 1

   Collect the committed change (3 min).

   Paste `git log` for the branch commits and `git diff main...HEAD` (or your base). Say what you tested. If a file is only on disk, leave it out. Redact tokens, passwords, customer data, and private keys before you paste.

2. 2

   Lock “no invented uncommitted work.”

   Paste the rules first. The model may not add a test plan you did not run or a file that is not in the diff.

   Copy-paste prompt

   Copy

   Write a pull-request description from the git diff and commits I paste.
   
   Hard rules:
   - Use only files, hunks, and commit messages in my paste.
   - Do not invent uncommitted work, extra files, tests I did not run, or reviewers.
   - If you see a secret (token, password, private key, .env, connection string), stop, name the file/line pattern, and refuse to repeat the secret.
   - Do not claim “adds tests” or “backwards compatible” unless the diff shows it or I said so.
   
   Output markdown:
   ## Summary
   ## Changes (file → what changed)
   ## Test plan (only what I said I ran; else NEED FROM ME)
   ## Risks / follow-ups (only if evidenced)
   ## Secrets check
   
   Confirm the rules, then wait.

3. 3

   Paste the diff and generate the body.

   If the diff is huge, paste the commit list plus the highest-signal files first. Then send:

   Generate command

   Copy

   Here are the commits and the diff. Write the PR body. If a behavior change is not in the hunks, omit it. List NEED FROM ME for tests I did not describe. Run the secrets check.

4. 4

   Paste into the host; you still click Create.

   Copy the markdown into GitHub/GitLab/Bitbucket. Add screenshots yourself. If you need a shorter summary for a small PR, use the block below.

   Short summary

   Copy

   Rewrite ## Summary as 3 bullets, max 40 words total, using only the approved body. No new files or tests.

When not to

• Do not paste .env files, tokens, or customer payloads. Redact first.
• Do not let the model claim tests, migrations, or feature flags that are not in the diff.
• Do not treat the draft as a security review. You still read the secrets check.
• Skip this recipe if you have no commits yet—only a wish list. Commit or describe the change first.