Add UI String
openfootmanager/openfootmanager
Add or change any text a player can see, in every locale the game ships in.
A skill your agent uses when the user asks to create, draft, prepare, or publish a GitHub issue for the rocketmq-rust project — bugs, features, enhancements, refactors, docs, unit tests, CI…
Install Rocketmq Rust Issue Generator
$ npx skills add mxsm/rocketmq-rust --skill rocketmq-rust-issue-generator -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mxsm/rocketmq-rust rocketmq-rust-issue-generator --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/mxsm/rocketmq-rust.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/rocketmq-rust-issue-generator .claude/skills/rocketmq-rust-issue-generator && 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 "rocketmq-rust-issue-generator" agent skill from https://github.com/mxsm/rocketmq-rust/tree/main/.agents/skills/rocketmq-rust-issue-generator into .claude/skills/rocketmq-rust-issue-generator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rocketmq-rust-issue-generator", 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/mxsm/rocketmq-rust/tree/main/.agents/skills/rocketmq-rust-issue-generatorType 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 mxsm/rocketmq-rust --skill rocketmq-rust-issue-generator -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mxsm/rocketmq-rust rocketmq-rust-issue-generator --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mxsm/rocketmq-rust.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/rocketmq-rust-issue-generator .agents/skills/rocketmq-rust-issue-generator && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "rocketmq-rust-issue-generator" agent skill from https://github.com/mxsm/rocketmq-rust/tree/main/.agents/skills/rocketmq-rust-issue-generator into .agents/skills/rocketmq-rust-issue-generator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rocketmq-rust-issue-generator", 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 mxsm/rocketmq-rust --skill rocketmq-rust-issue-generator -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mxsm/rocketmq-rust rocketmq-rust-issue-generator --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mxsm/rocketmq-rust.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/rocketmq-rust-issue-generator .cursor/skills/rocketmq-rust-issue-generator && 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 "rocketmq-rust-issue-generator" agent skill from https://github.com/mxsm/rocketmq-rust/tree/main/.agents/skills/rocketmq-rust-issue-generator into .cursor/skills/rocketmq-rust-issue-generator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rocketmq-rust-issue-generator", 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/mxsm/rocketmq-rust.git --path .agents/skills/rocketmq-rust-issue-generator--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 mxsm/rocketmq-rust --skill rocketmq-rust-issue-generator -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mxsm/rocketmq-rust rocketmq-rust-issue-generator --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mxsm/rocketmq-rust.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/rocketmq-rust-issue-generator .gemini/skills/rocketmq-rust-issue-generator && 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 "rocketmq-rust-issue-generator" agent skill from https://github.com/mxsm/rocketmq-rust/tree/main/.agents/skills/rocketmq-rust-issue-generator into .gemini/skills/rocketmq-rust-issue-generator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rocketmq-rust-issue-generator", 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 mxsm/rocketmq-rust rocketmq-rust-issue-generatorInstalls 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 mxsm/rocketmq-rust --skill rocketmq-rust-issue-generator -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mxsm/rocketmq-rust.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/rocketmq-rust-issue-generator .github/skills/rocketmq-rust-issue-generator && 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 "rocketmq-rust-issue-generator" agent skill from https://github.com/mxsm/rocketmq-rust/tree/main/.agents/skills/rocketmq-rust-issue-generator into .github/skills/rocketmq-rust-issue-generator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rocketmq-rust-issue-generator", 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 mxsm/rocketmq-rust --skill rocketmq-rust-issue-generator -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mxsm/rocketmq-rust rocketmq-rust-issue-generator --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mxsm/rocketmq-rust.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/rocketmq-rust-issue-generator .opencode/skills/rocketmq-rust-issue-generator && 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 "rocketmq-rust-issue-generator" agent skill from https://github.com/mxsm/rocketmq-rust/tree/main/.agents/skills/rocketmq-rust-issue-generator into .opencode/skills/rocketmq-rust-issue-generator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rocketmq-rust-issue-generator", 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
rocketmq-rust-issue-generator- GitHub stars
- 1.5k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 737 words
- Files
- 3 (incl. scripts)
- Skills in repo
- 6
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
A skill your agent uses when the user asks to create, draft, prepare, or publish a GitHub issue for the rocketmq-rust project — bugs, features, enhancements, refactors, docs, unit tests, CI…
- Works in 4 steps: Locate Templates → Fill The Issue → Remove Local Paths → …
- The user asks to create
- SKILL.md covers When to Use, Quick Reference, Workflow and Common Mistakes, plus 2 more sections
- Runs Python scripts from its folder; calls rg and python
What it does
Rocketmq Rust Issue Generator is an agent skill from mxsm/rocketmq-rust. Use when the user asks to create, draft, prepare, or publish a GitHub issue for the rocketmq-rust project — bugs, features, enhancements, refactors, docs, unit tests, CI, runtime-model, broker, namesrv, client, store, dashboard, architecture, or performance work — especially when the issue must preserve real ISSUETEMPLATE fields, exact title prefix including template emoji, aligned labels, actionable engineering tasks, and no leaked local filesystem paths.
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including scripts (for example `evals/evals.json` and `scripts/audit_issue_paths.py`).
It sits in Testing & QA, covering Unit testing and Refactoring. It works with Rust, GitHub and Model Context Protocol. The repository describes itself as: 🚀 Apache RocketMQ built in Rust 🦀 — faster, safer, and more memory-efficient. Powering high-performance messaging for the AI era, with AI Agent, MCP, and AI-SRE capabilities. The licence is Apache-2.0.
When your agent uses it
- The user asks to create
- Publish a GitHub issue for the rocketmq-rust project — bugs
- Performance work — especially when the issue must preserve real ISSUETEMPLATE fields
- Exact title prefix including template emoji
Example prompts
- “/rocketmq-rust-issue-generator”
Requirements
- Python 3
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 13f7f5d. 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
Ships 1 file in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
rgpython
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 no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Rocketmq Rust Issue Generator loads about 1.6k tokens when it runs. Until then it costs about 123 tokens; SKILL.md has 737 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); the scripts in this folder are not scanned.
SKILL.md
The full file from mxsm/rocketmq-rust at commit 13f7f5d, republished under its Apache-2.0 licence (© mxsm). 737 words, ~1,635 tokens.
Download SKILL.mdSave it as
.claude/skills/rocketmq-rust-issue-generator/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- rocketmq-rust-issue-generator
- description
- Use when the user asks to create, draft, prepare, or publish a GitHub issue for the rocketmq-rust project — bugs, features, enhancements, refactors, docs, unit tests, CI, runtime-model, broker, namesrv, client, store, dashboard, architecture, or performance work — especially when the issue must preserve real ISSUE_TEMPLATE fields, exact title prefix including template emoji, aligned labels, actionable engineering tasks, and no leaked local filesystem paths.
RocketMQ Rust Issue Generator
Generate GitHub issue drafts from the repository's real issue forms. Template-driven — do not output a fixed canonical body unless the selected form has those fields.
When the repository owner or maintainer wants to prepare issues for new contributors to claim, also use rocketmq-rust-good-first-issue for concrete file checklists, newcomer labels, and optional per-crate sub-issues.
When to Use
- User asks to create, draft, or publish a GitHub issue for rocketmq-rust
- User's rough draft mentions generic sections or non-existent template names — must be converted to real forms
- Issue must preserve exact template title prefix (including emoji), label set, and field order
- Local filesystem paths must be audited and removed before publishing
- Public issue titles and body content must be English-only
When NOT to use: Non-rocketmq-rust repositories, pure discussion/questions that should not become GitHub issues, or requests where the user explicitly says not to apply issue templates.
Quick Reference
| Intent | Template | Title Prefix |
|---|---|---|
| Bug, panic, incorrect behavior | bug_report.yml | [Bug🐛] |
| Missing/improved test coverage | unit_test.yml | [Test🧪] |
| Docs, README, examples, comments | doc.yml | [Doc📝] |
| New broker/client/store/dashboard capability | feature_request.yml | [Feature🚀] |
| CI gate, runtime audit, ergonomics | enhancement_request.yml | [Enhancement✨] |
| Internal restructure, module cleanup | refactor.yml | [Refactor♻️] |
Select the narrowest template. When ambiguous, state tradeoff and choose narrowest (e.g., "add consume queue recovery tests" → unit test, not feature). Verify files exist in checkout — don't assume draft-only names like architecture.yml.
Workflow
1. Locate Templates
rg --hidden --files -g '.github/ISSUE_TEMPLATE/**' -g 'ISSUE_TEMPLATE/**' -g '!**/target/**'Read config.yml for policy. For each form, extract name, title prefix (with emoji), labels, every body item in order, and validations.required. For Markdown forms, preserve heading order and checklist meaning.
If terminal output corrupts emoji or symbols, do not copy from the noisy terminal. Re-read the template files as UTF-8 and use the exact checked-out title: value.
2. Fill The Issue
Title: <template title prefix including emoji><specific summary>
Template: <filename>
Labels: <labels from template>
<issue body following template field order>
Missing info:
- <None, or concise missing confirmations/data>Rules:
- Every template field, in order. Required fields must have content or be listed as missing.
- Use
Not applicableonly when a field clearly does not apply. - Never mark prerequisite/contribution checkboxes complete unless confirmed or actually performed.
- Generate the title summary from the actual bug, feature, test gap, doc change, or refactor. Do not use sequencing-marker wording such as
task 1,stage 1,phase 1,step 3, orpart 4, even when the user's rough draft contains those words. - Tasks must be actionable: name affected modules, expected behavior, tests, and validation commands.
- Use RocketMQ domain vocabulary (broker, namesrv, commitlog, consume queue, Tokio runtime, etc.) only where it helps the form.
- Write all public issue title/body text in English. Repository-relative paths, code identifiers, commands, issue numbers, Markdown punctuation, and the template emoji are allowed; Chinese or other non-English prose is not allowed.
Show full SKILL.md (311 more words)Show less
3. Remove Local Paths
Strip Windows/Unix home paths, file:// links, user-home env vars, local screenshot/temp/IDE paths. Rewrite to repository-relative paths or generic descriptions ("local broker log").
Audit before publishing, including the title when available:
python <skill-dir>/scripts/audit_issue_paths.py --title "<title>" <draft.md>Fix every finding.
4. Publish
- Confirm required fields complete and path audit passes.
- Use available GitHub tool/CLI with template labels.
- Report created issue URL. If publishing unavailable, return ready-to-submit draft.
Common Mistakes
| Mistake | Fix |
|---|---|
| Dropping the template emoji from title | Copy title: prefix exactly from the template file |
Inventing template names (e.g., architecture.yml) | Verify files exist in checkout; use only real filenames |
| Marking checkboxes complete without confirmation | List unconfirmed items as missing |
| Leaving a local Windows user path in draft | Run audit_issue_paths.py before finalizing |
| Writing issue prose in Chinese or mixed language | Rewrite the title/body in English and rerun the audit |
Using process labels like task 1, stage 1, or phase 1 in the title | Replace them with a concise summary of the actual change or problem |
| Using feature_request for test-only work | Unit test additions → unit_test.yml |
| Copying mojibake emoji from terminal | Re-read file with UTF-8 or use file content directly |
Output Modes
- Title only: Return candidate titles with exact template prefix.
- Full draft: Title, template, labels, body in template order, missing info section.
- Draft conversion: Normalize user's rough draft to real form; drop sections not in the selected template.
Final Check
- Selected template filename is real in the current checkout.
- Title keeps the selected template prefix exactly, including emoji.
- Title summary describes the actual change/problem and does not contain sequencing markers like
task 1,stage 1, orphase 1. - Labels match the selected template.
- Body fields appear in template order.
- Required fields have content or are listed under
Missing info. - Title/body are English-only.
- Checkboxes are not falsely marked complete.
- Path and English audit passes with no local absolute paths, machine-specific roots, or non-English prose.
© mxsm, Apache-2.0. 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 2 other files (scripts) in .agents/skills/rocketmq-rust-issue-generator of mxsm/rocketmq-rust.
- SKILL.md
- evals/evals.json
- scripts/audit_issue_paths.py
Open the folder on GitHubat commit 13f7f5d
Compare with similar skills
Rocketmq Rust Issue Generator 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 |
|---|---|---|---|---|---|---|
| Rocketmq Rust Issue Generator this skillmxsm/rocketmq-rust | 1.5k | — | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| Add UI Stringopenfootmanager/openfootmanager | 1.1k | — | ~2.6k | Automated safety check: Pass | GPL-3.0 | |
| Reviewapollographql/apollo-mcp-server | 311 | — | ~2.9k | Automated safety check: Pass | MIT | |
| Rust Hygiene Audittsz-org/tsz | 572 | — | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| OctomindMuvon/octomind | 148 | — | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| Releasearcee-ai/nac | 279 | — | ~2.7k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Review
apollographql/apollo-mcp-server
Review a GitHub pull request for a Rust codebase. An agent skill from apollographql/apollo-mcp-server.
Rust Hygiene Audit
tsz-org/tsz
Run a deep DRY + code-hygiene audit of the Rust workspace and turn the findings into verified, deduplicated, hierarchical GitHub tech-debt issues.
Octomind
Muvon/octomind
Delegate coding to the Octomind CLI — a token-efficient, model-agnostic coding agent.
Release
arcee-ai/nac
Cut and publish a full stable NAC release after main, release-PR, and publication CI pass.
Refactor
termide/termide
Full-workspace code quality analysis and refactoring with validation
More from mxsm/rocketmq-rust
Rocketmq Rust Local Cluster
mxsm/rocketmq-rust
Set up, start, verify, inspect, and stop local development clusters from the current rocketmq-rust checkout.
Rocketmq Rust PR Submitter
mxsm/rocketmq-rust
A skill your agent uses when the user asks to prepare, submit, publish, or optimize a pull request for the rocketmq-rust project, especially when the PR title or commit message must follow the [ISSUE
Translate It Doc En Zh
mxsm/rocketmq-rust
Translate English IT and software engineering documents into professional, accurate Chinese.
Rocketmq Rust Good First Issue
mxsm/rocketmq-rust
Help the rocketmq-rust repository owner or maintainer prepare and publish good first issues for new contributors to claim, with exact files, concrete changes, acceptance criteria, labels, and…
Rust Doc Comment Generator
mxsm/rocketmq-rust
Generate idiomatic, production-grade Rust comments and documentation strictly following official Rustdoc and Rust API documentation conventions.
Related
Works with
Categories
Questions about Rocketmq Rust Issue Generator
What does Rocketmq Rust Issue Generator do?
A skill your agent uses when the user asks to create, draft, prepare, or publish a GitHub issue for the rocketmq-rust project — bugs, features, enhancements, refactors, docs, unit tests, CI…. Rocketmq Rust Issue Generator is an agent skill from mxsm/rocketmq-rust. Use when the user asks to create, draft, prepare, or publish a GitHub issue for the rocketmq-rust project — bugs, features, enhancements, refactors, docs, unit tests, CI, runtime-model, broker, namesrv, client, store, dashboard, architecture, or performance work — especially when the issue must preserve real ISSUETEMPLATE fields, exact title prefix including template emoji, aligned labels, actionable engineering tasks, and no leaked local filesystem paths.
When should I use Rocketmq Rust Issue Generator?
Rocketmq Rust Issue Generator fits situations like: the user asks to create; publish a GitHub issue for the rocketmq-rust project — bugs; performance work — especially when the issue must preserve real ISSUETEMPLATE fields; exact title prefix including template emoji.
How do I install Rocketmq Rust Issue Generator in Claude Code?
Run `npx skills add mxsm/rocketmq-rust --skill rocketmq-rust-issue-generator -a claude-code`. Or copy the skill folder (.agents/skills/rocketmq-rust-issue-generator in mxsm/rocketmq-rust) into .claude/skills/rocketmq-rust-issue-generator in your project. Claude Code loads it when a task matches its description.
How do I install Rocketmq Rust Issue Generator in Codex?
Run `npx skills add mxsm/rocketmq-rust --skill rocketmq-rust-issue-generator -a codex`. Or copy the skill folder (.agents/skills/rocketmq-rust-issue-generator in mxsm/rocketmq-rust) into .agents/skills/rocketmq-rust-issue-generator in your project. Codex loads it when a task matches its description.
Can I use Rocketmq Rust Issue Generator 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 mxsm/rocketmq-rust --skill rocketmq-rust-issue-generator -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/rocketmq-rust-issue-generator, .gemini/skills/rocketmq-rust-issue-generator, .github/skills/rocketmq-rust-issue-generator and .opencode/skills/rocketmq-rust-issue-generator in your project.
What does Rocketmq Rust Issue Generator need to run?
Going by SKILL.md and its folder, Rocketmq Rust Issue Generator needs Python for the scripts in its folder and the command-line tools its instructions call (rg and python). Our summary lists: Python 3.
Does Rocketmq Rust Issue Generator 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 Rocketmq Rust Issue Generator 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Rocketmq Rust Issue Generator use?
Rocketmq Rust Issue Generator is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Rocketmq Rust Issue Generator use?
About 1.6k tokens (SKILL.md is roughly 6.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 Rocketmq Rust Issue Generator?
Skills that share tags, products or a category with Rocketmq Rust Issue Generator: Add UI String (openfootmanager/openfootmanager, 1.1k stars), Review (apollographql/apollo-mcp-server, 311 stars), Rust Hygiene Audit (tsz-org/tsz, 572 stars) and Octomind (Muvon/octomind, 148 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Rocketmq Rust Issue Generator?
mxsm (a GitHub user) maintains it in mxsm/rocketmq-rust, which has 1,524 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 7, 2026.
Source: mxsm/rocketmq-rust on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.