// Write Lodestar release notes and Discord announcements for new versions. Use when cutting a new release, drafting announcement text, or updating the GitHub release body. Covers header text, Discord announcement, and changelog formatting. Requires access to the Lodestar repo and GitHub CLI for changelog generation.
| name | release-notes |
| description | Write Lodestar release notes and Discord announcements for new versions. Use when cutting a new release, drafting announcement text, or updating the GitHub release body. Covers header text, Discord announcement, and changelog formatting. Requires access to the Lodestar repo and GitHub CLI for changelog generation. |
| disable-model-invocation | true |
Write release notes for Lodestar versions by analyzing the changelog, identifying operator-facing changes, and producing both GitHub release header text and a Discord announcement.
references/style-guide.md for tone, structure, and past examplesreferences/changelog-analysis.md for how to categorize and prioritize changes# Get commits between last stable and new version
git log <prev-tag>..<new-tag> --oneline --no-merges
# Or use the auto-generated changelog from the RC
gh release view <new-tag> --json body -q '.body'
Read references/changelog-analysis.md for the prioritization framework.
Focus on what matters to node operators, not internal refactors.
The header text goes at the top of the GitHub release body, before the # Changelog section.
Follow the structure in references/style-guide.md.
Shorter version of the header text for the #lodestar-announcements channel.
See references/style-guide.md for Discord-specific formatting rules.
Produce a single markdown file with two sections:
## GitHub Release Header — full header text## Discord Announcement — shorter announcement(#XXXX)If any commands, file paths, URLs, or configurations in this skill are outdated or no longer work, update this SKILL.md with the correct information after completing your current task. Skills should stay accurate and self-healing — fix what you find broken.
Run Ethereum multi-client devnets using Kurtosis and the ethpandaops/ethereum-package. Use for spinning up local testnets, validating cross-client interop, testing fork transitions, running assertoor checks, debugging CL/EL client interactions, or verifying new feature implementations across multiple consensus and execution clients.
Debug Lodestar beacon node issues by running a local mainnet node with checkpoint sync and engineMock. Use for investigating networking bugs, peer discovery issues, identify failures, metrics anomalies, or any behavior that needs real-world peer interactions without a full execution client.