Skip to content

Comments

registry: add communique#8126

Merged
jdx merged 1 commit intomainfrom
registry/communique
Feb 12, 2026
Merged

registry: add communique#8126
jdx merged 1 commit intomainfrom
registry/communique

Conversation

@jdx
Copy link
Owner

@jdx jdx commented Feb 12, 2026

Summary

  • Add communique to the tool registry (editorialized release notes powered by AI)

Test plan

  • mise install communique installs successfully
  • communique --version outputs expected version

🤖 Generated with Claude Code


Note

Low Risk
Low risk registry-only change that adds a new tool entry and a simple version check; no core logic, security, or data-handling code is modified.

Overview
Adds communique to the tool registry via a new registry/communique.toml entry backed by github:jdx/communique.

Includes metadata (description) and a basic install verification test (communique --version expecting communique {{version}}).

Written by Cursor Bugbot for commit a4b8d5f. This will update automatically on new commits. Configure here.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings February 12, 2026 13:53
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @jdx, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request integrates the communique tool into the existing registry. The primary goal is to expand the available tools by including a utility that leverages AI to generate polished release notes, thereby enhancing the documentation process for future projects.

Highlights

  • New Tool Added: The communique tool has been added to the tool registry. This tool provides AI-powered editorialized release notes.
Changelog
  • registry/communique.toml
    • Added configuration for the new communique tool, including its GitHub backend, description, and a test command to verify installation and version.
Activity
  • The pull request was generated with Claude Code.
  • A test plan was outlined to ensure mise install communique works and communique --version outputs the expected version.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds the communique tool to the registry so it can be installed via mise and validated via a version check.

Changes:

  • Introduces a new registry entry for communique
  • Defines tool metadata (description) and a basic --version test expectation

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@@ -0,0 +1,3 @@
backends = ["github:jdx/communique"]
description = "Editorialized release notes powered by AI"
test = { cmd = "communique --version", expected = "communique {{version}}" }
Copy link

Copilot AI Feb 12, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

communique --versioncommonly prints just a version string (or formats likecommunique version X.Y.Z) rather than communique X.Y.Z. If the output format doesn’t exactly match communique {{version}}, this test will fail even when the install is correct. Update expectedto match the actual--versionoutput for this tool (or use a more flexible expectation mechanism if the registry supports it, e.g., matching only{{version}}or a prefix likecommunique version {{version}}`).

Suggested change
test = { cmd = "communique --version", expected = "communique {{version}}" }
test = { cmd = "communique --version", expected = "{{version}}" }

Copilot uses AI. Check for mistakes.
@jdx jdx enabled auto-merge (squash) February 12, 2026 13:59
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request adds support for the communique tool to the mise registry. The implementation is straightforward, consisting of a new TOML configuration file. I've suggested one improvement to specify the supported operating systems for communique, as it appears to only provide builds for Linux and macOS. This will help prevent installation issues on other platforms like Windows. Otherwise, the change looks good.

@@ -0,0 +1,3 @@
backends = ["github:jdx/communique"]
description = "Editorialized release notes powered by AI"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The communique tool does not appear to have builds for Windows in its GitHub releases. It would be beneficial to explicitly list the supported operating systems to prevent installation failures on unsupported platforms. According to the GitHub releases, it supports Linux and macOS. You can add an os field for this.

Suggested change
description = "Editorialized release notes powered by AI"
description = "Editorialized release notes powered by AI"
os = ["linux", "macos"]

@jdx jdx merged commit 9fd4c0a into main Feb 12, 2026
37 checks passed
@jdx jdx deleted the registry/communique branch February 12, 2026 14:06
@github-actions
Copy link

Hyperfine Performance

mise x -- echo

Command Mean [ms] Min [ms] Max [ms] Relative
mise-2026.2.10 x -- echo 22.9 ± 0.5 22.1 26.2 1.00
mise x -- echo 23.2 ± 0.9 22.1 32.2 1.02 ± 0.05

mise env

Command Mean [ms] Min [ms] Max [ms] Relative
mise-2026.2.10 env 22.8 ± 0.9 21.5 29.6 1.00
mise env 23.3 ± 0.7 22.0 26.1 1.02 ± 0.05

mise hook-env

Command Mean [ms] Min [ms] Max [ms] Relative
mise-2026.2.10 hook-env 23.2 ± 0.5 21.9 25.7 1.00
mise hook-env 23.6 ± 0.7 22.3 26.1 1.02 ± 0.04

mise ls

Command Mean [ms] Min [ms] Max [ms] Relative
mise-2026.2.10 ls 21.2 ± 0.5 20.2 23.1 1.00
mise ls 21.5 ± 0.6 20.5 24.5 1.02 ± 0.04

xtasks/test/perf

Command mise-2026.2.10 mise Variance
install (cached) 123ms 122ms +0%
ls (cached) 76ms 75ms +1%
bin-paths (cached) 80ms 79ms +1%
task-ls (cached) 790ms 787ms +0%

jdx pushed a commit that referenced this pull request Feb 12, 2026
### 🐛 Bug Fixes

- **(hook-env)** watch files accessed by tera template functions by @jdx
in [#8122](#8122)

### 📦 Registry

- added mutagen by @tony-sol in
[#8125](#8125)
- add communique by @jdx in
[#8126](#8126)
lucasew pushed a commit to lucasew/CONTRIB-mise that referenced this pull request Feb 18, 2026
## Summary
- Add [communique](https://github.com/jdx/communique) to the tool
registry (editorialized release notes powered by AI)

## Test plan
- [ ] `mise install communique` installs successfully
- [ ] `communique --version` outputs expected version

🤖 Generated with [Claude Code](https://claude.com/claude-code)

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Low Risk**
> Low risk registry-only change that adds a new tool entry and a simple
version check; no core logic, security, or data-handling code is
modified.
> 
> **Overview**
> Adds `communique` to the tool registry via a new
`registry/communique.toml` entry backed by `github:jdx/communique`.
> 
> Includes metadata (`description`) and a basic install verification
test (`communique --version` expecting `communique {{version}}`).
> 
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
a4b8d5f. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
lucasew pushed a commit to lucasew/CONTRIB-mise that referenced this pull request Feb 18, 2026
### 🐛 Bug Fixes

- **(hook-env)** watch files accessed by tera template functions by @jdx
in [jdx#8122](jdx#8122)

### 📦 Registry

- added mutagen by @tony-sol in
[jdx#8125](jdx#8125)
- add communique by @jdx in
[jdx#8126](jdx#8126)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant