course-project

Curate the [Unreleased] section of docs/CHANGELOG.md from git history. Triggers on "curate the changelog", "update the changelog", "/gen-changelog", "онови changelog", "курування журналу". Reads git log since the last tag, FILTERS out what a reader never feels (test/ci/chore/merge), GROUPS commits about one feature into one bullet, and REWRITES technical subjects into plain language under the six Keep a Changelog categories (Added/Changed/Deprecated/ Removed/Fixed/Security). The result must have FEWER lines than the raw log — that is the proof of curation, not a dump. Leaves the edit in the working tree; never commits or pushes.

Draft and save partner-facing release notes from the same commits as the changelog. Triggers on "draft release notes", "release notes for the next version", "/release-notes", "нотатки релізу", "release notes партнеру". Same input as gen-changelog, different audience and tone: a short, benefit-first narrative for a user or partner — "what's new for you" — not a categorized engineer's list. Keeps only changes a user actually notices; drops internal refactors and tooling. Saves the notes to docs/release-notes/vX.Y.Z.md (the version comes from package.json) and echoes them in the chat, to seed a GitHub Release description or a partner announcement.

Announce a finished release to the team Telegram channel. Triggers on "announce the release on Telegram", "post the release notes to Telegram", "/announce-telegram", "анонсуй реліз у телеграм", "оголоси реліз". Reads the saved partner notes (docs/release-notes/vX.Y.Z.md), shows the EXACT message and the EXACT target chat, and waits for an explicit yes before sending via the Telegram Bot API (TELEGRAM_BOT_TOKEN + TELEGRAM_CHAT_ID). This is an OUTBOUND step — once sent, the message is public to the channel and cannot be unsent. It never decides on its own to announce.

Decide and apply the next semver for a release. Triggers on "bump the version", "what version is next", "/bump-version", "простав версію", "яка наступна версія". Reads the next number from the deterministic scripts/next-version.sh (NEVER guesses it), explains in plain language WHICH part moved and why (e.g. "MINOR, because a feat landed: filter memes by tag"), edits the version field in package.json, and proposes the matching `git tag vX.Y.Z`. The number is decided by a rule; the agent explains and applies — the human confirms the tag. Never pushes a tag itself.

Generate the user-facing guide for this release, with real screenshots. Triggers on "generate the user docs", "write the user guide", "/generate-user-docs", "згенеруй документацію", "користувацька документація". Runs the deterministic scripts/capture-screenshots.mjs (Playwright — NO LLM renders the picture) to shoot the app's key screens into docs/user-guide/img/, then WRITES the guide pages under docs/user-guide/*.md, embedding those shots. The screenshotter is the rule; the agent writes the words around it. This runs as the second stage of /release: it prepares docs/user-guide/** in the working tree; /release commits it into the one release PR. It never commits, pushes, or publishes to Redmine itself.

Publish the release's user guide to the Redmine wiki. Triggers on "publish the docs to Redmine", "push the user guide to Redmine", "/publish-redmine", "опублікуй документацію в redmine", "виклади в redmine". This is the LOCAL MIRROR of the merge gate's Redmine step — in the real flow CI publishes on the release-PR merge; run this to rehearse the same publish from your machine. Reads docs/user-guide/*.md, shows the EXACT pages and the EXACT Redmine target, and waits for an explicit yes before PUTting each page to the wiki via the REST API (REDMINE_URL, REDMINE_API_KEY, REDMINE_PROJECT). Outbound and terminal: it publishes, it does not commit or push.

Prepare a release locally and open the release PR. Triggers on "run the release", "prepare a release", "/release", "зроби реліз", "підготуй реліз". Does the two steps that need a human and a running app: bumps the version (bump-version) and generates the user guide with real screenshots (generate-user-docs, against your locally running app — CI can't boot it). Then commits both, pushes the branch, and opens ONE pull request. Merging that PR is the gate: CI writes the changelog and release notes, tags, publishes the GitHub Release, announces on Telegram, and publishes the guide to the Redmine wiki. This skill never writes the changelog or notes, never tags, and never sends anything outbound — the merge does all of that.

Turn a repeated mistake into a durable, path-scoped rule in .claude/rules/. Triggers on "codify this rule", "make a rule so this doesn't happen again", "/codify-rule", "закодифікуй правило", "петля помилка-правило". Use only when the same mistake showed up TWICE (twice = a pattern, once = noise). Names the wrong shape and the right shape with one short example of each, scopes the rule to the paths that matter, and leaves the edit in the working tree so the next agent on this repo inherits the fix. Edits only .claude/rules/; never commits or pushes.