Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

03-release-tag

Estrelas206

Forks15

Atualizado10 de julho de 2026 às 10:57

Cut a semver release with an annotated tag and release notes. Use when the user wants to release, tag a release, bump the version, or cut a version. Not for a plain commit, a pull request, or amending an existing tag.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

ai-driven-dev

ai-driven-dev/framework

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

Explorador de arquivos

3 arquivos

SKILL.md

readonly

name	03-release-tag
description	Cut a semver release with an annotated tag and release notes. Use when the user wants to release, tag a release, bump the version, or cut a version. Not for a plain commit, a pull request, or amending an existing tag.

Release Tag

Cuts annotated semver releases with notes derived from recent commits.

Actions

#	Action	Role	Input
01	`release-tag`	Compute version, draft notes, validate, bump, tag, push	version (optional), notes_overrides

Before running an action, read its file in actions/, not only the table or assets.

Transversal rules

Versions follow semver major.minor.patch strictly. No suffixes unless explicitly requested.
Tags are annotated (git tag -a), never lightweight.
Release notes are mandatory and follow assets/release-template.md.
Always ask the user to validate the version, notes, and impacted files before tagging.
Never --force push tags. Use --force-with-lease only when explicitly required.
The bump commit only includes version-manager files (e.g. package.json, pyproject.toml).

Assets

assets/release-template.md: Release notes template.

Mais deste repositório

mesmo repositório

02-project-memory

ai-driven-dev/framework

Initialize or refresh the project memory bank. Use when the user wants to set up or regenerate the project's memory files. Not for updating one memory file after it exists or editing a single rule directly.

2026-07-13206

00-onboard

ai-driven-dev/framework

Guide a project's journey through AIDD, from first setup to shipping a feature. Use when the user says onboard me, where do I start, or what to do next. Not for listing every installed surface.

2026-07-10206

01-bootstrap

ai-driven-dev/framework

Design and validate a new SaaS's architecture into an INSTALL.md via Q&A and stack comparison. Use when the user starts a project, chooses a stack, or picks an architecture pattern. Not for editing an existing stack or scaffolding code.

2026-07-10206

03-context-generate

ai-driven-dev/framework

Route a request to generate a context artifact (skill, rule, agent, command, or hook) to its generator when the kind is unnamed. A named kind triggers its generator directly. Not for listing existing artifacts.

2026-07-10206

04-skill-generate

ai-driven-dev/framework

Generate a router-based skill across the host AI tools a project uses. Use when the user wants to create, scaffold, or refactor a skill, or turn a workflow into one. Not for other artifacts like rules, agents, commands, hooks.

2026-07-10206

05-rule-generate

ai-driven-dev/framework

Generate a coding rule that governs editor and agent behavior across the host AI tools. Use when the user wants to write, add, or refactor a rule, convention, or coding standard. Not for other artifacts like skills, agents, or hooks.

2026-07-10206

name	03-release-tag
description	Cut a semver release with an annotated tag and release notes. Use when the user wants to release, tag a release, bump the version, or cut a version. Not for a plain commit, a pull request, or amending an existing tag.

Release Tag

Cuts annotated semver releases with notes derived from recent commits.

Actions

#	Action	Role	Input
01	`release-tag`	Compute version, draft notes, validate, bump, tag, push	version (optional), notes_overrides

Before running an action, read its file in actions/, not only the table or assets.

Transversal rules

Versions follow semver major.minor.patch strictly. No suffixes unless explicitly requested.
Tags are annotated (git tag -a), never lightweight.
Release notes are mandatory and follow assets/release-template.md.
Always ask the user to validate the version, notes, and impacted files before tagging.
Never --force push tags. Use --force-with-lease only when explicitly required.
The bump commit only includes version-manager files (e.g. package.json, pyproject.toml).

Assets

assets/release-template.md: Release notes template.