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.
Validate and project canonical Happier release-note source, StoryDeck cards, translations, and media assets without making editorial or release-policy decisions.
Install Happier Release Notes
$ npx skills add happier-dev/happier --skill happier-release-notes -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install happier-dev/happier happier-release-notes --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/happier-dev/happier.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/happier-release-notes .claude/skills/happier-release-notes && 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 "happier-release-notes" agent skill from https://github.com/happier-dev/happier/tree/dev/.agents/skills/happier-release-notes into .claude/skills/happier-release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "happier-release-notes", 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/happier-dev/happier/tree/dev/.agents/skills/happier-release-notesType 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 happier-dev/happier --skill happier-release-notes -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install happier-dev/happier happier-release-notes --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/happier-dev/happier.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/happier-release-notes .agents/skills/happier-release-notes && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "happier-release-notes" agent skill from https://github.com/happier-dev/happier/tree/dev/.agents/skills/happier-release-notes into .agents/skills/happier-release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "happier-release-notes", 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 happier-dev/happier --skill happier-release-notes -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install happier-dev/happier happier-release-notes --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/happier-dev/happier.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/happier-release-notes .cursor/skills/happier-release-notes && 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 "happier-release-notes" agent skill from https://github.com/happier-dev/happier/tree/dev/.agents/skills/happier-release-notes into .cursor/skills/happier-release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "happier-release-notes", 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/happier-dev/happier.git --path .agents/skills/happier-release-notes--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 happier-dev/happier --skill happier-release-notes -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install happier-dev/happier happier-release-notes --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/happier-dev/happier.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/happier-release-notes .gemini/skills/happier-release-notes && 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 "happier-release-notes" agent skill from https://github.com/happier-dev/happier/tree/dev/.agents/skills/happier-release-notes into .gemini/skills/happier-release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "happier-release-notes", 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 happier-dev/happier happier-release-notesInstalls 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 happier-dev/happier --skill happier-release-notes -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/happier-dev/happier.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/happier-release-notes .github/skills/happier-release-notes && 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 "happier-release-notes" agent skill from https://github.com/happier-dev/happier/tree/dev/.agents/skills/happier-release-notes into .github/skills/happier-release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "happier-release-notes", 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 happier-dev/happier --skill happier-release-notes -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install happier-dev/happier happier-release-notes --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/happier-dev/happier.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/happier-release-notes .opencode/skills/happier-release-notes && 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 "happier-release-notes" agent skill from https://github.com/happier-dev/happier/tree/dev/.agents/skills/happier-release-notes into .opencode/skills/happier-release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "happier-release-notes", 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
happier-release-notes- GitHub stars
- 1.9k
- Token cost
- ~1.2k tokens
- SKILL.md length
- 441 words
- Files
- 2
- Skills in repo
- 28
- Repo updated
- First seen
- Licence
- MIT
At a glance
Validate and project canonical Happier release-note source, StoryDeck cards, translations, and media assets without making editorial or release-policy decisions.
- Works in 3 steps: Read apps/ui/release-notes/README.md and → Inspect… → If UI behavior changes, use the…
- Tasks that involve Changelog and release notes
- SKILL.md covers Read first, Canonical changelog and…, StoryDeck source and assets and Validation
- Calls node and yarn
What it does
Happier Release Notes is an agent skill from happier-dev/happier. Validate and project canonical Happier release-note source, StoryDeck cards, translations, and media assets without making editorial or release-policy decisions.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).
It sits in Development, covering Changelog and release notes and Translation. The repository describes itself as: Web, Desktop & Mobile client and orchestrator for Codex, Claude Code, OpenCode, Pi, Cursor, Grok, Antigravity, Kimi, Augment Code, Qwen, fully end-to-end encrypted. The licence is MIT.
When your agent uses it
- Tasks that involve Changelog and release notes
- Tasks that involve Translation
Example prompts
- “/happier-release-notes”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Read apps/ui/release-notes/README.md and
- Inspect apps/ui/sources/changelog/releaseNotes/types.ts and
- If UI behavior changes, use the canonical UI testkit and TDD.
What it can do on your machine
Read from SKILL.md and the folder at commit 1f03ccd. 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:
nodeyarn
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use yarn, 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
Happier Release Notes loads about 1.2k tokens when it runs. Until then it costs about 46 tokens; SKILL.md has 441 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 happier-dev/happier at commit 1f03ccd, republished under its MIT licence (© happier-dev). 441 words, ~1,241 tokens.
Download SKILL.mdSave it as
.claude/skills/happier-release-notes/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- happier-release-notes
- description
- Validate and project canonical Happier release-note source, StoryDeck cards, translations, and media assets without making editorial or release-policy decisions.
Happier Release Notes
This skill owns only source-coupled release-note mechanics: the canonical changelog section schema, bounded-channel projection, StoryDeck cards, translations, assets, and generation. It does not choose release scope, group changes, write editorial prose, recommend patch/minor/major, approve content, or dispatch a release.
For those decisions, start with the private maintainer release authority:
hmaint release bootstrap --repo <absolute checkout> --jsonRead first
- Read
apps/ui/release-notes/README.mdandapps/ui/release-notes/releases/README.md. - Inspect
apps/ui/sources/changelog/releaseNotes/types.tsandapps/ui/sources/components/ui/storyDeck/storyDeckCardLimits.tsbefore changing card data or limits. - If UI behavior changes, use the canonical UI testkit and TDD.
Canonical changelog and bounded projections
apps/ui/CHANGELOG.md is the single authored authority for one release's
public Markdown and exact bounded channel text. Put this JSON comment at the
start of the matching ## Release <project-release-id> - <date> section. The
project release ID is a unique lowercase identifier such as 2026-08-09.1,
independent of every component version. Use the date plus an ordinal, increase
the ordinal for another release on that date, and keep the same ID from preview
through stable. The heading is the only authored source; a workflow
input only selects and verifies it:
<!-- happier-release-note-projections:v1
{
"expo": { "message": "Approved Expo text." },
"appStore": { "whatsNew": "Approved App Store text." },
"playStore": { "whatsNew": "Approved Play Store text." },
"storyDeck": { "summary": "Approved StoryDeck text." }
}
-->
## Public heading
Approved public Markdown follows here.The comment is removed from the GitHub/rolling Markdown projection. The script publishes every bounded string exactly as authored—there is no truncation, translation, synthesis, or AI rewrite. Expo is the currently consumed required projection. App Store, Play Store, and StoryDeck projections are optional until the selected release surfaces consume them; when present they are validated. Limits are: Expo 1,024; App Store 4,000; Play 500; StoryDeck 280. The section must contain meaningful public Markdown after the comment.
Project the release with its source identity and independently versioned components:
node scripts/pipeline/release/release-notes/project-release-notes.mjs \
--release-id <project-release-id> \
--source-sha <40-lowercase-git-sha> \
--component-version ui=<ui-semver> \
--component-version cli=<cli-semver> \
--component-version stack=<stack-semver> \
--component-version server=<server-semver> \
--changelog apps/ui/CHANGELOG.mdThe v2 bundle records { id, sourceSha, components }; it does not treat the UI
version as a project-wide release identity. Workflow callers must pass the
human-authored project ID, the release source SHA they already verified, and
every applicable component version, then validate the v2 bundle before use.
Show full SKILL.md (136 more words)Show less
StoryDeck source and assets
- Add or update
apps/ui/release-notes/releases/<releaseId>.jsononly with already-approved card content. - Add each referenced translation key to every locale under
apps/ui/sources/text/translations/. - Register image-card and video-poster local assets in
sources/components/ui/storyDeck/storyDeckBundledAssetRegistry.ts. - Put remote video and optional fallback media in
apps/ui/release-notes/assets/<releaseId>/. - Run from
apps/ui:
yarn tsx sources/scripts/parseReleaseNotes.ts- Confirm only the generated release-note manifest/index outputs changed.
For remote assets, build and publish only through the canonical scripts:
node scripts/pipeline/release/release-notes/build-release-notes-assets.mjs
node scripts/pipeline/release/release-notes/publish-release-notes-assets.mjs --dry-runDo not upload or modify a GitHub release unless separately authorized.
Validation
node --test scripts/release/release_notes_projection.contract.test.mjs
cd apps/ui && yarn vitest run --config vitest.config.ts \
sources/changelog/releaseNotes/schema.test.ts \
sources/scripts/parseReleaseNotes.test.tsThese checks validate structure, source identity, selected bounded fields, and asset/translation references. They must not judge editorial wording or release selection.
Issue stage:* labels and issue comments are not release-note source. The owning release workflow reconciles availability after verification according to docs/issue-triage.md; keep editorial projection and issue lifecycle as separate consumers of the same proven release.
© happier-dev, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in .agents/skills/happier-release-notes of happier-dev/happier.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit 1f03ccd
Compare with similar skills
Happier Release Notes 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 |
|---|---|---|---|---|---|---|
| Happier Release Notes this skillhappier-dev/happier | 1.9k | — | ~1.2k | 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 | 516 | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Release WorkflowCaldis/react-zmage | 946 | — | ~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.
Release New Version
niki914/zafiro
A skill your agent uses when the user wants to release a new Zafiro version — drafting bilingual release notes, deciding the next version number, bumping app/build.gradle.kts, tagging, and…
More from happier-dev/happier
All 28 skills in this repoHappier Review
happier-dev/happier
Conduct evidence-backed Happier code, plan-completeness, session, worktree, feature, commit, branch, PR, codebase, and release-readiness reviews with affected-corridor analysis, high-confidence…
Happier CI Stabilize
happier-dev/happier
Stabilize failing, flaky, slow, or repeatedly rerun Happier CI and nightlies by collecting all reachable failures from one exact attempt, correcting canonical causes in one batch, simplifying…
Happier Commit Worktree
happier-dev/happier
Reconnoiter, classify, validate, group, and commit a large or continuously changing Happier worktree as coherent, human-understandable commits while preserving concurrent work and excluding…
Happier Release
happier-dev/happier
Resolve Happier's private release authority and run an exact-SHA release or nightly through cheap admission, verified CI evidence, resumable immutable candidates, and terminal publication proof.
Happier Diagnose
happier-dev/happier
Diagnose and explain a Happier runtime, session, daemon, provider (Claude/Codex/OpenCode), authentication, or connectivity incident from logs, structured diagnostics, runtime state, and source…
Happier Implement
happier-dev/happier
Implement, change, build, fix, refactor, migrate, or apply accepted review findings in the Happier repositories with canonical-owner discovery, scope-preserving solution economy, TDD, efficient…
Related
Categories
Questions about Happier Release Notes
What does Happier Release Notes do?
Validate and project canonical Happier release-note source, StoryDeck cards, translations, and media assets without making editorial or release-policy decisions. Happier Release Notes is an agent skill from happier-dev/happier. Validate and project canonical Happier release-note source, StoryDeck cards, translations, and media assets without making editorial or release-policy decisions.
When should I use Happier Release Notes?
Happier Release Notes fits situations like: tasks that involve Changelog and release notes; tasks that involve Translation.
How do I install Happier Release Notes in Claude Code?
Run `npx skills add happier-dev/happier --skill happier-release-notes -a claude-code`. Or copy the skill folder (.agents/skills/happier-release-notes in happier-dev/happier) into .claude/skills/happier-release-notes in your project. Claude Code loads it when a task matches its description.
How do I install Happier Release Notes in Codex?
Run `npx skills add happier-dev/happier --skill happier-release-notes -a codex`. Or copy the skill folder (.agents/skills/happier-release-notes in happier-dev/happier) into .agents/skills/happier-release-notes in your project. Codex loads it when a task matches its description.
Can I use Happier Release Notes 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 happier-dev/happier --skill happier-release-notes -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/happier-release-notes, .gemini/skills/happier-release-notes, .github/skills/happier-release-notes and .opencode/skills/happier-release-notes in your project.
What does Happier Release Notes need to run?
Going by SKILL.md and its folder, Happier Release Notes needs the command-line tools its instructions call (node and yarn).
Does Happier Release Notes 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 Happier Release Notes 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 Happier Release Notes use?
Happier Release Notes 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 Happier Release Notes use?
About 1.2k 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 Happier Release Notes?
Skills that share tags, products or a category with Happier Release Notes: 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, 516 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Happier Release Notes?
happier-dev (a GitHub organization) maintains it in happier-dev/happier, which has 1,883 GitHub stars. The repository holds 28 skills in this directory. The repository was last updated on October 8, 2026.
Source: happier-dev/happier on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.