Summary

Remove PR/issue references from the release notes skill template to create cleaner, more user-focused release notes.

Context

Release notes are meant to communicate value to end users, not serve as a changelog for developers. Including PR numbers and GitHub links (#123, [PR link]) adds noise and shifts focus from the user experience to development tracking.

This update aligns the release notes skill with best practices for user-facing documentation by removing all PR/issue reference patterns from the template and adding explicit guidance against including them.

Changes

• Removed ([#NNN](url)) pattern from highlights section template
• Updated bug fixes section guidance to remove "PR link" reference
• Added explicit guideline: "No PR/issue references - do not include PR numbers, issue numbers, or links to GitHub PRs/issues in the release notes"

Use Cases

When using the write-release-notes skill, the generated release notes will now:

• Focus purely on user value and impact
• Avoid GitHub-specific tracking identifiers
• Be cleaner and more readable for end users
• Match industry best practices for public-facing release notes

Testing

# Verify the skill template has been updated
cat .forge/skills/write-release-notes/SKILL.md | grep -A 5 "No PR/issue"

# Test the skill by generating release notes
forge skill write-release-notes
# Verify generated notes do not contain PR/issue references

Links

• Related skill: .forge/skills/write-release-notes/SKILL.md