create-release-notes
Generate Redmine.org release notes from a GitHub release tag. Fetches the release, strips emojis/issue numbers/author names, and outputs Textile-formatted text ready to paste into redmine.org.
- License 许可
- MIT
- 最近更新
- 2026-10-31
- Stars
- ★ 4
- Forks
- 1
01 前言 Front Matter
- name
- create-release-notes
- description
- Generate Redmine.org release notes from a GitHub release tag. Fetches the release, strips emojis/issue numbers/author names, and outputs Textile-formatted text ready to paste into redmine.org.
- argument-hint
- The release version tag, e.g. 3.3.0
- user-invocable
- true
- disable-model-invocation
- false
03 SKILL.md 正文
Create Redmine.org Release Notes
Fetch the GitHub release notes for a given version and convert them into Textile format suitable for posting on redmine.org.
User Input
$ARGUMENTS
The user input should contain the release version (e.g. 3.3.0). If no version is provided, ask the user which version to use before proceeding.
Procedure
Step 1: Determine the Version
Extract the version from $ARGUMENTS. If absent, ask the user for the target version.
Step 2: Fetch the GitHub Release Notes
Run:
gh release view <version> --repo haru/redmine_render_switcher
Parse the Markdown body from the output.
Step 3: Convert to Textile
Transform the Markdown release notes into Textile following these rules:
| Markdown | Textile |
|---|---|
## What's Changed |
h3. What's Changed |
### New Features … |
h4. New Features |
### Bug Fixes … |
h4. Bug Fixes |
### Other Changes … |
h4. Other Changes |
* item / - item |
* item |
Cleanup rules (apply in order):
- Remove emojis — strip all emoji characters (e.g.
:tada:, Unicode emoji such as 🎉, 🐛, 📝). - Remove GitHub issue/PR references — delete patterns like
by @author in https://github.com/.../pull/123orby @author in https://github.com/.*/issues/\d+. Also remove standaloneby @usernamesuffixes. - Remove author names — delete any remaining
by @usernamepatterns. - Remove hyperlinks — delete bare GitHub URLs that appear after cleanup (e.g.
https://github.com/...). - Remove the "Full Changelog" line — drop the line starting with
**Full Changelog**. - Trim trailing whitespace from each bullet.
Step 4: Prepend the Download Section
Add a download section at the top:
h3. Download
https://github.com/haru/redmine_render_switcher/releases/tag/<version>
Step 5: Output the Result
Print the complete Textile text to the user so they can copy and paste it into redmine.org. Do not write it to any file.
Expected Output Format
h3. Download
https://github.com/haru/redmine_render_switcher/releases/tag/<version>
h3. What's Changed
h4. New Features
* <feature description>
* <feature description>
h4. Bug Fixes
* <fix description>
h4. Other Changes
* <change description>
* <change description>
Notes
- Output must be Textile, not Markdown. redmine.org does not render Markdown.
- Never include emoji — redmine.org does not support them.
- Never include GitHub issue/PR numbers (
#123) — they would be interpreted as redmine.org issue numbers. - Never include author names — GitHub usernames are irrelevant on redmine.org.
- Do not write the output to any file; display it in the conversation only.
04 同仓库更多 Skills
speckit-review-types
Type design analysis — encapsulation, invariant expression, usefulness, and enforcement.
speckit-review-tests
Test coverage quality analysis — behavioral coverage, critical gap identification, test resilience evaluation.
speckit-review-simplify
Code simplification suggestions — clarity, unnecessary complexity, redundant abstractions. Advisory only.
speckit-review-run
Comprehensive code review using specialized agents — orchestrates code, comments, tests, errors, types, and simplify agents sequentially.
speckit-review-errors
Error handling review — silent failure detection, catch block analysis, error logging.
speckit-review-comments
Code comment accuracy verification, documentation completeness assessment, comment rot detection.