Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

Comenzar

release

Estrellas48

Forks7

Actualizado14 de julio de 2026 a las 19:32

Release a new version of the project.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

mochow13

mochow13/keen-code

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

SKILL.md

readonly

name	release
description	Release a new version of the project.

Release Skill

Target version (required): $ARGUMENTS

Steps

Bump versions. Update the version string in both files to the target version:
- cmd/main.go
- npm/package.json
Update CHANGELOG.md.
- Move all entries under [Unreleased] into a new [X.Y.Z] - YYYY-MM-DD section below it.
- Add a new empty [Unreleased] section at the top.
- Check the commit history for any changes that should be included in the release and were missing in the [Unreleased] section.
- Update the comparison links at the bottom of the file.
Run the tests.
```
go test -race ./...
```
Verify the npm wrapper.
```
cd npm && npm pack --dry-run
```
Commit the version bump. Stage only the four changed files and commit:
- cmd/main.go
- npm/package.json
- CHANGELOG.md
Create and push the tag.
```
git tag vX.Y.Z && git push origin main && git push origin vX.Y.Z
```
The tag must match npm/package.json version exactly (e.g. v1.2.3).
Watch the pipelines. Pushing the tag triggers the build and release workflows. Watch them to completion:
```
gh run watch $(gh run list --limit 1 --json databaseId --jq '.[0].databaseId')
```
If a run fails, inspect logs with gh run view <run-id> --log-failed.
Confirm. Once both pipelines succeed, report the tag, commit SHA, and release URL (gh release view vX.Y.Z --web or --json url) to the user.

Más de este repositorio

mismo repositorio

commit

mochow13/keen-code

Inspect git status, draft a commit message that matches the repo's style, and commit staged changes.

2026-06-1848

clarify

mochow13/keen-code

Ask focused clarifying questions to resolve ambiguous requirements before planning or implementing work.

2026-05-1048

explain

mochow13/keen-code

Explain code, behavior, architecture, or diffs with concrete references to the relevant files.

2026-05-1048

fix-tests

mochow13/keen-code

Diagnose failing tests, determine whether code or tests are wrong, and make the smallest passing fix.

2026-05-1048

refactor

mochow13/keen-code

Refactor existing code while preserving behavior, keeping changes scoped, and verifying with relevant tests.

2026-05-1048

review

mochow13/keen-code

Review current code changes for bugs, regressions, test gaps, and project-guideline violations.

2026-05-1048

name	release
description	Release a new version of the project.

Release Skill

Target version (required): $ARGUMENTS

Steps

Bump versions. Update the version string in both files to the target version:
- cmd/main.go
- npm/package.json
Update CHANGELOG.md.
- Move all entries under [Unreleased] into a new [X.Y.Z] - YYYY-MM-DD section below it.
- Add a new empty [Unreleased] section at the top.
- Check the commit history for any changes that should be included in the release and were missing in the [Unreleased] section.
- Update the comparison links at the bottom of the file.
Run the tests.
```
go test -race ./...
```
Verify the npm wrapper.
```
cd npm && npm pack --dry-run
```
Commit the version bump. Stage only the four changed files and commit:
- cmd/main.go
- npm/package.json
- CHANGELOG.md
Create and push the tag.
```
git tag vX.Y.Z && git push origin main && git push origin vX.Y.Z
```
The tag must match npm/package.json version exactly (e.g. v1.2.3).
Watch the pipelines. Pushing the tag triggers the build and release workflows. Watch them to completion:
```
gh run watch $(gh run list --limit 1 --json databaseId --jq '.[0].databaseId')
```
If a run fails, inspect logs with gh run view <run-id> --log-failed.
Confirm. Once both pipelines succeed, report the tag, commit SHA, and release URL (gh release view vX.Y.Z --web or --json url) to the user.