We split this AGENTS.md into the rules it gives an agent

6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.

• ≈0

  Common · estimate

  Many files like this have a rule of this kind.

• ≈3

  Distinctive · estimate

  This author's own choices. Worth a look.

• 3

  Very specific

  Tied to their project's names, files or tools. Probably skip.

• Common
• Distinctive
• Very specific

1. Very specific:

   Every PR or code update that changes dynos-work must include a tiny version bump and a changelog entry.

   line 7
2. Very specific:

   Use patch-style nightly increments for ordinary updates: 7.5.1 -> 7.5.2 -> 7.5.3, and so on.

   line 10
3. Distinctive:

   Update every plugin/package version field together:

   line 11
4. Very specific:

   Add a matching entry to CHANGELOG.md for the new version before opening the PR.

   line 16
5. Distinctive:

   Keep the changelog entry small but concrete: summarize the behavior change, fix, or maintenance work that justifies the version bump.

   line 17
6. Distinctive:

   Do not open or prepare a PR with code changes while leaving the version and changelog unchanged.

   line 19

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.