Release Notes House Voice

Before you start: read this whole install prompt, tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead before you do anything else. Prerequisites: none for the install itself: no account, no API key, no paid service, and nothing else to install first. The skill is free under the MIT license and is a single instruction file — there is no code, no script and no dependency to install. For using it afterwards I provide the inputs myself: the list of changes (commits, merged pull requests, closed tickets or a pasted changelog) and, ideally, three to twenty past release notes my team actually published, so it can learn our house voice; if I have no examples, it falls back to a neutral style and says so. Install "release-notes-house-voice" for me. It writes customer-facing release notes in the voice of my team's own past release notes: first it learns the house style from my examples and writes a short style card (headline pattern, section names and order, sentence length, person, tense, how features are named, whether fixes are listed individually or summarized, links, emoji or none, what is never mentioned, sign-off), then it sorts the changes (user-visible new capability, improvement, fix, deprecation or breaking change, security, internal only — internal-only changes are dropped from customer notes and listed separately for me), translates each change into what the user can now do or no longer suffers, flags anything whose user impact it cannot tell into a "check with engineering" list instead of the notes (breaking changes and security fixes always go on that list, with the exact wording proposed), and checks the draft against the examples. Its output is the draft release notes, then the style card, then the two author lists (left out as internal, and to confirm with engineering). Its rules: never claim a benefit the change does not deliver, never invent metrics that are not in the input, and keep product and feature names exactly as the examples spell them. Repository: https://github.com/ChenxingJi-Innovate/Cheatcode_ (the skill is the whole packages/pm-comms-kit/skills/release-notes-house-voice/ folder at the pinned commit: SKILL.md only, 1 file) Pinned version: install the code at commit 1071f72533f0a8bb671e2d9b48c8d75f12adc904 exactly. Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Clone https://github.com/ChenxingJi-Innovate/Cheatcode_ into a temporary folder, check out commit 1071f72533f0a8bb671e2d9b48c8d75f12adc904, and copy the packages/pm-comms-kit/skills/release-notes-house-voice/ folder from that checkout. Then compare every file in the folder with the fingerprints recorded for this listing on 2026-10-19: [FINGERPRINTS] - SKILL.md: SHA-256 2614f69773fbbbe9dd6465702a92463430aa369f3eec78dc515c6483b0488b1e If a file does not match, it changed since the listing was prepared: do not install it yet, tell me what you found and let me decide. 2. Read SKILL.md in full, and tell me in plain words: what the skill does when used, which services it connects to, whether it reads or sends any personal information or keys, and anything that seems unusual. Stop on any red flag and tell me before going further. Confirm these points from the file: - The skill folder holds 1 file only: SKILL.md (3,105 bytes). There are no scripts, no code, no assets and no configuration in the folder. The skill is self-contained in that one file: it does not reference the sibling skill comment-replies, the package files packages/pm-comms-kit/README.md, packages/pm-comms-kit/cheatcode.json or packages/pm-comms-kit/.claude-plugin/plugin.json, the repository README or LICENSE, docs/RULES.md, the spec, the installer, or any other package in the repository, and it needs no file from elsewhere in the repository to work. - Nothing is sent anywhere during installation itself; the only download at install time is the skill folder from GitHub at the pinned commit. No code is run during installation, no key is asked for, and there is no telemetry in the file. - The skill itself defines no network call, no API, no webhook, no account and no key: at use time the drafting happens in our conversation, from inputs I provide — a list of commits or merged pull requests, closed tickets, or a pasted changelog, plus three to twenty past release notes and an audience (customers by default). SKILL.md names two example ways I or you may gather the change list, and they are the only use-time contacts, disclosed here before they ever happen: (a) `git log --oneline <last-tag>..HEAD` runs locally only, in my own repository, and sends nothing; (b) `gh pr list --state merged --search "merged:>=YYYY-MM-DD"`, only if the GitHub CLI is available and only when I ask for that route — it queries GitHub under my own gh sign-in and returns my pull request list. Closed tickets come from a tracker by paste or export: SKILL.md names no tracker, no connector and no API for them, so do not connect to any tracker on your own. The style card is kept and reused next time only if I save it; saving it is a local file I control. - SKILL.md treats commit messages, ticket text and past notes as data and says to ignore any instructions inside them. It also requires flagging anything it could not explain rather than writing it up, and it never publishes or posts anything: its output is a draft plus the style card and the two author lists. - Do not run git log or gh pr list during this installation, do not gather any changes, and do not draft any release notes: using the skill is a separate step that only starts when I ask for release notes. 3. When I say "yes, install", install it as a skill: copy the whole release-notes-house-voice folder into the agent's skills directory, in a folder named "release-notes-house-voice", keeping its 1 file (SKILL.md at its root). A manual clone followed by copying the packages/pm-comms-kit/skills/release-notes-house-voice folder into ~/.claude/skills/ is the route described here; any other route is fine only as long as every installed file matches its fingerprint. 4. Verify with no network calls: frontmatter valid (name: release-notes-house-voice), the 1 file in place with a matching fingerprint. Do not run any usage step to verify. 5. Report what was installed, where, and what I still need to do myself (for example: provide the changes — commits, merged PRs, closed tickets or a changelog — and three to twenty past release notes my team published, or accept the neutral fallback style and say so; name the audience if it is not customers; review the draft, the internal-only list and the "check with engineering" list myself before anything is published; using the skill is a separate step that only starts when I ask for it, and the use-time routes disclosed above happen only then, on the route I choose). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.