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.
Write a human changelog from the REAL commit history — read the actual commit range via the GitHub connector, not a template.
Install Changelog From Commits
$ npx skills add mohitagw15856/pm-claude-skills --skill changelog-from-commits -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills changelog-from-commits --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/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/changelog-from-commits .claude/skills/changelog-from-commits && 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 "changelog-from-commits" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/changelog-from-commits into .claude/skills/changelog-from-commits/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "changelog-from-commits", 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/mohitagw15856/pm-claude-skills/tree/main/skills/changelog-from-commitsType 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 mohitagw15856/pm-claude-skills --skill changelog-from-commits -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills changelog-from-commits --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/changelog-from-commits .agents/skills/changelog-from-commits && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "changelog-from-commits" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/changelog-from-commits into .agents/skills/changelog-from-commits/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "changelog-from-commits", 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 mohitagw15856/pm-claude-skills --skill changelog-from-commits -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills changelog-from-commits --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/changelog-from-commits .cursor/skills/changelog-from-commits && 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 "changelog-from-commits" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/changelog-from-commits into .cursor/skills/changelog-from-commits/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "changelog-from-commits", 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/mohitagw15856/pm-claude-skills.git --path skills/changelog-from-commits--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 mohitagw15856/pm-claude-skills --skill changelog-from-commits -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills changelog-from-commits --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/changelog-from-commits .gemini/skills/changelog-from-commits && 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 "changelog-from-commits" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/changelog-from-commits into .gemini/skills/changelog-from-commits/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "changelog-from-commits", 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 mohitagw15856/pm-claude-skills changelog-from-commitsInstalls 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 mohitagw15856/pm-claude-skills --skill changelog-from-commits -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/changelog-from-commits .github/skills/changelog-from-commits && 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 "changelog-from-commits" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/changelog-from-commits into .github/skills/changelog-from-commits/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "changelog-from-commits", 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 mohitagw15856/pm-claude-skills --skill changelog-from-commits -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills changelog-from-commits --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/changelog-from-commits .opencode/skills/changelog-from-commits && 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 "changelog-from-commits" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/changelog-from-commits into .opencode/skills/changelog-from-commits/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "changelog-from-commits", 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
changelog-from-commits- GitHub stars
- 1.4k
- Token cost
- ~1k tokens
- SKILL.md length
- 460 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Write a human changelog from the REAL commit history — read the actual commit range via the GitHub connector, not a template.
- Works in 5 steps: Group by impact — Added / Changed /… → Translate — every entry says what the… → Dedupe & merge — many commits behind one… → …
- Asked to write the changelog for this release
- SKILL.md covers What This Skill Produces, Required Inputs, Framework: Commits → Changelog and Execution (Cowork), plus 4 more sections
- Calls git
What it does
Changelog From Commits is an agent skill from mohitagw15856/pm-claude-skills. Write a human changelog from the REAL commit history — read the actual commit range via the GitHub connector, not a template. Use when asked to write the changelog for this release, what changed since the last tag, draft release notes from my commits, or summarise this range for users in Cowork. Reads commits/PRs between two refs via the GitHub connector, groups them into user-facing changes (features / fixes / breaking), translates commit-speak into human benefit, and produces a changelog artifact ready for the…
Its SKILL.md is about 1k 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: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Asked to write the changelog for this release
- What changed since the last tag
- Draft release notes from my commits
- Summarise this range for users in Cowork
Example prompts
- “/changelog-from-commits”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Group by impact — Added / Changed / Fixed / Breaking; drop internal-only churn (chore/ci/refactor) unless it changes behaviour.
- Translate — every entry says what the user can now do or no longer suffers, not the implementation.
- Dedupe & merge — many commits behind one feature become one line.
- Breaking first — removals, renames, and migrations lead, with the upgrade step.
- Credit & links — PR numbers/authors where it helps.
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. 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
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
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
Changelog From Commits loads about 1k tokens when it runs. Until then it costs about 137 tokens; SKILL.md has 460 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 mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 460 words, ~1,006 tokens.
Download SKILL.mdSave it as
.claude/skills/changelog-from-commits/SKILL.md (or your agent's skills folder).- name
- changelog-from-commits
- description
- Write a human changelog from the REAL commit history — read the actual commit range via the GitHub connector, not a template. Use when asked to write the changelog for this release, what changed since the last tag, draft release notes from my commits, or summarise this range for users in Cowork. Reads commits/PRs between two refs via the GitHub connector, groups them into user-facing changes (features / fixes / breaking), translates commit-speak into human benefit, and produces a changelog artifact ready for the release.
Changelog from Commits (Live)
Users don't read commit messages, and they shouldn't have to. In Claude Cowork this skill reads the real commit range and turns it into a changelog written for the people who use the software — grouped, deduped, and translated from "refactor: extract helper" into what actually changed for them.
What This Skill Produces
- The changelog — grouped into Added / Changed / Fixed / Breaking, each entry written as user-facing benefit, not commit-speak
- The breaking-change callout — migrations and removals pulled to the top with what to do
- A changelog artifact — Keep-a-Changelog style, ready to paste into
CHANGELOG.mdor a release
Required Inputs
Ask for these if not provided:
- The range — from tag/ref to tag/ref (default: last tag → HEAD), and the repo
- The audience — end users, API consumers, or developers — translation depth follows
- Version & date — the release number and date for the heading
Framework: Commits → Changelog
- Group by impact — Added / Changed / Fixed / Breaking; drop internal-only churn (chore/ci/refactor) unless it changes behaviour.
- Translate — every entry says what the user can now do or no longer suffers, not the implementation.
- Dedupe & merge — many commits behind one feature become one line.
- Breaking first — removals, renames, and migrations lead, with the upgrade step.
- Credit & links — PR numbers/authors where it helps.
Execution (Cowork)
- Read the range — via the GitHub connector, list commits (and merged PRs) between the two refs, with messages, PR titles, and labels.
- Classify — map each to Added/Changed/Fixed/Breaking; set aside pure-internal churn; detect breaking changes from
!/BREAKING CHANGE/removed-public-API signals. - Translate & merge — collapse the commits behind each user-facing change into one benefit-led line; keep PR references.
- Order — breaking first, then Added, Changed, Fixed.
- Emit the artifact — the changelog block; offer to prepend it to
CHANGELOG.mdor attach to a release, only on request.
Guardrails: include only changes actually present in the range — never invent a feature; base "breaking" on real signals, not guesses; don't overstate impact; if the connector is unauthorised, work from a pasted git log and say the range couldn't be read live.
Show full SKILL.md (121 more words)Show less
Output Format
A Changelog block:
## [version] — date
### ⚠ Breaking
- what changed → what to do (#PR)
### Added
- user-facing capability (#PR)
### Changed
- what's different now (#PR)
### Fixed
- the problem that's gone (#PR)Quality Checks
- Every entry maps to a real commit/PR in the range
- Entries read as user benefit, not commit messages
- Breaking changes lead and include the migration step
- Internal-only churn was excluded (unless it changed behaviour)
- Multiple commits behind one feature are a single line
Anti-Patterns
- Pasting raw commit messages as the changelog.
- Inventing a feature not in the range to round it out.
- Burying a breaking change in the middle of "Changed".
- Listing every
chore:/refactor:that users never see.
Example Trigger Phrases
- "Write the changelog since the last tag in Cowork."
- "Draft release notes from my commits for v2.0."
- "What changed for users between v1.4 and HEAD?"
- "Summarise this commit range as a human changelog."
© mohitagw15856, MIT. 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 skills/changelog-from-commits of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Changelog From Commits 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 |
|---|---|---|---|---|---|---|
| Changelog From Commits this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1k | Automated safety check: Pass | MIT | |
| Cutting A ReleaseTriliumNext/Trilium | 38k | — | ~3.2k | Automated safety check: Pass | AGPL-3.0 | |
| Rea Changelog Updatemorluto/rea | 80k | — | ~1.9k | Automated safety check: Pass | MIT | |
| 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 |
Similar skills
Rea Changelog Update
morluto/rea
Prepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.
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.
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Related
Works with
Categories
Questions about Changelog From Commits
What does Changelog From Commits do?
Write a human changelog from the REAL commit history — read the actual commit range via the GitHub connector, not a template. Changelog From Commits is an agent skill from mohitagw15856/pm-claude-skills. Write a human changelog from the REAL commit history — read the actual commit range via the GitHub connector, not a template.
When should I use Changelog From Commits?
Changelog From Commits fits situations like: asked to write the changelog for this release; what changed since the last tag; draft release notes from my commits; summarise this range for users in Cowork.
How do I install Changelog From Commits in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill changelog-from-commits -a claude-code`. Or copy the skill folder (skills/changelog-from-commits in mohitagw15856/pm-claude-skills) into .claude/skills/changelog-from-commits in your project. Claude Code loads it when a task matches its description.
How do I install Changelog From Commits in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill changelog-from-commits -a codex`. Or copy the skill folder (skills/changelog-from-commits in mohitagw15856/pm-claude-skills) into .agents/skills/changelog-from-commits in your project. Codex loads it when a task matches its description.
Can I use Changelog From Commits 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 mohitagw15856/pm-claude-skills --skill changelog-from-commits -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/changelog-from-commits, .gemini/skills/changelog-from-commits, .github/skills/changelog-from-commits and .opencode/skills/changelog-from-commits in your project.
What does Changelog From Commits need to run?
Going by SKILL.md and its folder, Changelog From Commits needs the command-line tools its instructions call (git).
Does Changelog From Commits access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Changelog From Commits 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 Changelog From Commits use?
Changelog From Commits is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Changelog From Commits use?
About 1k tokens (SKILL.md is roughly 4k 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 Changelog From Commits?
Skills that share tags, products or a category with Changelog From Commits: Cutting A Release (TriliumNext/Trilium, 38k stars), Rea Changelog Update (morluto/rea, 80k stars), Mole CLI Release Flow (tw93/Mole, 70k stars) and Draft Release Notes (jamiepine/voicebox, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Changelog From Commits?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.