What happens
When the user skips the custom title prompt, the skill builds a tag annotation that starts directly with a category header (e.g. Features). GoReleaser reads the first non-empty line of an annotation as .TagSubject, so the release title becomes v0.9.0: Features - Docs sidebar search filter with fuzzy matching and UX polish instead of v0.9.0.
What should happen
With no custom title, the release title should be just the tag (e.g. v0.9.0).
Context
The skill's step 6 currently instructs: "If no custom title, omit the subject line — start the annotation body directly with the highlights." This is incorrect — GoReleaser treats the first non-empty line as .TagSubject regardless. The annotation must start with a blank line to produce an empty .TagSubject.
Follows on from #520, which added the ne .TagSubject .Tag guard but left the skill instruction incomplete.
What happens
When the user skips the custom title prompt, the skill builds a tag annotation that starts directly with a category header (e.g.
Features). GoReleaser reads the first non-empty line of an annotation as.TagSubject, so the release title becomesv0.9.0: Features - Docs sidebar search filter with fuzzy matching and UX polishinstead ofv0.9.0.What should happen
With no custom title, the release title should be just the tag (e.g.
v0.9.0).Context
The skill's step 6 currently instructs: "If no custom title, omit the subject line — start the annotation body directly with the highlights." This is incorrect — GoReleaser treats the first non-empty line as
.TagSubjectregardless. The annotation must start with a blank line to produce an empty.TagSubject.Follows on from #520, which added the
ne .TagSubject .Tagguard but left the skill instruction incomplete.