docs(agents): mark a PR ready after the update that finishes it, and measure every area a change touches #22

Merged
HumanBean merged 1 commit from HumanBean/Tooling:docs/ready-after-update into main 2026-11-19 06:30:07 +00:00
Owner

Why

AGENTS.md tells agents to take a PR out of WIP once it is ready, but only at the moment it first gets there. A PR often becomes ready later, through its last measurement, fix-up or test run, and then sits in WIP where nobody reviews it.

It also asks for a PR to be "measured" without saying what: PRs measure only the area they aim at, and miss the cost elsewhere (a compiler flag's build time, a cache's first-run load).

What changed

Two additions to AGENTS.md, under the pull request rules:

  • after each pr update, check again whether the PR is ready, and if it is, pr ready <n> then, rather than leaving a finished PR in WIP;
  • measured where it has an effect, every area of it: numbers from the game for a change the game runs, the build's time and size for a build change, load time and cache size for loading or caches, the program's own time, size or output for the launcher, the website or a tool; several when one change touches several, and a line saying why for an area that plainly can't be affected.

The same notes go into Longshot's docs/agent-pull-requests.md in a companion PR (Longshot #1715).

Testing

Docs only; nothing to run.

🤖 Generated with Claude Code

## Why `AGENTS.md` tells agents to take a PR out of WIP once it is ready, but only at the moment it first gets there. A PR often becomes ready later, through its last measurement, fix-up or test run, and then sits in WIP where nobody reviews it. It also asks for a PR to be "measured" without saying what: PRs measure only the area they aim at, and miss the cost elsewhere (a compiler flag's build time, a cache's first-run load). ## What changed Two additions to `AGENTS.md`, under the pull request rules: - after each `pr update`, check again whether the PR is ready, and if it is, `pr ready <n>` then, rather than leaving a finished PR in WIP; - **measured where it has an effect, every area of it**: numbers from the game for a change the game runs, the build's time and size for a build change, load time and cache size for loading or caches, the program's own time, size or output for the launcher, the website or a tool; several when one change touches several, and a line saying why for an area that plainly can't be affected. The same notes go into Longshot's `docs/agent-pull-requests.md` in a companion PR ([Longshot #1715](https://git.magicbean.dev/MagicBeanDev/Longshot/pulls/1715)). ## Testing Docs only; nothing to run. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
HumanBean force-pushed docs/ready-after-update from 54d35b4235 to d4b6bb9794 2026-11-19 06:29:02 +00:00 Compare
HumanBean changed title from docs(agents): check again whether a PR is ready after each update to docs(agents): mark a PR ready after the update that finishes it, and measure every area a change touches 2026-11-19 06:29:23 +00:00
Author
Owner

Added a second note in the same commit: measure every area a change touches (game, build time and size, loading and caches, memory, the launcher and tools), not only the one it targets.

Added a second note in the same commit: measure every area a change touches (game, build time and size, loading and caches, memory, the launcher and tools), not only the one it targets.
HumanBean deleted branch docs/ready-after-update 2026-11-19 06:30:07 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
MagicBeanDev/Tooling!22
No description provided.