Wox Update Changelog

4. Write changelog entries in repository style.

• Preserve header pattern exactly (for example: ## v2.0.1 -).
• Keep section order: Add, Improve, Fix.
• Use bullet nesting style already used in file.
• Keep wording concise, user-facing, and factual.
• Prefer plugin/module prefix when clear, e.g. [`Shell`] or [`Clipboard`].
• Keep issue references in existing style, e.g. #4339.
• Keep existing screenshots and add new image lines only when already available in repo.

5. Validate before finishing.

• Ensure no duplicate bullets.
• Ensure every bullet maps to at least one commit in range.
• Ensure markdown renders cleanly and section spacing matches nearby versions.
• Avoid rewriting old release sections unless explicitly requested.
• If a commit set only contains tiny UI-only polish, keep it out of changelog by default.

Command Reference

git tag --sort=-creatordate | head -n 20
sed -n '1,120p' CHANGELOG.md
git log --oneline --no-merges <last_tag>..HEAD
git show --stat --oneline <sha>
git diff -- CHANGELOG.md

Output Rules

• Edit CHANGELOG.md directly.
• Keep final response short: what section was updated and what categories were changed.
• If commit intent is ambiguous, state the assumption briefly in the final response.