Write patch notes and store page copy players read: Patch Notes Source Check (free sample)

What you end up with

Patch notes where every line is real, nothing player-facing is missing and nothing goes up without your yes.

What you get

• The method: an {id} on every line, unclear items on a Check before posting list
• Five checks: no source, unknown source, internal work, a player change left out and placeholders
• clean: the post-ready copy with tags removed, refused while the check list is open
• Your yes at your own terminal, refused in agent sessions, and a gate that says NO-GO if the post changed
• AGENTS.md, CLAUDE.md, a Grok Bot standing order, a Hermes skill and 18 tests

Who it is for

Solo developers and small studios who let an agent draft patch notes from the repo and want every line proven before players see it.

Works with

Solid chips: the agent is named in this listing's own tools list. Dashed chip: One Python script, a template, a made-up cozy game with seven changes and agent rules for each harness. Tested on Linux.

Tools needed

Cost to run: Free. Python is free.
Time to result: About five minutes

How it works

1. Run the example

   Unpack the file and run python3 patch_trace.py check example/draft-bad.md example/changes.txt.

   Expected: Seven findings, including an invented feature and a refactor sold as faster.

2. Make your change list

   In your game repo, list every commit since your last release tag with git log --no-merges --format='%h %s' and save it as changes.txt.

   Expected: One change per line, ID first.

3. Let the agent draft

   Give it AGENTS.md. It writes draft.md from the template and checks it.

   Expected: TRACE PASS and a short check list for you.

4. Approve and post yourself

   Answer the check list, run clean, then python3 patch_trace.py approve settings.json post.md and type post.

   Expected: gate says GO until post.md changes.

Sample prompts, free to use

Follow AGENTS.md. Make changes.txt from git since the last release tag, write draft.md with an {id} on every line, put anything unclear under Check before posting, and run patch_trace.py check until it passes.
Show me the draft and the check list, then stop. Never approve, post or schedule anything.

Free preview of the file

# Patch Notes Source Check

**Players forgive a short patch note. They do not forgive one that lists a fix that is not in the build. This free sample makes every line point at a real change, catches what was invented or left out, and holds the post until you say yes.**

Version 1.0, 2026-11-04. By PaperChaseWebb Inc. Free sample of Write patch notes and store page copy players read ($14). Works with Grok Bot, Claude Code, Codex and Hermes, or by hand. Python 3.8 or newer, no installs.

## What you get out of it

- Patch notes where each line under New, Changes, Fixes and Known issues carries the {id} of the commit or task it came from.
- Five checks before anyone reads it: a line with no source, a source that is not in the change list, internal work (refactors, CI, tests) dressed up as a player change, a player-facing change left out, and [placeholders] still in the text.
- A Check before posting list for anything the agent could not describe. The clean copy will not be written until you answer it.
- A post-ready file with the tags removed, and your yes recorded against it as it reads. Edit one line and the gate says NO-GO.

## Who it is for

Solo developers and small studios who let an agent draft update notes from the repo and want proof that every line is real before players see it.

## Set up (5 minutes)

1. Copy `extract_from_pack.py` from the appendix by hand, then run `python3 extract_from_pack.py patch-notes-source-check-free-sample.md notes/` to unpack the rest.
2. I

Worth knowing

• The sample checks that every line points at a real change. Section order, line length, hype words, store, Discord and hotfix checks, and the 16 prompts are in the full pack.
• On 2026-11-04: 18 tests passed on Python 3.8, 3.9, 3.11, 3.12 and 3.13 on Linux, run from the files unpacked out of the sample. Agent rules guide; they were not loaded inside each harness for this release. Not affiliated with Steam, itch.io or Discord.

Details

Version 1.0 · Updated Nov 4, 2026 · Markdown version of this page
License: Personal and commercial use. Download terms

Related

Prompt pack$14

Write patch notes and store page copy players actually read

by PaperChaseWebb

16 prompts that turn your commit log or task board into patch notes, a Steam or itch.io store page and devlog posts in your own voice, with every line tagged to the change it came from and a read-only checker that flags missing, invented-from-nothing and internal items before you post.

Works withClaude CodeCodexClaudeGrok Bot+3Plain .md and one Python 3 file (standard library only). The agent version in section 16 is written for any agent that can run commands in your game folder; it was not run inside each tool.

Games · Beginner · 10 min setup

Agent use case pack$19

Launch an AI-built browser game: mobile, licensing, leaderboards and the itch.io page

by PaperChaseWebb

A launch plan for a browser game built with an AI agent, with a read-only checker for the game folder, an input and audio script, leaderboard rules with a cheat probe, an asset license ledger and the itch.io page.

Works withClaude CodeCodexGrok BotHermes+1Plain .md with Python and Node files. The agent version in section 9 is written for any agent that can read files and run commands in a folder; it was not run inside each tool

Games · Intermediate · 30 min setup

Bot template$29

Discord game night bot: schedule sessions, run polls, post patch notes

by PaperChaseWebb

A Python Discord bot that schedules game nights with time zone aware RSVPs, runs map and mode polls and posts Steam or RSS patch notes, with an offline test you run before adding a token.

Works withClaude CodeCodexGrok BotHermesRuns on your own accounts. The agent version in section 6 is written for any agent that can run commands in a folder; it was not run inside each tool

Games · Intermediate · 30 min setup