Prepare, validate, package, or review a dygo framework release and its upgrade path. Use for versioning, tags, binaries, Studio and Core bundling, installers, archives, checksums, and release smoke checks.
Scanned 8/31/2026
Install to Claude Code
Skills Directorynpx -y skills add hapyco/dygo --skill dygo-release-engineering --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Dygo Release Engineering?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/hapyco-dygo-release-engineering)More formats (shields.io, HTML) on the badges page.
---
name: dygo-release-engineering
description: Prepare, validate, package, or review a dygo framework release and its upgrade path. Use for versioning, tags, binaries, Studio and Core bundling, installers, archives, checksums, and release smoke checks.
---
# dygo Release Engineering
Release a reproducible framework artifact from a clean, reviewed state.
## Source Contract
Read `docs/releasing.md`, `docs/installation.md`, the release scripts, and `.github/workflows/release.yml` before changing or running the release process.
## Rules
- Release from clean `main` that matches its remote.
- Use semantic version tags in the documented form.
- Keep tags annotated and make sure the commit belongs to `main`.
- Build and validate Studio, bundled Core metadata, Go binaries, installers, archives, and checksums through the repository release path.
- Keep generated-project upgrades compatible with the released framework contract.
- Verify that the installed binary reports the requested version.
- Keep binary replacement atomic and checksum verification mandatory.
- Do not use a moving source branch as a versioned installer.
- Do not claim a release exists until the tag, workflow, artifacts, and remote state prove it.
Release work is a major finalization task. Run the complete documented release checks. Do not push a tag or publish a release without explicit authorization.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Use this skill when developing or maintaining browser extension code in the `browser/` directory, including Chrome/Firefox/Edge compatibility, content scripts, background scripts, or i18n updates.
SEO optimization with keyword analysis, readability assessment, technical validation, content quality. Use for search rankings, blog posts, content audits, or encountering keyword density, readability scores, meta tags, schema markup errors.
Python backend development expertise for FastAPI, security patterns, database operations, Upstash integrations, and code quality. Use when: (1) Building REST APIs with FastAPI, (2) Implementing JWT/OAuth2 authentication, (3) Setting up SQLAlchemy/async databases, (4) Integrating Redis/Upstash caching, (5) Refactoring AI-generated Python code (deslopification), (6) Designing API patterns, or (7) Optimizing backend performance.
Drive the full internationalization journey for a project — detect the stack, recommend a library, set up the chosen library, wrap existing strings, and optionally connect a translation platform. Use when the user asks to add or configure i18n, internationalization, localization, multi-language support, or translations — including when they explicitly mention LinguiJS, Lingui, next-intl, "wrap strings", "find hardcoded text", "make my app translatable", or "set up translations". Triggers on g...
PTES-aligned adversarial security audit for backend, frontend, and mobile applications. Produces a CVSS-scored Hacker Report with verified PoCs and phased remediation.
