跳到正文
cccskills
免费在 GitHub 公开

changelog-for-humans

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.

中文简介正在准备中。当前显示原文说明。

实测评分 未实测

查看安装方法

包含的文件(1)

  • SKILL.md5.2 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

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

  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. 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.

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?"

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.

中文简介正在准备中。当前显示原文说明。

mohitagw15856/pm-claude-skills14822026年10月23日 更新

Decode a 401k or workplace retirement plan — the real cost of its funds, the match's fine print, vesting math, and the plan features worth using or avoiding. Use when someone asks 'is my 401k any good', 'decode my 401k plan', 'which funds should I look at', or 'what fees am I paying'. Produces a fee decode in dollars-over-time, match and vesting math, a fund-lineup triage by cost, and the questions for HR or the plan administrator.

中文简介正在准备中。当前显示原文说明。

mohitagw15856/pm-claude-skills14822026年10月23日 更新

Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.

中文简介正在准备中。当前显示原文说明。

mohitagw15856/pm-claude-skills14822026年10月23日 更新

Analyse a finished A/B test and write the readout — the result, whether it's statistically and practically significant, what it means, and the ship/no-ship call. Use when asked to analyse experiment results, write an A/B test readout, interpret test data, or decide whether to ship a variant. Produces a clear verdict with the lift and confidence, segment cuts, the risks (peeking, novelty, sample), and a recommendation. Distinct from planning a test — this reads results.

中文简介正在准备中。当前显示原文说明。

mohitagw15856/pm-claude-skills14822026年10月23日 更新

Build or tailor an academic CV for faculty, postdoc, research or fellowship applications: publications, grants, teaching, supervision and service in the order the field expects, with consistent citations. Use when asked to write my academic CV, update my CV for a lectureship, tenure-track or postdoc application, format my publications list, or adapt my academic CV for an industry research role. Produces the full academic CV, a field-appropriate section order, a clean publications list in one citation style, and a two-page summary version when asked.

中文简介正在准备中。当前显示原文说明。

mohitagw15856/pm-claude-skills14822026年10月23日 更新

Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.

中文简介正在准备中。当前显示原文说明。

mohitagw15856/pm-claude-skills14822026年10月23日 更新

查看 mohitagw15856 的全部技能

报告此技能的问题