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.
Generate, review, and publish release notes with Communique, including changelogs and package releases.
Install Communique
$ npx skills add jdx/communique --skill communique -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jdx/communique communique --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/jdx/communique.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/communique .claude/skills/communique && 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 "communique" agent skill from https://github.com/jdx/communique/tree/main/skills/communique into .claude/skills/communique/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "communique", 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/jdx/communique/tree/main/skills/communiqueType 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 jdx/communique --skill communique -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jdx/communique communique --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jdx/communique.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/communique .agents/skills/communique && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "communique" agent skill from https://github.com/jdx/communique/tree/main/skills/communique into .agents/skills/communique/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "communique", 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 jdx/communique --skill communique -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jdx/communique communique --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jdx/communique.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/communique .cursor/skills/communique && 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 "communique" agent skill from https://github.com/jdx/communique/tree/main/skills/communique into .cursor/skills/communique/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "communique", 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/jdx/communique.git --path skills/communique--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 jdx/communique --skill communique -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jdx/communique communique --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jdx/communique.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/communique .gemini/skills/communique && 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 "communique" agent skill from https://github.com/jdx/communique/tree/main/skills/communique into .gemini/skills/communique/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "communique", 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 jdx/communique communiqueInstalls 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 jdx/communique --skill communique -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jdx/communique.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/communique .github/skills/communique && 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 "communique" agent skill from https://github.com/jdx/communique/tree/main/skills/communique into .github/skills/communique/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "communique", 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 jdx/communique --skill communique -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jdx/communique communique --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jdx/communique.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/communique .opencode/skills/communique && 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 "communique" agent skill from https://github.com/jdx/communique/tree/main/skills/communique into .opencode/skills/communique/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "communique", 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
communique- GitHub stars
- 119
- Token cost
- ~999 tokens
- SKILL.md length
- 486 words
- Files
- 1
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- MIT
At a glance
Generate, review, and publish release notes with Communique, including changelogs and package releases.
- Working with the communique CLI
- SKILL.md covers Choose the release range, Review and edit the result and Apply the requested output
- Needs ANTHROPIC_API_KEY and OPENAI_API_KEY
- Communique.toml editorial configuration
What it does
Communique is an agent skill from jdx/communique. Generate, review, and publish release notes with Communique, including changelogs and package releases. Use when working with the communique CLI or communique.toml editorial configuration.
Its SKILL.md is about 1000 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: Editorialized release notes powered by AI. The licence is MIT.
When your agent uses it
- Working with the communique CLI
- Communique.toml editorial configuration
Example prompts
- “/communique”
Requirements
- A credential in ANTHROPIC_API_KEY
- A credential in OPENAI_API_KEY
What it can do on your machine
Read from SKILL.md and the folder at commit 34349cf. 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 (its code samples are bash).
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 these keys or tokens, usually read from environment variables:
ANTHROPIC_API_KEYOPENAI_API_KEYGITHUB_TOKEN
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Communique loads about 999 tokens when it runs. Until then it costs about 50 tokens; SKILL.md has 486 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 jdx/communique at commit 34349cf, republished under its MIT licence (© jdx). 486 words, ~999 tokens.
Download SKILL.mdSave it as
.claude/skills/communique/SKILL.md (or your agent's skills folder).- name
- communique
- description
- Generate, review, and publish release notes with Communique, including changelogs and package releases. Use when working with the communique CLI or communique.toml editorial configuration.
Communique
Read the repository's communique.toml, release workflow, and existing release
style before choosing flags. Use communique init only when configuration is
missing. CLI flags override configuration; preserve the project's provider and
model choices unless the task calls for changing them.
Choose the release range
Run from the target Git repository. Check the tag and previous reference before generation; pass the baseline explicitly when automatic selection is unsuitable:
communique generate v1.2.0 v1.1.0 --draft release.json --review-report review.mdIn a monorepo, use existing [packages.NAME] settings with --package NAME.
--path values replace the package's configured paths and are literal
repository-relative paths, not globs. --tag-pattern filters baseline tags;
--channel stable excludes prereleases, while the default all includes them.
Check the selected range printed by the command. Use HEAD for unreleased
changelog work, not for publishing a GitHub Release.
Generation calls an LLM and may read GitHub context, including with --dry-run.
Use the configured provider's credentials (ANTHROPIC_API_KEY or
OPENAI_API_KEY) through the existing secret mechanism without printing them.
GITHUB_TOKEN provides PR context and release access; label rules require it.
Missing history calls for fetching the needed tags or unshallowing a shallow
checkout, not substituting a guessed baseline.
Review and edit the result
Use --draft release.json when the result needs review before publication.
It saves the repository, tag, target commit, title, body, changelog, and review
metadata. Edit release_title, release_body, or changelog in that file as
needed; preserve the target and provenance fields.
- Use
--review-report review.mdto inspect included, omitted, and uncertain commits. The model's coverage assessments are advisory; check unclear claims against their linked source changes. - Add
--migration-guide upgrade.mdwhen upgrade instructions are needed. Verify examples and affected users before publishing. - Put reusable audience context in
contextand writing guidance insystem_extra. Label rules belong under[rules]; explicit inclusion wins over exclusion. Do not silently drop a change because its PR is inaccessible.
generate --dry-run skips GitHub/changelog updates and link verification; it
can still write explicitly requested drafts, reports, or output files. Review
links separately when using that mode.
Show full SKILL.md (165 more words)Show less
Apply the requested output
Preview an edited draft with:
communique publish release.json --dry-runWhen publication is authorized, communique publish release.json updates the
existing GitHub Release without calling the model again. It checks that the
remote tag still names the saved commit. If the tag moved, regenerate and review
the notes; do not edit target_commit just to bypass the check. Draft generation
cannot be combined with --github-release.
For an authorized direct generation and publication, use generate TAG --github-release. This replaces the release body. To retain hand-written text,
use --preserve-sections during generation (including draft generation); it
manages only the <!-- communique:start --> / <!-- communique:end --> section
and preserves the existing title. Its publish preview needs GitHub access to
merge the existing body, unlike a plain draft preview.
For local output, use --output RELEASE_NOTES.md, or --changelog to update
the version entry in CHANGELOG.md. --concise selects the short changelog
form. Publishing a saved draft does not write its changelog field to disk.
Inspect the resulting file diff or fetch the updated release to verify the
requested output.
© jdx, 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/communique of jdx/communique.
Open the folder on GitHubat commit 34349cf
Compare with similar skills
Communique 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 |
|---|---|---|---|---|---|---|
| Communique this skilljdx/communique | 119 | — | ~999 | Automated safety check: Pass | MIT | |
| Cutting A ReleaseTriliumNext/Trilium | 38k | — | ~3.2k | Automated safety check: Pass | AGPL-3.0 | |
| 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 | |
| Release Bumpjamiepine/voicebox | 57k | — | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
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.
Cut Release
jfernandez/bpftop
Cut a new versioned release of bpftop — pick the version, open a version-bump PR, sign-tag the merge commit on main, and draft GitHub release notes in the project's established format.
More from jdx/communique
Entire Search
jdx/communique
Search Entire checkpoint history and transcripts with entire search --json.
Related
Works with
Categories
Questions about Communique
What does Communique do?
Generate, review, and publish release notes with Communique, including changelogs and package releases. Communique is an agent skill from jdx/communique. Generate, review, and publish release notes with Communique, including changelogs and package releases.
When should I use Communique?
Communique fits situations like: working with the communique CLI; communique.toml editorial configuration.
How do I install Communique in Claude Code?
Run `npx skills add jdx/communique --skill communique -a claude-code`. Or copy the skill folder (skills/communique in jdx/communique) into .claude/skills/communique in your project. Claude Code loads it when a task matches its description.
How do I install Communique in Codex?
Run `npx skills add jdx/communique --skill communique -a codex`. Or copy the skill folder (skills/communique in jdx/communique) into .agents/skills/communique in your project. Codex loads it when a task matches its description.
Can I use Communique 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 jdx/communique --skill communique -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/communique, .gemini/skills/communique, .github/skills/communique and .opencode/skills/communique in your project.
What does Communique need to run?
Going by SKILL.md and its folder, Communique needs credentials named ANTHROPIC_API_KEY, OPENAI_API_KEY and GITHUB_TOKEN. Our summary lists: A credential in ANTHROPIC_API_KEY; A credential in OPENAI_API_KEY.
Does Communique 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 Communique 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 Communique use?
Communique 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 Communique use?
About 999 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 Communique?
Skills that share tags, products or a category with Communique: Cutting A Release (TriliumNext/Trilium, 38k stars), Mole CLI Release Flow (tw93/Mole, 70k stars), Draft Release Notes (jamiepine/voicebox, 57k stars) and Mole Release Notes Publisher (tw93/Mole, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Communique?
jdx (a GitHub user) maintains it in jdx/communique, which has 119 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 9, 2026.
Source: jdx/communique on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.