Plane Release Notes Generator
makeplane/plane
Builds categorized release notes for a Plane release pull request from its commits and writes them into the PR description, for both the plane-cloud and plane-ee repos.
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
Install Rocketmq Rust PR Submitter
$ npx skills add mxsm/rocketmq-rust --skill rocketmq-rust-pr-submitter -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mxsm/rocketmq-rust rocketmq-rust-pr-submitter --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-pr-submitter .claude/skills/rocketmq-rust-pr-submitter && 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-pr-submitter" agent skill from https://github.com/mxsm/rocketmq-rust/tree/main/.agents/skills/rocketmq-rust-pr-submitter into .claude/skills/rocketmq-rust-pr-submitter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rocketmq-rust-pr-submitter", 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-pr-submitterType 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-pr-submitter -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mxsm/rocketmq-rust rocketmq-rust-pr-submitter --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-pr-submitter .agents/skills/rocketmq-rust-pr-submitter && 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-pr-submitter" agent skill from https://github.com/mxsm/rocketmq-rust/tree/main/.agents/skills/rocketmq-rust-pr-submitter into .agents/skills/rocketmq-rust-pr-submitter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rocketmq-rust-pr-submitter", 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-pr-submitter -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mxsm/rocketmq-rust rocketmq-rust-pr-submitter --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-pr-submitter .cursor/skills/rocketmq-rust-pr-submitter && 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-pr-submitter" agent skill from https://github.com/mxsm/rocketmq-rust/tree/main/.agents/skills/rocketmq-rust-pr-submitter into .cursor/skills/rocketmq-rust-pr-submitter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rocketmq-rust-pr-submitter", 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-pr-submitter--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-pr-submitter -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mxsm/rocketmq-rust rocketmq-rust-pr-submitter --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-pr-submitter .gemini/skills/rocketmq-rust-pr-submitter && 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-pr-submitter" agent skill from https://github.com/mxsm/rocketmq-rust/tree/main/.agents/skills/rocketmq-rust-pr-submitter into .gemini/skills/rocketmq-rust-pr-submitter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rocketmq-rust-pr-submitter", 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-pr-submitterInstalls 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-pr-submitter -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-pr-submitter .github/skills/rocketmq-rust-pr-submitter && 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-pr-submitter" agent skill from https://github.com/mxsm/rocketmq-rust/tree/main/.agents/skills/rocketmq-rust-pr-submitter into .github/skills/rocketmq-rust-pr-submitter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rocketmq-rust-pr-submitter", 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-pr-submitter -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-pr-submitter --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-pr-submitter .opencode/skills/rocketmq-rust-pr-submitter && 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-pr-submitter" agent skill from https://github.com/mxsm/rocketmq-rust/tree/main/.agents/skills/rocketmq-rust-pr-submitter into .opencode/skills/rocketmq-rust-pr-submitter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rocketmq-rust-pr-submitter", 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-pr-submitter- GitHub stars
- 1.5k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 623 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 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
- Works in 5 steps: Read the PR Template → Determine Issue Id → Write Title → …
- The user asks to prepare
- 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 PR Submitter is an agent skill from mxsm/rocketmq-rust. Use 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
Its SKILL.md is about 1.4k 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/validate_pr_content.py`).
It sits in Development, covering Commit messages and Pull requests. It works with Rust 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 prepare
- Optimize a pull request for the rocketmq-rust project
- Especially when the PR title
- Commit message must follow the [ISSUE
Example prompts
- “/rocketmq-rust-pr-submitter”
Requirements
- Python 3
Workflow steps
5 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 36142c2. 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 PR Submitter loads about 1.4k tokens when it runs. Until then it costs about 52 tokens; SKILL.md has 623 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 36142c2, republished under its Apache-2.0 licence (© mxsm). 623 words, ~1,381 tokens.
Download SKILL.mdSave it as
.claude/skills/rocketmq-rust-pr-submitter/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- rocketmq-rust-pr-submitter
- description
- Use 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
RocketMQ Rust PR Submitter
Prepare RocketMQ Rust PR titles, commit messages, and bodies from .github/PULL_REQUEST_TEMPLATE.md. Connects PR to issue via [ISSUE #id] title/commit prefix and Fixes #id body line.
When to Use
- User asks to create, prepare, or publish a PR for rocketmq-rust
- PR title or commit message must follow
[ISSUE #issue_id]<emoji><summary>format - PR body must follow the repository's real PR template (not a custom format)
- Issue id is available from user request, branch name, or commit history
- Public PR titles, commit messages, and body content must be English-only
When NOT to use: Simple branch merges without a linked issue. PRs for repos that don't use the RocketMQ Rust PR template convention.
Quick Reference
| Change Type | Emoji |
|---|---|
| Bug fix | 🐛 |
| Documentation | 📝 |
| Enhancement / CI / runtime audit | ✨ |
| New feature | 🚀 |
| Refactor | ♻️ |
| Tests | 🧪 |
If unclear, default to ✨ and note the assumption.
Workflow
1. Read the PR Template
rg --hidden --files -g '*PULL_REQUEST_TEMPLATE*' -g '*pull_request_template*' -g '!**/target/**'Expected: .github/PULL_REQUEST_TEMPLATE.md with three headings: Which Issue(s) This PR Fixes(Closes), Brief Description, How Did You Test This Change?. Remove HTML comments from the generated body. Use the checked-out template if it differs.
2. Determine Issue Id
Priority order: user request → branch name (issue-7544, fix-7544) → commit messages ([ISSUE #7544]) → prepared PR text (Fixes #7544). Normalize to numeric id. Never publish with #issue_id still present.
3. Write Title
[ISSUE #issue_id]<emoji><summary>Do not put spaces between ], the emoji, and the summary. No extra prefixes (conventional commit, branch name). Keep the summary short and action-oriented.
Generate the summary from the actual PR change: affected subsystem, behavior fixed, test coverage added, docs updated, or refactor performed. Do not use sequencing-marker wording such as task 1, stage 1, phase 1, step 3, or part 4, even if the branch name, issue text, or user draft contains those words.
Write the title and commit-message summary in English only. The required emoji is allowed; Chinese or other non-English prose is not allowed.
If creating a commit as part of the PR workflow, use the exact same compact format for the commit message:
[ISSUE #issue_id]<emoji><summary>4. Write Body
### Which Issue(s) This PR Fixes(Closes)
- Fixes #issue_id
### Brief Description
<Changed modules, behavior, motivation. Keep focused on maintainer review.>
### How Did You Test This Change?
<Commands run and results, or honest note that validation was not run.>Preserve template headings exactly. Keep paths repository-relative. In the test section, list commands and results; say "validation not run" honestly if applicable.
Write all public body prose in English. Repository-relative paths, code identifiers, commands, issue numbers, Markdown punctuation, and the required emoji are allowed.
Show full SKILL.md (259 more words)Show less
5. Validate and Publish
- Confirm branch, target branch, and issue id.
- Validate title/body:
bash python <skill-dir>/scripts/validate_pr_content.py --title "<title>" --body <body.md> - Use available GitHub tool/CLI. Create a normal ready-for-review PR — do not pass draft flags unless the user explicitly asked for a draft PR.
- Report PR URL. If publishing unavailable, provide ready-to-submit title and body.
Common Mistakes
| Mistake | Fix |
|---|---|
| Omitting emoji from title | Always include emoji between ] and summary |
Leaving #issue_id placeholder | Replace with numeric id in both title and body |
| Creating draft PR by default | Normal ready-for-review PR unless user says "draft PR" |
| Claiming unrun validation passed | State "validation not run" honestly in test section |
| Writing PR prose in Chinese or mixed language | Rewrite the title/body in English and rerun validation |
| Adding spaces or extra prefixes | Only [ISSUE #id]<emoji><summary> for PR titles and commit messages |
Using process labels like task 1, stage 1, or phase 1 as the summary | Replace them with a concise summary of the actual code, docs, tests, or behavior change |
| Wrong emoji for change type | Match to linked issue type; default to ✨ |
Output Format
Full prepare request:
Title:
[ISSUE #issue_id]<emoji><summary>
Body:
### Which Issue(s) This PR Fixes(Closes)
- Fixes #issue_id
...Title only: Return candidate titles in the exact format.
Final Check
- Title matches
[ISSUE #number]<emoji><summary> - Commit message, when created, matches
[ISSUE #number]<emoji><summary> - Title and commit summary describe the actual change and do not contain sequencing markers like
task 1,stage 1, orphase 1. - Body includes three PR template headings in order with
- Fixes #number - Title/body are English-only.
- Test section doesn't claim unrun commands passed
- 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-pr-submitter of mxsm/rocketmq-rust.
- SKILL.md
- evals/evals.json
- scripts/validate_pr_content.py
Open the folder on GitHubat commit 36142c2
Compare with similar skills
Rocketmq Rust PR Submitter 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 PR Submitter this skillmxsm/rocketmq-rust | 1.5k | — | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| Plane Release Notes Generatormakeplane/plane | 61k | — | ~2.5k | Automated safety check: Pass | AGPL-3.0 | |
| Commit ScopeDevolutions/IronRDP | 3.2k | — | ~854 | Automated safety check: Pass | Apache-2.0 | |
| Zhtw Conventionssysprog21/zhtw-mcp | 488 | — | ~2k | Automated safety check: Pass | MIT | |
| Agentbro PR Mergeshirenchuang/agentbro | 203 | — | ~648 | Automated safety check: Pass | Apache-2.0 | |
| Cuga Contributor Workflowscuga-project/cuga-agent | 896 | — | ~277 | Automated safety check: Pass | Custom licence |
Similar skills
Commit Scope
Devolutions/IronRDP
Derive and validate the canonical scope for IronRDP Conventional Commit and pull-request titles.
Zhtw Conventions
sysprog21/zhtw-mcp
The zhtw-mcp conventions no gate enforces - the register a comment, a commit message and a PR reply are written in, where Chinese belongs in the tree and where it does not, the untracked working…
Agentbro PR Merge
shirenchuang/agentbro
A skill your agent uses when reviewing, fixing CI for, approving workflows for, or merging AgentBro pull requests into dev/main, especially external contributor PRs where contributor attribution…
Cuga Contributor Workflows
cuga-project/cuga-agent
Run CUGA contributor workflows: Conventional Commits, create pull requests against origin with gh and PR templates, and ruff check/format via uv.
Code Review
oaslananka/kicad-mcp-pro
A skill your agent uses for GitHub Copilot pull request and code reviews in oaslananka/kicad-mcp-pro.
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 Issue Generator
mxsm/rocketmq-rust
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…
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 PR Submitter
What does Rocketmq Rust PR Submitter do?
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. Rocketmq Rust PR Submitter is an agent skill from mxsm/rocketmq-rust.
When should I use Rocketmq Rust PR Submitter?
Rocketmq Rust PR Submitter fits situations like: the user asks to prepare; optimize a pull request for the rocketmq-rust project; especially when the PR title; commit message must follow the [ISSUE.
How do I install Rocketmq Rust PR Submitter in Claude Code?
Run `npx skills add mxsm/rocketmq-rust --skill rocketmq-rust-pr-submitter -a claude-code`. Or copy the skill folder (.agents/skills/rocketmq-rust-pr-submitter in mxsm/rocketmq-rust) into .claude/skills/rocketmq-rust-pr-submitter in your project. Claude Code loads it when a task matches its description.
How do I install Rocketmq Rust PR Submitter in Codex?
Run `npx skills add mxsm/rocketmq-rust --skill rocketmq-rust-pr-submitter -a codex`. Or copy the skill folder (.agents/skills/rocketmq-rust-pr-submitter in mxsm/rocketmq-rust) into .agents/skills/rocketmq-rust-pr-submitter in your project. Codex loads it when a task matches its description.
Can I use Rocketmq Rust PR Submitter 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-pr-submitter -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-pr-submitter, .gemini/skills/rocketmq-rust-pr-submitter, .github/skills/rocketmq-rust-pr-submitter and .opencode/skills/rocketmq-rust-pr-submitter in your project.
What does Rocketmq Rust PR Submitter need to run?
Going by SKILL.md and its folder, Rocketmq Rust PR Submitter 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 PR Submitter 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 PR Submitter 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 PR Submitter use?
Rocketmq Rust PR Submitter 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 PR Submitter use?
About 1.4k tokens (SKILL.md is roughly 5.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 PR Submitter?
Skills that share tags, products or a category with Rocketmq Rust PR Submitter: Plane Release Notes Generator (makeplane/plane, 61k stars), Commit Scope (Devolutions/IronRDP, 3.2k stars), Zhtw Conventions (sysprog21/zhtw-mcp, 488 stars) and Agentbro PR Merge (shirenchuang/agentbro, 203 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Rocketmq Rust PR Submitter?
mxsm (a GitHub user) maintains it in mxsm/rocketmq-rust, which has 1,525 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 9, 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.