release-version

Estrellas203

Forks12

Actualizado18 de junio de 2026 a las 00:14

Use when releasing a new version (v1.x or v2.x) of Patternflow. Triggers on requests like "release v1.1", "tag a new version", "publish a release".

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

engmung

engmung/Patternflow

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-version
description	Use when releasing a new version (v1.x or v2.x) of Patternflow. Triggers on requests like "release v1.1", "tag a new version", "publish a release".

Release Version Skill

Follow these steps to finalize and tag a new release:

Verify all changes since the last tag are committed and pushed.
Update CHANGELOG.md:
- Add a new version entry at the top.
- Follow the "Keep a Changelog" format.
- Use sections: Added, Changed, Fixed, Known Issues.
Reference closed GitHub issues, if any.
Bump version references across the repository:
- README.md (if a specific v-string is mentioned).
- BUILD_GUIDE.md (if the version is mentioned in the header or text).
- firmware/patternflow/ directory name (ONLY if the update introduces major, hardware-incompatible changes).
Commit the changes with the message: release: v1.x.0 (replace x with target version).
Tag the release: git tag -a v1.x.0 -m "Release v1.x.0".
Push tags: git push --tags.
Remind the user to create a GitHub Release from the tag manually in their browser.

Más de este repositorio

mismo repositorio

update-bom

engmung/Patternflow

Use when the BOM in BUILD_GUIDE.md needs to be checked against or synchronized with the schematic in hardware/pcb/schematic.pdf or the KiCad source in hardware/pcb/kicad/. Trigger when adding, removing, or changing electronic components, or when the user asks to verify BOM correctness.

2026-06-18203

add-pattern

engmung/Patternflow

Use when adding a new generative pattern to the Patternflow firmware. Triggers on requests like "add a new pattern", "create a [name] pattern", or when the user describes a visual effect they want on the LED matrix.

2026-05-10203

firmware-cleanup

engmung/Patternflow

Use when preparing firmware code for public release or pull request. Triggers on requests like "clean up the firmware", "prepare this code for release", or when reviewing firmware before commit.

2026-05-10203

name	release-version
description	Use when releasing a new version (v1.x or v2.x) of Patternflow. Triggers on requests like "release v1.1", "tag a new version", "publish a release".

Release Version Skill

Follow these steps to finalize and tag a new release:

Verify all changes since the last tag are committed and pushed.
Update CHANGELOG.md:
- Add a new version entry at the top.
- Follow the "Keep a Changelog" format.
- Use sections: Added, Changed, Fixed, Known Issues.
Reference closed GitHub issues, if any.
Bump version references across the repository:
- README.md (if a specific v-string is mentioned).
- BUILD_GUIDE.md (if the version is mentioned in the header or text).
- firmware/patternflow/ directory name (ONLY if the update introduces major, hardware-incompatible changes).
Commit the changes with the message: release: v1.x.0 (replace x with target version).
Tag the release: git tag -a v1.x.0 -m "Release v1.x.0".
Push tags: git push --tags.
Remind the user to create a GitHub Release from the tag manually in their browser.