DeepChat Release Process
ThinkInAIXYZ/deepchat
Runs the DeepChat repository's release flow: prepares bilingual release notes and a version bump on dev, cuts or updates a release branch, then fast-forwards main and tags the version.
Write changelogs and release notes readers actually benefit from — changes translated to so-whats, grouped by reader impact (breaking first, gifts second, plumbing last), with the upgrade path…
Install Changelog For Humans
$ npx skills add mohitagw15856/pm-claude-skills --skill changelog-for-humans -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills changelog-for-humans --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-for-humans .claude/skills/changelog-for-humans && 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-for-humans" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/changelog-for-humans into .claude/skills/changelog-for-humans/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "changelog-for-humans", 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-for-humansType 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-for-humans -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills changelog-for-humans --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-for-humans .agents/skills/changelog-for-humans && 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-for-humans" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/changelog-for-humans into .agents/skills/changelog-for-humans/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "changelog-for-humans", 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-for-humans -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills changelog-for-humans --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-for-humans .cursor/skills/changelog-for-humans && 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-for-humans" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/changelog-for-humans into .cursor/skills/changelog-for-humans/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "changelog-for-humans", 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-for-humans--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-for-humans -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills changelog-for-humans --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-for-humans .gemini/skills/changelog-for-humans && 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-for-humans" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/changelog-for-humans into .gemini/skills/changelog-for-humans/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "changelog-for-humans", 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-for-humansInstalls 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-for-humans -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-for-humans .github/skills/changelog-for-humans && 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-for-humans" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/changelog-for-humans into .github/skills/changelog-for-humans/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "changelog-for-humans", 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-for-humans -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-for-humans --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-for-humans .opencode/skills/changelog-for-humans && 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-for-humans" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/changelog-for-humans into .opencode/skills/changelog-for-humans/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "changelog-for-humans", 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-for-humans- GitHub stars
- 1.4k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 652 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Write changelogs and release notes readers actually benefit from — changes translated to so-whats, grouped by reader impact (breaking first, gifts second, plumbing last), with the upgrade path…
- Works in 5 steps: So-what or silence: every entry passes… → Breaking changes lead, with verbs: the ⚠… → Write the reader's grammar: "You can… → …
- Asked write the release notes
- SKILL.md covers What This Skill Produces, Required Inputs, Framework: The Translation Rules and Output Format, plus 6 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Changelog For Humans is an agent skill from mohitagw15856/pm-claude-skills. Write changelogs and release notes readers actually benefit from — changes translated to so-whats, grouped by reader impact (breaking first, gifts second, plumbing last), with the upgrade path stated and the marketing kept honest. Use when asked write the release notes, turn this commit list into a changelog, announce this update to users, or why does nobody read our changelogs. Produces the impact-grouped changelog, the so-what translations, the breaking-changes block with migration steps, and the two-audience…
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 and Translation. 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 write the release notes
- Turn this commit list into a changelog
- Announce this update to users
- Why does nobody read our changelogs
Example prompts
- “/changelog-for-humans”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- So-what or silence: every entry passes "what does the reader now experience differently?" — "Refactored the auth middleware" fails…
- Breaking changes lead, with verbs: the ⚠ block comes first regardless of how exciting the features are — who's affected, what stops…
- Write the reader's grammar: "You can now…" beats "Added support for…" — second person, present tense, the reader as subject. Feature names…
- Honest marketing, sized claims: "faster" carries its number when one exists ("~40% faster on large files"), known limitations ride along…
- Depth per channel, one source: the full changelog is written once (docs-grade), then compressed: email gets the breaking block + top…
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
No scripts in the folder and no shell commands in SKILL.md.
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
Changelog For Humans loads about 1.3k tokens when it runs. Until then it costs about 139 tokens; SKILL.md has 652 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). 652 words, ~1,297 tokens.
Download SKILL.mdSave it as
.claude/skills/changelog-for-humans/SKILL.md (or your agent's skills folder).- name
- changelog-for-humans
- description
- Write changelogs and release notes readers actually benefit from — changes translated to so-whats, grouped by reader impact (breaking first, gifts second, plumbing last), with the upgrade path stated and the marketing kept honest. Use when asked write the release notes, turn this commit list into a changelog, announce this update to users, or why does nobody read our changelogs. Produces the impact-grouped changelog, the so-what translations, the breaking-changes block with migration steps, and the two-audience split when needed.
Changelog For Humans Skill
Commit lists are what happened; changelogs are what it means for you — and most teams publish the former with headers. The human version translates each change into its so-what ("Faster search" → "Search results now return in under a second on large workspaces"), orders by reader impact — breaking changes first with migration steps, improvements second, internal plumbing compressed to a line — and never buries the one thing users must do behind twelve things the team is proud of. When audiences diverge (end users vs. developers), the changelog splits rather than serving both badly.
What This Skill Produces
- The impact-grouped changelog — ⚠ breaking/action-needed → ✨ new & improved → 🔧 fixes → (plumbing, one line)
- The so-what translations — each entry: what changed for the reader, not what the team did
- The breaking block — who's affected, what breaks, the migration steps, the deadline if one exists
- The audience split — the user-facing notes and the developer/API notes, separated when their so-whats differ
Required Inputs
Ask for these if not provided:
- The raw changes — commits, PR titles, the team's list; translation needs the source material and the actual user-visible effect of each (ask when a commit's impact is unclear — guessing so-whats manufactures lies)
- The readers — end users? admins? API consumers? Their vocabulary and their stakes decide the grouping and whether the split applies
- The action items — anything readers must do (migrate, re-auth, update configs) — these outrank everything and need deadlines
- The channel — in-app note (three lines), email (skimmable), docs page (complete) — the same release ships different depths
Framework: The Translation Rules
- So-what or silence: every entry passes "what does the reader now experience differently?" — "Refactored the auth middleware" fails (plumbing line); "You stay logged in across devices now" passes. Changes with no reader-visible effect compress to "plus internal improvements" — honesty and mercy.
- Breaking changes lead, with verbs: the ⚠ block comes first regardless of how exciting the features are — who's affected, what stops working, the numbered migration steps, the date. Burying an action-needed under feature marketing is how support tickets get scheduled.
- Write the reader's grammar: "You can now…" beats "Added support for…" — second person, present tense, the reader as subject. Feature names the team invented get one explanatory clause on first use.
- Honest marketing, sized claims: "faster" carries its number when one exists ("~40% faster on large files"), known limitations ride along ("not yet on mobile"), and fixed bugs are stated plainly — readers who hit the bug deserve to find its fix by searching the changelog. Overclaiming buys one release of excitement and a subscription of skepticism.
- Depth per channel, one source: the full changelog is written once (docs-grade), then compressed: email gets the breaking block + top three, in-app gets one line + link. Compression cuts entries, never the breaking block — it survives at every depth.
Show full SKILL.md (190 more words)Show less
Output Format
[Product] — [version/date]
⚠ Action needed
[Who's affected · what breaks · migration steps, numbered · by when]
✨ New & improved
[Per entry: "You can now [so-what]." — number-carrying claims, limitations attached]
🔧 Fixed
[Plain statements — searchable by the sufferers]
Plus internal improvements.
[Channel cuts: email version · in-app line — breaking block preserved in all]
Quality Checks
- Every entry states a reader-visible so-what or lives in the plumbing line
- Breaking/action-needed leads, with steps and dates
- Claims carry their numbers and their limitations
- The reader is the grammatical subject throughout
- Channel versions all retain the breaking block
Anti-Patterns
- Do not publish the commit list with a header — that's the team's diary, not the reader's news
- Do not bury action-needed under features — excitement doesn't file the migration for them
- Do not overclaim improvements — the number or a modest verb
- Do not hide fixed bugs in vague language — the people who hit them are searching for exactly those words
- Do not write one changelog for two audiences with different stakes — split it or lose both
Example Trigger Phrases
- "Write the release notes."
- "Turn this commit list into a changelog."
- "Announce this update to users."
- "Why does nobody read our changelogs?"
© 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-for-humans of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Changelog For Humans 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 For Humans this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1.3k | Automated safety check: Pass | MIT | |
| DeepChat Release ProcessThinkInAIXYZ/deepchat | 6.4k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| D2mcpp Authoringmcpp-community/d2mcpp | 1.8k | — | ~2.7k | Automated safety check: Pass | Custom licence | |
| Pre ReleaseZhuoZhuoCrayon/throttled-py | 651 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Pulse Releasequnqin24/Pulse | 521 | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Release WorkflowCaldis/react-zmage | 945 | — | ~3.6k | Automated safety check: Notes | MIT |
Similar skills
D2mcpp Authoring
mcpp-community/d2mcpp
Authoring conventions, design principles, and file formats for the d2mcpp (D2X) Modern C++ tutorial project.
Pre Release
ZhuoZhuoCrayon/throttled-py
Automates release preparation for throttled-py. An agent skill from ZhuoZhuoCrayon/throttled-py.
Pulse Release
qunqin24/Pulse
Release a new Pulse version end to end — checks, bilingual CHANGELOG entry, VERSION, tag, the release workflow, syncing main, and the issue replies that go with it.
Release Workflow
Caldis/react-zmage
A skill your agent uses when the user wants to ship a new version of react-zmage to npm.
Publish Release
Ayuilos/Miffan
Publish a GitHub release for this fork, with a bilingual changelog that separates fork-owned changes from changes introduced by upstream merges.
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
Categories
Questions about Changelog For Humans
What does Changelog For Humans do?
Write changelogs and release notes readers actually benefit from — changes translated to so-whats, grouped by reader impact (breaking first, gifts second, plumbing last), with the upgrade path…. Changelog For Humans is an agent skill from mohitagw15856/pm-claude-skills. Write changelogs and release notes readers actually benefit from — changes translated to so-whats, grouped by reader impact (breaking first, gifts second, plumbing last), with the upgrade path stated and the marketing kept honest.
When should I use Changelog For Humans?
Changelog For Humans fits situations like: asked write the release notes; turn this commit list into a changelog; announce this update to users; why does nobody read our changelogs.
How do I install Changelog For Humans in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill changelog-for-humans -a claude-code`. Or copy the skill folder (skills/changelog-for-humans in mohitagw15856/pm-claude-skills) into .claude/skills/changelog-for-humans in your project. Claude Code loads it when a task matches its description.
How do I install Changelog For Humans in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill changelog-for-humans -a codex`. Or copy the skill folder (skills/changelog-for-humans in mohitagw15856/pm-claude-skills) into .agents/skills/changelog-for-humans in your project. Codex loads it when a task matches its description.
Can I use Changelog For Humans 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-for-humans -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-for-humans, .gemini/skills/changelog-for-humans, .github/skills/changelog-for-humans and .opencode/skills/changelog-for-humans in your project.
What does Changelog For Humans need to run?
SKILL.md names no scripts, command-line tools or credentials: Changelog For Humans is instructions for the agent only.
Does Changelog For Humans 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 Changelog For Humans 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 For Humans use?
Changelog For Humans 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 For Humans use?
About 1.3k tokens (SKILL.md is roughly 5.2k 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 For Humans?
Skills that share tags, products or a category with Changelog For Humans: DeepChat Release Process (ThinkInAIXYZ/deepchat, 6.4k stars), D2mcpp Authoring (mcpp-community/d2mcpp, 1.8k stars), Pre Release (ZhuoZhuoCrayon/throttled-py, 651 stars) and Pulse Release (qunqin24/Pulse, 521 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Changelog For Humans?
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.