Skip to content

Update release-notes skill guidance and tool naming#10345

Merged
richlander merged 7 commits intomainfrom
richlander/release-notes-skill-updates
Apr 8, 2026
Merged

Update release-notes skill guidance and tool naming#10345
richlander merged 7 commits intomainfrom
richlander/release-notes-skill-updates

Conversation

@richlander
Copy link
Copy Markdown
Member

Summary

  • update the skill docs to use the current release-notes tool name where the older name still appeared
  • tighten release-notes guidance around VMR/codeflow-aware revert handling, product boundaries for tooling and editor features, scoring, and community-contributor mentions
  • include the additional tool-name updates already on the branch alongside the follow-up guidance from PR 10344

Context

This folds in the findings from the PR 10344 investigation and keeps the maintainer workflow documentation aligned with the current tooling names.

richlander and others added 7 commits April 7, 2026 21:07
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@richlander richlander merged commit baa702b into main Apr 8, 2026
8 checks passed
@richlander richlander deleted the richlander/release-notes-skill-updates branch April 8, 2026 05:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants