release-add

To append a merged task to release notes without duplicating entries, use an idempotent post-merge tracking workflow that validates the task ID and checks the active release entry before appending the bullet.

The best way to track multiple merges after manual commits is using a bulk catch-up mode triggered by a command like --since-last-tag, which automatically identifies and appends tasks mentioned since the last release tag.

Task title resolution for release entries works by reading the task title directly from its corresponding spec file, falling back to a placeholder only when the spec file is not found.

No, the release tracking workflow does not automatically commit changes. It safely appends the task bullet to the release file and prompts you to review and commit the modifications yourself.

To maintain the correct release format when appending new tasks, the workflow reads formatting rules from a configuration file like release-rules.md and appends the new bullet without reordering existing content.