release-version

Étoiles203

Forks12

Mis à jour18 juin 2026 à 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".

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

engmung

engmung/Patternflow

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·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.

Plus depuis ce dépôt

même dépôt

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.