// Create GitHub issues for the RobustMQ project. Use when the user asks to create an issue, file a bug, propose a feature, or track a task.
| name | create-issue |
| description | Create GitHub issues for the RobustMQ project. Use when the user asks to create an issue, file a bug, propose a feature, or track a task. |
Create GitHub issues for the RobustMQ repository using the project's issue script and templates.
Ask the user or infer from context which template to use:
| Template | Title Prefix | Labels | When |
|---|---|---|---|
| Feature Request | [Feat] | kind:feat | Brand new feature |
| Enhancement | [Style/Refactor/Performance/Docs/Test/Build/CI/Chore] | enhancement | Improve existing functionality |
| Bug Report | [BUG] | kind:bug | Something is broken |
| Subtask | [RBIP-*/MINOR][...][Subtask] | kind:subtask | Subtask of a parent issue |
Template definitions are in .github/ISSUE_TEMPLATE/.
GITHUB_TOKEN if not already set in the environment.scripts/create-issue.sh:export GITHUB_TOKEN=<user-provided token>
./scripts/create-issue.sh \
--title "<title with correct prefix>" \
--body "$(cat <<'EOF'
<body content>
EOF
)" \
--labels "<labels>"
Return the created issue URL to the user.
kind:feat)## What problem does the new feature solve?
<describe the problem and why it matters>
## What does the feature do?
<high-level overview>
## Implementation challenges
<optional: technical details, design considerations>
enhancement)## Type
<one of: Style / Refactor / Performance / Doc / Test / Build / CI / Chore>
## What does the enhancement do?
<description of the improvement>
## Implementation challenges
<optional: technical details>
kind:bug)## Bug type
<one of: Configuration / Crash / Data corruption / Incorrect result / Locking issue / Performance issue / Unexpected error / Other>
## Affected subsystem
<one of: Standalone mode / Frontend / Datanode / Meta / Other>
## Minimal reproduce step
<steps to reproduce>
## Expected behavior
<what should happen>
## Actual behavior
<what actually happens>
## Environment
<OS, version, architecture>
## Relevant logs
<optional: log output or stack trace>
kind:subtask)## Describe the subtask
<clear description of the subtask>
## Parent issue
<link to the parent issue>
7×24 chaos testing for RobustMQ. Injects broker-kill and network-delay faults, validates SDK client resilience across Python/Go/Rust/Java, and publishes a Markdown + JSON report to GitHub after each run.
Audit and update the HTTP API documentation under docs/zh/Api/ and docs/en/Api/ against the actual route definitions in src/admin-server/src/. Uses path.rs as the single source of truth. Fixes wrong URI prefixes, non-existent routes, wrong request/response fields, and syncs the English docs to match the Chinese ones.
Complete step-by-step guide for implementing a new protocol Broker in RobustMQ. Use when the user asks to add a new broker, implement a new protocol, or scaffold a new broker crate.
Deep analysis and iterative fixing of a Rust source file. Finds logic errors, lock/concurrency issues, and simplification opportunities, then fixes them one by one until the file is clean.
Implements new RobustMQ MQTT connector integrations end-to-end using project conventions. Use when the user asks to add, implement, or support a new connector type such as webhook, opentsdb, clickhouse, influxdb, cassandra, mqtt bridge, or protocol-compatible targets.
Designs and implements minimal, high-value metrics for RobustMQ services and dashboards. Use when the user asks to add metrics, improve observability, or update Grafana panels for core processing pipelines.