菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| 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 |
Fetch the GitHub release notes for a given version and convert them into Textile format suitable for posting on redmine.org.
$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.
Extract the version from $ARGUMENTS. If absent, ask the user for the target version.
Run:
gh release view <version> --repo haru/redmine_ai_helper
Parse the Markdown body from the output.
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):
:tada:, Unicode emoji such as 🎉, 🐛, 📝).by @author in https://github.com/.../pull/123 or by @author in https://github.com/.*/issues/\d+. Also remove standalone by @username suffixes. by @username patterns.https://github.com/...).**Full Changelog**.Add a download section at the top:
h3. Download
https://github.com/haru/redmine_ai_helper/releases/tag/<version>
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.
h3. Download
https://github.com/haru/redmine_ai_helper/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>
#123) — they would be interpreted as redmine.org issue numbers.Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync.
Connect to the running Redmine instance and log in via the Playwright MCP browser, using REDMINE_PLAYRIGHT_URL/REDMINE_PLAYRIGHT_USER/REDMINE_PLAYRIGHT_PASSWORD environment variables. Use whenever the user asks to open, check, access, or test something in the running Redmine UI (e.g. verifying a feature in the browser, taking a screenshot of a page, manually exercising a flow).
Stage the current changes and create a git commit with a properly formatted English message. Use whenever the user asks to commit, save, or check in their work. Picks a Conventional-Commits-style prefix (fix:, feat:, refactor:, docs:, test:, chore:, style:, perf:) based on the actual diff, keeps the first line a concise summary, and adds a bullet list of details only when the change touches several things.
Execute the implementation plan by processing and executing all tasks defined in tasks.md
Execute the implementation planning workflow using the plan template to generate design artifacts.
Create or update the feature specification from a natural language feature description.