Agent skill
dev-release
Release preparation — changelog generation, version bump, tag creation. Generic version (not project-specific). For EvoNexus releases, use custom-release instead.
Install this agent skill to your Project
npx add-skill https://github.com/EvolutionAPI/evo-nexus/tree/main/.claude/skills/dev-release
SKILL.md
Dev Release
Derived from oh-my-claudecode (MIT, Yeachan Heo). Adapted for the EvoNexus Engineering Layer.
Generic release preparation: changelog generation from git log, version bump, tag creation. For EvoNexus-specific releases, use custom-release (the existing skill that handles git-flow develop→main).
Use When
- Releasing a non-EvoNexus project (Evolution API, Evo AI, Evo Go, etc.)
- Generic semver bump on a library you're maintaining
Do Not Use When
- Releasing EvoNexus itself → use
custom-releaseinstead - Project has its own custom release process → follow that
Workflow
Phase 1 — Pre-flight
- Verify on the right branch (not
main/masterdirectly) - Verify clean working tree (no uncommitted changes)
- Verify CI is green on the target commit
- Verify tests pass locally (
dev-verify)
Phase 2 — Determine version
- Read current version from manifest (
package.json,Cargo.toml,go.mod,pyproject.toml) - Determine bump type: major / minor / patch (semver)
- Confirm with user
Phase 3 — Generate changelog
- Read commits since last tag:
git log {last-tag}..HEAD --oneline - Group by type (feat / fix / docs / etc.) if conventional commits
- Save to
CHANGELOG.mdwith new version section
Phase 4 — Bump version
- Update manifest file
- Update any version references in docs
Phase 5 — Commit and tag
git commit -m "chore(release): vX.Y.Z"git tag vX.Y.Zgit push origin vX.Y.Z(after user confirmation)
Phase 6 — Verify
@oath-verifierconfirms the release commit and tag are correct
Output
Save release notes to workspace/development/research/[C]release-{version}-{date}.md.
Pairs With
@flow-git(commits and tags)@oath-verifier(verification)@quill-writer(changelog formatting)dev-verify(pre-flight)
EvoNexus-Specific Note
EvoNexus has its own release skill (custom-release) that handles the git-flow develop→main workflow with EvoNexus-specific gates (CHANGELOG entry, version sync across files, GitHub release creation). Use custom-release for EvoNexus releases. Use dev-release only for projects in workspace/projects/ that have their own release lifecycle.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
data-create-viz
Cria visualizações de dados de qualidade profissional com Python no tema Evolution (fundo escuro, acento
cs-customer-escalation
Empacota uma escalação para Devs, Produto ou Davidson com contexto completo. Use quando um bug precisa de atenção além do suporte normal, vários clientes reportam o mesmo problema, um cliente está ameaçando cancelar, ou um problema ficou sem resolução além do SLA. / Package an escalation for engineering, product, or leadership with full context. Use when a bug needs engineering attention beyond normal support, multiple customers report the same issue, a customer is threatening to churn, or an issue has sat unresolved past its SLA.
mkt-draft-content
Draft blog posts, social media, email newsletters, landing pages, press releases, and case studies with channel-specific formatting and SEO recommendations. Use when writing any marketing content, when you need headline or subject line options, or when adapting a message for a specific platform, audience, and brand voice.
gog-tasks
Create, manage, and prioritize tasks and todo items. Convert emails to tasks, set priorities (P0-P3) and categories (Work/Personal/Errands/Admin), review daily priorities, track blocked and overdue tasks. Use when user mentions tasks, todos, action items, or wants to convert emails to tasks. Requires confirmation before creating or deleting tasks.
discord-get-messages
Retrieve messages from Discord channels via the Discord API. Use this skill when the user wants to read, search, or analyze messages from a Discord channel.
cs-customer-research
Pesquisa multi-fonte sobre pergunta ou tópico de cliente com atribuição de fontes. Use quando um cliente pergunta algo que precisa ser verificado, investigando se um bug foi reportado antes, verificando o que foi dito anteriormente a uma conta específica, ou coletando contexto antes de redigir uma resposta. / Multi-source research on a customer question or topic with source attribution. Use when a customer asks something you need to look up, investigating whether a bug has been reported before, checking what was previously told to a specific account, or gathering background before drafting a response.
Didn't find tool you were looking for?