菜单
Release notes generator. Collects merged PRs since the latest tag, groups by type, and emits Polish and English changelog markdown. Trigger when: /release-notes, changelog, release notes, notatki wydania.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | release-notes |
| description | Release notes generator. Collects merged PRs since the latest tag, groups by type, and emits Polish and English changelog markdown. Trigger when: /release-notes, changelog, release notes, notatki wydania. |
Generate a bilingual changelog from merged PRs.
--since <tag|date>, --until <date>, --target team|investors|both.Prefer an explicit --since. Otherwise use the newest tag:
git fetch --tags origin
git tag --sort=-creatordate | head -5
git describe --tags --abbrev=0
If there are no tags, use the last merged release PR or a date confirmed by the user.
For a tag range:
BASE_TAG=vX.Y.Z
BASE_DATE=$(git log -1 --format=%cI "$BASE_TAG")
gh pr list \
--repo <OWNER>/<REPO> \
--state merged \
--search "merged:>=$BASE_DATE base:main" \
--limit 500 \
--json number,title,mergedAt,author,labels,url
Use --limit 500 for any range longer than a few days. Repos with merge queues, dependency groups, or automatic version bumps can exceed 200 merged PRs in a month. Confirm the count before writing notes:
gh pr list \
--repo <OWNER>/<REPO> \
--state merged \
--search "merged:>=$BASE_DATE base:main" \
--limit 500 \
--json number \
--jq 'length'
Also inspect commits if PR data is incomplete:
git log --oneline "$BASE_TAG"..HEAD
Use title prefixes first, then labels:
| Group | Signals |
|---|---|
| Features | feat, enhancement, user-visible additions |
| Fixes | fix, bug, regressions, production issues |
| Content | content, copy / docs changes |
| Tests and QA | test, area: tests, Playwright/Vitest/manual QA |
| Tooling | chore, ci, tooling, scripts, agent skills |
| Docs | docs, documentation-only changes |
Exclude noise:
Not included note and keep at most one bullet for the highest version reachedTeam format:
## Release notes PL
### Najważniejsze zmiany
- ...
### Funkcje
- ...
### Poprawki
- ...
### Testy i tooling
- ...
### Ryzyka i follow-up
- ...
Investor format:
## Release notes EN
### Highlights
- ...
### Product progress
- ...
### Quality and reliability
- ...
### Next risks
- ...
Not included section.Shared multi-agent presence and claim protocol. Use before any coding agent starts work in this repo, when coordinating Claude/Codex/Gemini sessions, or when checking who is already working on the repository. Triggers: agent session start, check agent presence, agent coordination, who's working on repo.
Claude Code adapter for the shared agent-presence protocol (for Codex CLI use `.agent/skills/dispatch-watcher/SKILL.md`, for Gemini CLI use `.agent/skills/dispatch-watcher-gemini/SKILL.md`). Use on Claude session start to run pre-flight, claim Slack-dispatched issues (@claude #N), and emit lifecycle events. Triggers: Claude session start, /dispatch, /agent-presence, message addressed to @claude in the dispatch channel.
Gemini CLI adapter for the shared agent-presence protocol (for Claude Code use `.agent/skills/dispatch-watcher-claude/SKILL.md`, for Codex CLI use `.agent/skills/dispatch-watcher/SKILL.md`). Use on Gemini session start to run pre-flight, claim Slack-dispatched issues (@gemini #N), and emit lifecycle events. Triggers: Gemini session start, /dispatch, /agent-presence, message addressed to @gemini in the dispatch channel.
Optional agent dispatch watcher — Phase 1 walking skeleton, Codex-flavored. Use on agent session start when a Slack-style dispatch channel assigns GitHub issues to a model handle such as @codex. For Claude use `.agent/skills/dispatch-watcher-claude/SKILL.md`, for Gemini use `.agent/skills/dispatch-watcher-gemini/SKILL.md`, for the full multi-agent contract see `.agent/skills/agent-presence/SKILL.md`.
PR merge supervisor workflow. Use to merge a GitHub PR safely — resolve review threads correctly, check CI, run an optional repo supervisor, and do post-merge cleanup. Trigger when: /merge, merge PR, complete a PR, finalize a PR.
Use when generating operational reports, release notes, demo readiness checks, stakeholder updates, infrastructure cost/expiry checks, or bilingual changelogs. Triggers: /release-notes, /investor-report, /demo-check, /cost-check, changelog, release notes, stakeholder report, monthly metrics, demo readiness, before demo, infrastructure costs, cost monitoring, certificate expiry.