What problem does it solve? Releasing a new SDK or bumping an SDK version touches many disconnected places: source code, version files, website badges, documentation pages, changelogs, i18n translations, and CI workflows. Missing any one of them causes version drift, broken badges, or untranslated pages. This Skill provides a mandatory checklist that keeps every integration point in sync. ## Core Features & Use Cases - New SDK Onboarding Checklist: Covers source layout, canonical version files (.csproj, pyproject.toml, package.json), Astro version badge wiring, docs sections, changelog pages in three locales, and CI configuration. - Version Bump Checklist: A short path for existing SDKs covering version source updates, changelog entries, and build verification. - Validation Commands: Includes build and grep-based checks to confirm version badges and changelog entries render correctly in the built website. - Use Case: When adding a Go SDK to the Envilder project, follow the checklist to wire its version into astro.config.mjs, add i18n keys to all locale files, create its changelog page, and verify the built site renders the new badge. ## Quick Start Ask the assistant to run the SDK release checklist for the new SDK you are adding and verify every integration point is connected.
