Cutting A Release
TriliumNext/Trilium
A skill your agent uses when cutting, preparing, or debugging a Trilium release — bumping the monorepo version, tagging, or diagnosing a failed "Release" workflow run.
A skill your agent uses when rewriting CHANGELOG.md, GitHub release notes, or Release Please PR changelog sections into user-facing release notes; do not use for release publishing, assets, licence…
Install User Facing Changelog
$ npx skills add kernitus/BukkitOldCombatMechanics --skill user-facing-changelog -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install kernitus/BukkitOldCombatMechanics user-facing-changelog --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/kernitus/BukkitOldCombatMechanics.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/user-facing-changelog .claude/skills/user-facing-changelog && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "user-facing-changelog" agent skill from https://github.com/kernitus/BukkitOldCombatMechanics/tree/master/.agents/skills/user-facing-changelog into .claude/skills/user-facing-changelog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "user-facing-changelog", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/kernitus/BukkitOldCombatMechanics/tree/master/.agents/skills/user-facing-changelogType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add kernitus/BukkitOldCombatMechanics --skill user-facing-changelog -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install kernitus/BukkitOldCombatMechanics user-facing-changelog --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kernitus/BukkitOldCombatMechanics.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/user-facing-changelog .agents/skills/user-facing-changelog && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "user-facing-changelog" agent skill from https://github.com/kernitus/BukkitOldCombatMechanics/tree/master/.agents/skills/user-facing-changelog into .agents/skills/user-facing-changelog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "user-facing-changelog", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add kernitus/BukkitOldCombatMechanics --skill user-facing-changelog -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install kernitus/BukkitOldCombatMechanics user-facing-changelog --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kernitus/BukkitOldCombatMechanics.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/user-facing-changelog .cursor/skills/user-facing-changelog && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "user-facing-changelog" agent skill from https://github.com/kernitus/BukkitOldCombatMechanics/tree/master/.agents/skills/user-facing-changelog into .cursor/skills/user-facing-changelog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "user-facing-changelog", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/kernitus/BukkitOldCombatMechanics.git --path .agents/skills/user-facing-changelog--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add kernitus/BukkitOldCombatMechanics --skill user-facing-changelog -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install kernitus/BukkitOldCombatMechanics user-facing-changelog --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kernitus/BukkitOldCombatMechanics.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/user-facing-changelog .gemini/skills/user-facing-changelog && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "user-facing-changelog" agent skill from https://github.com/kernitus/BukkitOldCombatMechanics/tree/master/.agents/skills/user-facing-changelog into .gemini/skills/user-facing-changelog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "user-facing-changelog", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install kernitus/BukkitOldCombatMechanics user-facing-changelogInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add kernitus/BukkitOldCombatMechanics --skill user-facing-changelog -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/kernitus/BukkitOldCombatMechanics.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/user-facing-changelog .github/skills/user-facing-changelog && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "user-facing-changelog" agent skill from https://github.com/kernitus/BukkitOldCombatMechanics/tree/master/.agents/skills/user-facing-changelog into .github/skills/user-facing-changelog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "user-facing-changelog", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add kernitus/BukkitOldCombatMechanics --skill user-facing-changelog -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install kernitus/BukkitOldCombatMechanics user-facing-changelog --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kernitus/BukkitOldCombatMechanics.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/user-facing-changelog .opencode/skills/user-facing-changelog && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "user-facing-changelog" agent skill from https://github.com/kernitus/BukkitOldCombatMechanics/tree/master/.agents/skills/user-facing-changelog into .opencode/skills/user-facing-changelog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "user-facing-changelog", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
user-facing-changelog- GitHub stars
- 225
- Token cost
- ~1.3k tokens
- SKILL.md length
- 626 words
- Files
- 1
- Skills in repo
- 9
- Repo updated
- First seen
- Licence
- MPL-2.0
At a glance
A skill your agent uses when rewriting CHANGELOG.md, GitHub release notes, or Release Please PR changelog sections into user-facing release notes; do not use for release publishing, assets, licence…
- Works in 6 steps: Edit the generated release section in… → Replace the matching release section in… → Preserve the PR body's :robot: header,… → …
- Rewriting CHANGELOG.md
- SKILL.md covers When to use, When not to use, Context gathering and Release Please pull requests, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
User Facing Changelog is an agent skill from kernitus/BukkitOldCombatMechanics. Use when rewriting CHANGELOG.md, GitHub release notes, or Release Please PR changelog sections into user-facing release notes; do not use for release publishing, assets, licence, or workflow readiness checks.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Changelog and release notes. It works with GitHub. The repository describes itself as: Minecraft plugin to configure combat mechanics for 1.9 onwards. The licence is MPL-2.0.
When your agent uses it
- Rewriting CHANGELOG.md
- GitHub release notes
- Release Please PR changelog sections into user-facing release notes
- Do not use for release publishing
Example prompts
- “/user-facing-changelog”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Edit the generated release section in CHANGELOG.md on the Release Please branch.
- Replace the matching release section in the PR body with the same user-facing prose. A commit that changes CHANGELOG.md does not…
- Preserve the PR body's :robot: header, horizontal-rule separators, version heading, and final Release Please attribution because its…
- Put the standard issue-reporting footer inside the release section, before the final separator, so it reaches the GitHub release and…
- Make manual changelog and PR-body edits after Release Please's final automatic refresh where practical. A later refresh may overwrite them.
- Before merging, verify that the release prose in CHANGELOG.md and the PR body agrees and that the PR retains its autorelease: pending label.
What it can do on your machine
Read from SKILL.md and the folder at commit e66e7a9. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
User Facing Changelog loads about 1.3k tokens when it runs. Until then it costs about 58 tokens; SKILL.md has 626 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from kernitus/BukkitOldCombatMechanics at commit e66e7a9, republished under its MPL-2.0 licence (© kernitus). 626 words, ~1,251 tokens.
Download SKILL.mdSave it as
.claude/skills/user-facing-changelog/SKILL.md (or your agent's skills folder).- name
- user-facing-changelog
- description
- Use when rewriting CHANGELOG.md, GitHub release notes, or Release Please PR changelog sections into user-facing release notes; do not use for release publishing, assets, licence, or workflow readiness checks.
User-facing Changelog
Use this skill to turn generated or developer-oriented changelog material into concise release notes that explain what users will experience after installing the release. Keep wording accurate, useful, and in British English.
When to use
- Rewriting
CHANGELOG.mdentries for a release. - Drafting or polishing GitHub release notes.
- Reworking Release Please PR changelog sections before publishing.
- Converting commit subjects, issue links, or PR notes into user-facing release prose.
When not to use
- Do not use for release readiness checks, upload assets, licence review, supported-version checks, or publishing workflow validation; use
release-readiness-reviewfor those tasks. - Do not use for broad PR descriptions unless the requested output is specifically a release-note or changelog section; use
pr-draft-summaryfor reviewer-facing prose.
Context gathering
- Before rewriting, fetch linked GitHub issues and PRs where available from commit subjects, changelog entries, compare views, or release notes.
- Use explicit GitHub URLs first. If only issue or PR numbers are present, resolve them against
https://github.com/kernitus/BukkitOldCombatMechanics. - Read enough issue, PR, and commit context to understand the user-visible problem and final shipped behaviour, but avoid broad repository exploration unless the requested rewrite needs it.
- Preserve useful issue links, especially when an entry fixes a reported bug or closes a user request.
Release Please pull requests
For this repository, CHANGELOG.md is the durable repository record, but the Release Please pull-request body is load-bearing release metadata. After the release PR merges, Release Please parses that body to create the GitHub release. The published GitHub release body then becomes the text passed to CurseForge and Hangar through github.event.release.body in .github/workflows/build-upload-release.yml.
When rewriting a Release Please release:
- Edit the generated release section in
CHANGELOG.mdon the Release Please branch. - Replace the matching release section in the PR body with the same user-facing prose. A commit that changes
CHANGELOG.mddoes not synchronise the PR body automatically. - Preserve the PR body's
:robot:header, horizontal-rule separators, version heading, and final Release Please attribution because its structure is parsed by Release Please. - Put the standard issue-reporting footer inside the release section, before the final separator, so it reaches the GitHub release and downstream publishing platforms.
- Make manual changelog and PR-body edits after Release Please's final automatic refresh where practical. A later refresh may overwrite them.
- Before merging, verify that the release prose in
CHANGELOG.mdand the PR body agrees and that the PR retains itsautorelease: pendinglabel.
If the user asks only for revised prose, provide the complete replacement PR body and do not mutate GitHub without explicit authorisation.
Show full SKILL.md (208 more words)Show less
Writing rules
- Describe only final shipped user-visible behaviour.
- Do not mention interim development churn. If a regression was introduced and fixed between releases and never reached users, omit it entirely or fold it into the final behaviour without saying it regressed.
- Avoid noisy implementation, refactor, build, formatting, dependency, and test-only entries unless they matter to server owners, administrators, plugin integrators, or players.
- Prefer clear categories such as
Highlights,Fixes,Compatibility,Configuration,API and integrations, orMaintenancewhen they help readers scan the release. - Group related low-level commits into one user-facing entry rather than listing every commit.
- Keep entries concise, concrete, and outcome-focused. Mention affected modules, Minecraft versions, configuration keys, or integrations when that helps users decide whether to update.
- Use British English spelling and phraseology throughout.
Footer requirement
At the bottom of CHANGELOG.md and release-note drafts, include a concise issue-reporting sentence that links the word GitHub to the issue tracker:
Report issues on [GitHub](https://github.com/kernitus/BukkitOldCombatMechanics/issues).Quality checklist
- Linked issues and PRs were checked where available.
- The prose avoids unreleased interim churn and describes only shipped behaviour.
- User-relevant categories are clear and not overly fragmented.
- Useful issue links are preserved.
- Test-only, refactor-only, and internal implementation entries are omitted unless user-relevant.
- The issue-reporting footer is present at the bottom when writing changelog or release-note output.
© kernitus, MPL-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/user-facing-changelog of kernitus/BukkitOldCombatMechanics.
Open the folder on GitHubat commit e66e7a9
Compare with similar skills
User Facing Changelog next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| User Facing Changelog this skillkernitus/BukkitOldCombatMechanics | 225 | — | ~1.3k | Automated safety check: Pass | MPL-2.0 | |
| Cutting A ReleaseTriliumNext/Trilium | 38k | — | ~3.2k | Automated safety check: Pass | AGPL-3.0 | |
| Mole CLI Release Flowtw93/Mole | 70k | — | ~2.6k | Automated safety check: Pass | GPL-3.0 | |
| Draft Release Notesjamiepine/voicebox | 57k | — | ~941 | Automated safety check: Pass | MIT | |
| Mole Release Notes Publishertw93/Mole | 70k | — | ~1.9k | Automated safety check: Pass | GPL-3.0 | |
| Release Bumpjamiepine/voicebox | 57k | — | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
Mole CLI Release Flow
tw93/Mole
Runbook for assessing and executing a Mole CLI release: distribution channels, pre-flight checks, capital-V tags, build artifacts and the handoff to curated release notes.
Draft Release Notes
jamiepine/voicebox
Writes or refreshes the Unreleased section of CHANGELOG.md as a themed narrative built from the commits, PRs and diff since the last version tag.
Mole Release Notes Publisher
tw93/Mole
Publishes curated, bilingual release notes for an existing Mole version tag with gh release edit, including contributor thanks and reactions, after the release workflow finishes.
Release Bump
jamiepine/voicebox
Ends a release cycle by moving the Unreleased changelog notes under a dated version heading, bumping version files with bumpversion and tagging the commit.
Cut Release
jfernandez/bpftop
Cut a new versioned release of bpftop — pick the version, open a version-bump PR, sign-tag the merge commit on main, and draft GitHub release notes in the project's established format.
More from kernitus/BukkitOldCombatMechanics
All 9 skills in this repoIntegration Test Verification
kernitus/BukkitOldCombatMechanics
A skill your agent uses when running, selecting, authoring, or triaging integration tests, Kotest specs, Gradle matrix tasks, FakePlayer-backed test cases, or compact test-result files; do not use…
Dependabot PR Review
kernitus/BukkitOldCombatMechanics
A skill your agent uses for Dependabot PRs, dependency bumps, Gradle or Maven dependency updates, GitHub Actions updates, dependency changelog/licence/release-note review, JVM/classfile checks, and…
Module Config Change
kernitus/BukkitOldCombatMechanics
A skill your agent uses for config.yml, module enablement, modesets, config migration, configurable module assignment, and per-module option changes; do not use for unrelated integration-test…
PR Draft Summary
kernitus/BukkitOldCombatMechanics
A skill your agent uses when drafting pull-request titles, descriptions, change summaries, risk notes, validation sections, or reviewer handoff text; do not use for implementation design, release…
Release Readiness Review
kernitus/BukkitOldCombatMechanics
A skill your agent uses for GitHub release, Hangar, CurseForge/BukkitDev upload, Spigot release handoff, licence, asset naming, supported-version, and workflow readiness checks; do not use for…
Compatibility Strategy
kernitus/BukkitOldCombatMechanics
A skill your agent uses for Java 8 backports, Bukkit/Paper version differences, NMS/reflection, PacketEvents compatibility, fake-player implementation choices, and feature-detection design; do not…
Related
Works with
Categories
Questions about User Facing Changelog
What does User Facing Changelog do?
A skill your agent uses when rewriting CHANGELOG.md, GitHub release notes, or Release Please PR changelog sections into user-facing release notes; do not use for release publishing, assets, licence…. User Facing Changelog is an agent skill from kernitus/BukkitOldCombatMechanics.md, GitHub release notes, or Release Please PR changelog sections into user-facing release notes; do not use for release publishing, assets, licence, or workflow readiness checks.
When should I use User Facing Changelog?
User Facing Changelog fits situations like: rewriting CHANGELOG.md; GitHub release notes; release Please PR changelog sections into user-facing release notes; do not use for release publishing.
How do I install User Facing Changelog in Claude Code?
Run `npx skills add kernitus/BukkitOldCombatMechanics --skill user-facing-changelog -a claude-code`. Or copy the skill folder (.agents/skills/user-facing-changelog in kernitus/BukkitOldCombatMechanics) into .claude/skills/user-facing-changelog in your project. Claude Code loads it when a task matches its description.
How do I install User Facing Changelog in Codex?
Run `npx skills add kernitus/BukkitOldCombatMechanics --skill user-facing-changelog -a codex`. Or copy the skill folder (.agents/skills/user-facing-changelog in kernitus/BukkitOldCombatMechanics) into .agents/skills/user-facing-changelog in your project. Codex loads it when a task matches its description.
Can I use User Facing Changelog in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add kernitus/BukkitOldCombatMechanics --skill user-facing-changelog -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/user-facing-changelog, .gemini/skills/user-facing-changelog, .github/skills/user-facing-changelog and .opencode/skills/user-facing-changelog in your project.
What does User Facing Changelog need to run?
SKILL.md names no scripts, command-line tools or credentials: User Facing Changelog is instructions for the agent only.
Does User Facing Changelog access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is User Facing Changelog safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does User Facing Changelog use?
User Facing Changelog is published under the MPL-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does User Facing Changelog use?
About 1.3k tokens (SKILL.md is roughly 5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to User Facing Changelog?
Skills that share tags, products or a category with User Facing Changelog: Cutting A Release (TriliumNext/Trilium, 38k stars), Mole CLI Release Flow (tw93/Mole, 70k stars), Draft Release Notes (jamiepine/voicebox, 57k stars) and Mole Release Notes Publisher (tw93/Mole, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains User Facing Changelog?
kernitus (a GitHub user) maintains it in kernitus/BukkitOldCombatMechanics, which has 225 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 4, 2026.
Source: kernitus/BukkitOldCombatMechanics on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.