[nertzy]

Summary

Document the conventions CHANGELOG.md already follows, in a new "Changelog format" subsection of CONTRIBUTING.md:

• ### X.Y.Z headings, newest first, with ### Unreleased at the top
• One bullet per change, written from the gem user's point of view
• Imperative verb, full sentence ending in a period, code in backticks, lines wrapped at 80 columns
• Dependency changes last: Active Record before Ruby, added support before a raised minimum
• No issue or pull request numbers
• Contributors from outside the maintainers credited by name in parentheses

Test plan

• Docs-only change; compared each rule against the 2.2.0 through 2.4.0 entries

[Copilot]

🟢 Approval recommended

The documentation is clear, internally consistent, and matches recent changelog practices.

0 open findings

What changed in this PR

Documents the project’s established changelog conventions for contributors.

Changes:

• Clarifies when changelog entries are required.
• Defines formatting, ordering, wording, and attribution rules.

File	Description
CONTRIBUTING.md	Adds changelog authoring and release-entry guidelines.

🧠 Review effort: Balanced

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.